Crystal Enterprise 9 Reporting Woes

[cryogenx]

Ok i have "Uploaded" several reports to my CE9 server.. all of which show up in enterprise. when i try to run this specific report i get the following.
============================================
"Failed to load database information. File 17f361614ee163.rpt."


Unable to retrieve Object.
"Failed to load database information. File 17f361614ee163.rpt."
============================================

This is what i have for database info in the management area:

Custom Database ( There was no reference in the report )

Database Driver: ODBC
Server: HERNREC ( I have ODBC connection setup for this )
Database: OPR ( This is the name of the SQL Database )
User: <<username>>
Password: <<password>>

I can seem to figure out why this Report refuses to run.

Any help would be great.

 

[lyanch]

Have you tried running this report logged on to the server as the "user" that the pageserver runs under? It sounds like the pageserver can't find the ODBC driver. It could be because it isn't a system DSN or other permission problems.

 

[cryogenx]

I have it setup as a system DSN.

how would i

"running this report logged on to the server as the "user" that the pageserver runs under"

Thanks

 

[lyanch]

For instance, if the pageserver runs under the system admin account (recommended by BO),

Log on to the server as the system admin and try to run the report from the designer on the server itself.

To find out what account the pageserver runs from, in the CCM on the server, right click on the pageserver and look at properties (you can also look in the system service panel).

If the admin can run the report okay, then it is definitely a server problem, otherwise it is a server local rights problem.

Lisa

 

[mmussel3]

cryogenx,

I recently ran into the same problem with a brand new Crystal 9.0 installation.

Have you tried rebooting the machine since the install? The other thing that seemed to work was copying the 4 .dll files form the \Tools\Extras\ folder in the Crystal Enterprise 9 media into the \WINNT\System32 folder, and rebooting the machine.

I'm not sure whether the DLLs were related or not, but the combination of the two actions fixed the problem.

 

[lyanch]

HAving just ran into this problem again with an old report that they wanted back.. and the database moved.. the problem was my ODBC driver wasn't set up correctly on the server.

Except for the report file, I had the exact message.

Lisa