Seagate Crystal error

[ehawkins]

We get the following Seagate Crystall error when trying to print out of Crystal 7: The library 'PdSODBC.dll' cannot be found. Continue to open report for viewing only.

The software is ran on "Windows Advance Server" using terminal server as a client.


ehawkins@vom.com

 

[kenhamady]

Where is Crystal installed?
What version and edition are you using.

It is looking for either Pdsodbc or p2sodbc (the second one is the 32 bit version, same error message). Also, you may be running the standard edition and the report was designed on the professional edition which has more ODBC support.


Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal

 

[ehawkins]

We are running Crystal 7 inside a 32 bit application called ReMACS (Accounting software for fast food restaurants). ReMACS was developed in Delphi 3 and we are using Delphi VCL to embed the Crystal reporting engine into ReMACS. If we run ReMACS stand alone Crystal reporting engine has always worked like a champ. We are now testing running ReMACS ASP with the hosting by Window 2000 Adv Server and Terminal Server client for the remote connection. ReMACS works great but Crystal return the error and locks up the connection.

Thanks for your first response
Ed Hawkins
ehawkins@vom.com

 

[kenhamady]

There are too many layers here for me to sort it out. My guess is that the ODBC connection (for CR) needs to be local, and isn't working remotely. As a test, does a report with saved data run OK? This will help you determine if it is the report engine or the database connection that is choking. Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal

 

[ehawkins]

Ken,
We tried running a report with the data save in the report and got the same error say pdsodbc.dll not found. I also tested running the report on the Win2000 Server ( no terminal server ) got the same error.

I would appreciate you advise

Ed Hawkins

 

[kenhamady]

>>If we run ReMACS stand alone Crystal >>reporting engine has always worked like a >>champ

So this isn't true when run on Win2K Server standalone? Is the ODBC configured correctly on the server? Is this DLL on that box and registered correctly? Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal

 

[ehawkins]

Ken,

Remacs printing out Crystal has always run like a champ on NT4
We have been using NT4 servers as workstartions in Taco Bells and are now testing it with Win2k Advanced Server.
We have yet to get past the Crystal error on Win2K server.
We have tried running Remacs thru Win2k Terminal Server
Then running Remacs directly on the Win2k server using the server as a workstartion. Same problem in both situations.
I have configured the odbc DSN 100s of times for Remacs in NT4 and Win2k Advanced. Should I be looking in Crystal for some odbc settings. Remacs runs great as an ASP using terminal server. Better than standalone in the restaurants so we are anxious to get past the crystal error.

Thanks again for your time

 

[kenhamady]

Nothing obvious jumps out at me.
This error may not have to do with the DLL itself. It will actually be P2Sodbc if you are using 323 bit Crystal, but they generate the same error.

I assume that you have confirmed that the P2sodbc.dll is in place and registered? Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal

 

[PDog]

I'm having the same problem. OEM version of Crystal reports 6 running on Windows 2000 Adv Serv running terminal services. Checked the Seagate Software site for a fix - no luck. Applied all the service packs and updates from Microsoft. No fix.

I'll check with the OEM tomorrow.

Paul

 

[PDog]

Fixed the problem. Here is the tip:

>> Copy all the .DLL files from the CRYSTAL directory to the
>> SYSTEM32 directory.
>>
>> CORRECTION STEPS:
>>
>> 1. Open Windows Explorer and locate the \\CRYSTAL directory.
>>
>> 2. Select and copy all the .DLL files to the \WINNT\SYSTEM32
>> directory.

It worked for me!

hth,

PDog