Crystal Reports and p2sodbc.dll

[sanjig]

I Installed full version of crystal reports 8.5 on a machine with windows 2000.And I could not run some of the crystal reports that were using ODBC connection.when I installed Crystal reports8.5,it put p2sodbc.dll version 8.5.0.72 in winnt\system32.But if i put p2sodbc.dll version 7.0.0.134 in winnt\crystal ,these reports run fine.
so now my reports using ODBC runs fine with :
p2sodbc.dll version 7.0.0.134 winnt\crystal
p2sodbc.dll version 8.5.0.72 winnt\system32
My problem now is :
I installed full version of Crystal reports8.5 on Citrix Metaframexpa for windows future release-3.and I have
p2sodbc.dll version 7.0.0.134 winnt\crystal
p2sodbc.dll version 8.5.0.72 winnt\system32
and in my profile I have
p2sodbc.dll version 7.0.0.134 winnt\crystal
p2sodbc.dll version 8.5.0.72 winnt\system

I cannot run the reports with ODBC.I get the error:
error detected by database dll.
Any help will be appreciated
jmodi@k-and-s.com

 

[jdemmi]

My guess is that there is a conflict created by having both versions of the p2sodbc.dll in the systems's path. Check your local PC path to see which p2sodbc.dll is being used (the folder listed "first" in the path). My guess is that the 8.5 version is located in the folder listed first in the path. If it's not it should be. (I would not use the 7.0 version of the dll with an 8.5 report even if it appears to work.)

Bottom line, you should only need the 8.5 version on both your PC and on the Citrix box. So, delete all copies of the 7.0 version from the Citrix box. (Right down all the places it exists before doing so if you're a little leary). Then place the 8.5 version in the WINNT\SYSTEM32 folder on the Citrix box making sure that the users have full control to this file. This should work.

(In all my Crystal\Citrix installs I leave the DLLs where Crystal places them during the install, grant users full control to them, and then copy all of them to the SYSTEM32 folder of the Citrix box, and I never seem to have any DLL related issues)

Good luck.

 

[sanjig]

Thanks jdemmi

Can you explain little bit in detail as how to check the local pc path to see which p2sodbc.dll is used.also the databases from which i retrieve data uses sql-server6.0.
On the test server I have:
p2sodbc.dll version 7.0.0.134 winnt\crystal
p2sodbc.dll version 8.5.0.72 winnt\system32
if i delete :
p2sodbc.dll version 7.0.0.134 winnt\crystal

the reports using ODBC don't work.SO looks like the crystal reports is using
p2sodbc.dll version 7.0.0.134
even when I have
p2sodbc.dll version 8.5.0.72 winnt\system32

Also I have heard that you should have p2sodbc.dll only in one of these two folders(crystal\system32) and not both

 

[jdemmi]

You can check the path statement several ways, 2 of the easiest are.

1. From a command prompt type PATH and hit enter.

2. From Control Panel go to SYSTEM. Click on the ADVANCED tab and then click on the ENVIRONMENT PATH button. In the bottom pane (SYSTEM VARIABLES) locate the PATH Variable. You can view it there or edit it so you can copy\paste it somewhere to make it easier to read.

The p2sodbc.dll that Crystal is using SHOULD BE located in the folder which appears first in the path statement.

For example, if your path statement reads:
C:\WINNT\SYSTEM32\;C:\WINNT\CRYSTAL then the Crystal SHOULD BE using the dll from the SYSTEM32 folder.

The fact that the report stopped working when you removed the DLL from the Crystal folder tells me that Crystal is looking for the DLL in the CRYSTAL folder and not the SYSTEM32 folder. The version is not really the problem. To confirm this, place the 8.5 version in both the CRYSTAL and SYSTEM32 folders and see if the report executes.

You are correct in that the DLL should only be located in 1 of the 2 folders IF YOU ARE OPERATING IN A DESKTOP (2000, XP, etc) ENVIRONMENT. But as I stated before I have had the best luck in placing the DLL in BOTH locations when I am operating in a CITRIX environment.

 

[sanjig]

Thanks Jdemmi for your advise.In the Path I don't see anything for ODBC.

 

[zemp]

Try Verifying your Database from the Crystal IDE Database menu. You can aklso try resetting the location. It may be that the stored path, used by crystal, is now invalid.

zemp