Error Detected by Database DLL

[leonbutler]

I'm currently using Crystal Reports 8.5 and Crystal Enterprise 8.5 with a Progress 9.1c Database.

Recently some of the reports which I publish to CE will not schedule or view - each time I attempt to open them, through CE, the error "Error Detected by Database DLL" is displayed. The strange thing is that these reports are fine within the CR Designer, but not through CE.

It's not all reports that this happens on - it also seems complexity isn't an issue either - some of the reports can take 4hrs to refresh (in CR) others 10mins....but in CE they don't run.

I've checked support.crystaldecisions.com and read the help files on this particular error, but to no avail.

Is there anyone out there having or has had the same problem on a progress DB?

 

[tmobile]

Leon,
We have seen some of these messages and have linked it to the same issues as you. What cleared up many (but not all) was to install ALL of the recent hotfixes from Crystal Decisions.
We have one last issue we are fighting, our reports are running in Designer, and in ePortfolio, but users on our intranet using their IE browser and the CR ActiveX viewer see failed reports. $%#@^^%$#!!

 

[leonbutler]

I've now downloaded the afforementioned updates from Crystal, but to no avail (aside from the patches fixing the bugs they were supposed to ;-)).

I've tried publishing the reports again but still get the Database DLL error message.

Any more ideas?

 

[lyanch]

Have you checked the reports in designer mode on the enterprise server itself? Sometimes that will highlight a server dll problem.

Lisa

 

[leonbutler]

Opening the reports on the server was one of my first points of call.... I've opened all the reports that are demonstrating the problem in the designer on the server itself. I've verified the database (countless times) and checked the ODBC links are working. I've refreshed the report then saved (with data) and tried refreshing and then saving, but without data.

I've published by Saving to APS, publishing wizard and using the CMC, but still to no avail.

What I have noticed since applying the patches is that not all reports throw a DLL error - some of them load the ActiveX viewer, appear to be retrieving the report but never actually display the report (the status bar indicates done - but the backdrop remains grey and not white like it would be if no records were selected).

 

[Burgovision]

When you opened the reports on the server, were you using the same profile which the crystal services run under?