Missing database DLL

[Wendell]

In the process of the SysAdmin moving our ASP code and Crystal Reports (and pointing to the Production SQL database) from the development environment to the production environment, the Crystal Reports quit working and began providing the following:<br><br>cpeaut32 error '800a5034' <br><br>Can not find database DLL. <br><br>Any help in resolving the problem would be appreciated.<br><br>Thanks,

 

[Wendell]

barn wrote me with the following suggestions:<br>First thing to check is that the ODBC driver (I assume you to be using ODBC) on the server is the same or later version as the one on the development machine and that it is identically configured to the development ODBC driver.<br><br>Next, be certain that the Crystal installation on the production server is the same or greater version as on the development machine.&nbsp;&nbsp;Crystal has always been bad at introducing incremental fixes on the order of x.xx.xxxb<br>that break the version x.xx.xxxa.&nbsp;&nbsp;Best bet here is to hit their website and pull down the latest updates for your major.minor version of Crystal and install it on both machines.<br><br>Path considerations can be critical, particularly if you are using a DSN-less connection.&nbsp;&nbsp;While I'm certain you've already checked any path structures in your ASP code, it still (always &lt;grin!&gt bears mention.<br><br>One last thing to check is to examine the reports for the database location and be certain that location is viable and visible from the production server (this one ran me ragged for a week one time.<br><br>And, finally, have the network admin check permissions for the directories involved.&nbsp;&nbsp;If the ID associated with the report engine (the operator, so to speak) does not have access, you can get the same error.<br><br>Wendell:&nbsp;&nbsp;I haven't gotten it to work yet, but we haven't run throught the above either.....&nbsp;&nbsp;More to follow??<br>

 

[johnk]

Wendell,&nbsp;&nbsp;It looks like your problem is specific to your database driver.&nbsp;&nbsp;Can you tell us what driver you are using? <p>John Kisner<br><a href=mailto:jlkisner@jlkisner.com>jlkisner@jlkisner.com</a><br><a href= > </a><br>

 

[Wendell]

Interim answer:<br>Seems there were several problems (and maybe more yet to be discovered!).&nbsp;&nbsp;One was an oleaut problem with reporting, one was there had been a change made to SmartViewerActiveX.asp to work with SSL and someone else had decided that using SSL wasn't necessary and changed the rest of the asp config back <b>EXCEPT</b> SmartViewerActiveX.&nbsp;&nbsp;