Failed to load database information

Question

1.00/5 (1 vote)

See more:

VS2013

I created report using Crystal Report VS2013. While in the development machine 64 bit the application works fine

But when I deployed the application into Win2008 64bit, whenever I run the report below message appear

Failed to load database information. Error in File ClaimsBySerialNo 11456_10292_{32E3653E-C045-4035-982F-0A872750C8DF}.rpt: Failed to load database information.

I had followed all the suggestion I can found in net but no success. Anybody ever solve this problem?

Posted 7-Nov-14 6:03am

vikramasingh

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-11-07T06:12:00

Start by looking at your database connection string: most of the time that is the culprit with any DB related problem, when you move from development to production.

The other problem can be access permissions on the actual DB file - depending on where you put it. Have a look at the folder and see if it is read and write for all users. If not, that can throw some odd errors as well.