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

[rustylee]

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:

http://testintra/scrreports/General Business/report1.rpt?init=actx.

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

 

[Naith]

In your ODBC DSN setup, check that you have the Current Directory option switched off in the ODBC Admin.

If it was on, verify the database, and republish the report.

Naith

 

[rustylee]

Perhaps I confused the issues here. My issue isn't with ODBC. As I mentioned in my post, I was successful using ODBC (MS SQL, and Crystal's included sample reports).

Let me sum up the issue:

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.

 

[Naith]

If you have the Current Directory on and try to run your report in CR, or connect to the database, everything will be a-okay.

When you try to access the report via the browser, then the Current Directory will push the report on it's ass, because it forces the ODBC connector to make assumptions of the data source and report which are incorrect.

You haven't said whether you have this on or not yet.

Naith

 

[rustylee]

I assume when you say "Current Directory" you are referring to the menu item "Database -> Set Location", then clicking the "Same as Report" button. That is not the case here. The location path of the database is specified in the "File:" text box. The location of the database is not the same as the report location.

Also, I'm using the Crystal Reports Btrieve driver (p2bbtrv.dll), not ODBC (p2sodbc.dll).

Any ideas?

 

[lyanch]

I also have this problem with Oracle 9 and CE8. Although I can't prove it.. and Segate won't test it, mine is related to permission issues with a BDC and not actual database connectivity. When I run the pageserver in console mode instead of as a service, the reports started working. Definitely not a long term solution, but the only one I have right now.

Lisa

 

[rustylee]

Lisa,

What is "console mode"? Why would this not be a "long term solution" for you? Just wondering.

-Rusty

 

[lyanch]

Running in console mode is essentially running the pageserver as an application from a dos prompt. (Just copy the execution line from the CMC, change -service to -console and run from a dos prompt.)

The pageserver was not intended to run as a process, but is designed to run as a service. It generally is not as stable, and often requests a second logon from my users.

Here is a link to a whitepaper on this problem.. didn't help me but you never know..

http://support.crystaldecisions.com/communityCS/TechnicalPapers/cr_error_detected_by_db_dll.pdf

Lisa

 

[rustylee]

Lisa,

I loaded the pageserver at the command prompt, as you described here, and by golly, the reports run. I've been able to run simple reports up to reports with subreports with no problem.

I wonder why running it on the console works, but running as a service doesn't.

Anyways, thanks for the heads up.

-Rusty

 

[scriv1]

Hi Rusty. I don't know if you've already solved your problem or not, but we have been having our own little tussles with this one. I have found an article at Crystal Decisions that has been of some benefit to us... Try this URL...

http://support.crystaldecisions.com/communityCS/TechnicalPapers/cr_error_detected_by_db_dll.pdf

It may be of some help, or at least I hope so. We were running into the same problem with the error messages. We also received verification advice from Crystal Decisions Support to make sure the checkmark was off in the checkbox for "Use Indexes or Server for Speed" (in "Menu "File", "Report Options&quot, as well as making sure that it was also off in the same settings under "File", "Options", "Advance Options", "Database". With the check marks being on, there was a problem accessing the index (a problem with the cache according to C.D.). Once we took the checkmark off, we didn't get the "Error Detected by Database DLL" anymore.

Kent

 

[rustylee]

Thanks Kent.

I have been talking with them directly and they saying it may also have something to do with the account that the Page Server service is using. I'm not quite buying it because I am using the Administrator account.

I also looked at the document you referenced. Unfortunately, much if it deals with ODBC. My problem deals with Crystal Reports' so-call native Btrieve drivers.

The console mode works great. We may have to that direction.