Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crystal Report Viewer Error - Physical database not found.

Status
Not open for further replies.

Jag69

Programmer
Mar 28, 2002
2
GB
I am viewing an existing crystal report (.rpt) through an ASP page. The report opens fine on my local machine (built as a server) with local sqlserver database, but when I deploy the files (after changing the database on the report via "Verify Database" option) to a separate web server and a separate Sqlserver database, I get the following error message:

CRAXDRT Error Occurred on Server. -2147192191 : Physical database not found.

I have checked that the CRAXDRT.dll versions are the same, also checked the dsn settings .... Help!
 
I assume that you call your reports through ASP code (you mentioned CRAXDRT). In this case, you can change your data source through the code with SetLogOnInfo method (as soon as the new database structure is identical to the original one); this will free you of verifying database in the Designer before deploying reports to production.

Also, you might want to check out this article:

I've had the same problem, Ntwdblib.dll was missing.
 
I once had the same problem. The problem is that you are missing one ODBC dll (but you have to find which one)
 
I've seen this message on occasions in the development cycle.
Ensure that crxdrt.dll is registered.
Similarly ensure that you have the required database access dll's for accessing data in the appropriate database (be it SQL Server, etc.). The dll's are listed in one of the development help files - indicating which dll's are required for which databases.
Can the client machines access the data through means outside of the crystal reports view ?
Steve
 
Thank you all for your replies, much appreciated. After numerous attempts at registering and unregistering dlls I stumbled across a solution. Crystal reports has the database set during design time, and when deploying these reports to a different server and database, I had to use the 'set location' menu option and point to the correct database, and then click on 'verify database'.

Then on the client the following files need to be registered (C:\winnt\system32\)
xqviewer.dll,cselexpt.ocx, sviewhlp.dll,swebrs.dll,crviewer.dll, and then it all worked fine.

Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top