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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error detected by database DLL. [Connecting to Page Server: testintra]

Status
Not open for further replies.

rustylee

Programmer
Sep 11, 2001
59
US
Error detected by database DLL. [Connecting to Page Server: testintra]

Greetings.

I have set up a test platform for an intranet server. I installed Win2k Server which comes with IIS 5.0. I performed a complete install of Crystal Reports 8.0 Developer on the server. I also installed Pervasive's 32-bit client for P.SQL 7.0. In production, this intranet server would be connecting to a Macola database on another server for Crystal Reports.

On the server, I created a very simple report from a Btrieve table using Crystal Reports' Btrieve drivers. I tested the report from the server and it ran fine. I saved the report in the same directory where some of the sample reports are kept, "General Business".

From another machine, I can connect to the intranet server and run the sample reports. I used the following URL: However, when I run my report I get the message "Error detected by database DLL. [Connecting to Page Server: testintra]".

In effort to troubleshoot, I set up and ODBC DSN for SQL Server (we have an MS SQL Server as well). From the intranet server, I created a Crystal Report using the ODBC connection. I tested the report from the server and it ran fine. I saved the report under the "General Business" folder as before.

From the other machine, connected to intranet server using the same URL (I used the same file name for this report). I was presented with a login prompt (something that needs be addressed later as this should be intrinsic to the report) and entered the 'sa' account info. The report was displayed in my browser.

My conclusion: The ActiveX component on the browser works. However, for whatever reason, Btrieve-based reports are problematic. That's not to say that other databases aren't a problem, but when the SQL/ODBC report works and the sample reports work, I have to assume there is something about the Btrieve setup. It can't be the Btrieve connnection on the server because, as I said before, I created and tested the report from the intranet server and it works beautiful.

Any ideas out there? I've searched on this issue and I haven't found any solution yet.

Thanks in advance...

-Rusty
 
What is meant by the Intranet Server, is this CE? If so, load it into CE through CMC and set up the database connectivity, then try running it through ePortfolio.

"Error detected by database DLL" is a very generic error, often times relating to database connectivity.

-k kai@informeddatadecisions.com
 
I performed a complete install of Crystal Reports 8.0 Developer on the intranet server (not Crystal Enterprise). This package includes a service known as Web Component Server. This is works in conjunction with IIS.

I am pretty confident that my error is related to database connectivity. Let me reiterate a couple of points:

1) The report works fine on the server, which tells me that database connectivity using Crystal Reports' native Btrieve drivers is working well.

2) Viewing reports on the Intranet using other other datasources works (ODBC/MS SQL, sample reports that come with Crystal Reports), which tells me that the report viewer on the client's browser functions properly.

Conclusion: There is a database connectivity problem with Btrieve when using the client's report viewer in the browser.

By the way, I'm using the ActiveX control for viewing in IE 5.5. That is evident by looking at the end of the URL:
?init=actx.
 
Any solution on this rustylee? I'm having the same problem.

thx Scott
Programmer Analyst
<{{><
 
Hi Scott,

I was able to get it to work based a suggestion in another thread where I posed this same question. If you go to the following link...


...Lisa suggested running the page server at the console instead of running it as a service, which worked.
 
Thanks! I agree, this is a wierd solution but it works.
Scott
Programmer Analyst
<{{><
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top