Failed to open the connection. Details: [Database Vendor Code: 12154].

[vasana_perera]

I have installed Crystal reports server 2008 VI on a Windows 2008 64bit OS. I have added SQL server and Oracle reports through CMC. I then installed Oracle 10g client 32bit on the server and created and tested the required DSNs using ODBC 32bit. All the testings are successfull.

Now when I try to run my Oracle report through CMC it prompts for the parameters and when I enter them and click ok, gives me the following error:

Failed to open the connection. Details: [Database Vendor Code: 12154].

I have the same exact setup on a different server which has a 32 bit windows 2008 server OS and could run the same reports through CMC.

Is there away to fix this in the 64 bit OS?

I did a yahoo search and someone had a similar problem with Crystal RAS and Oracle.

And there is mentions that this is an issue with 32 bit ODBC drivers on 64bit wondows OS.The parentheses in the default file location, C:\Program Files (x86), causes problems with the ODBC driver and the workarouns in re-installing Crystal RAS on a different folder.

Full description is at (http://www.tririga.info/)

Is this the case with Crystal report server 2008 VI? I already got users using the InfoView to run SQL reports and doing this will have to put the application offline atlease for a say.

Any help is greatly appreciated.

[Former Member]

Vasana,

Resolution: Failed to Open the Connection.

First:

If the Crystal Report is using 32-bit version of Microsoft ODBC then the Window 2008 server must also have 32-bit version of Microsoft ODBC. The 32- bit version of Odbcad32.exe is located in the %systemdrive%\Windows\SysWoW64 folder.

On the Windows 2008 server, execute Odbcad32.exe by clicking start and run and entering the following: C:\Window\SysWow64\ODBC32.exe.

Then:

The Windows 2008 server ODBC Data Source Administrator must have the same System Data Source Server and Database Names that is used to run the Crystal Report.

e.g. Crystal Report points to server ABC and database EFG (ABC_efg); then the ODBC connections on the Windows 2008 Server must also point to the same server ABC and database EFG (abc_efg) listed.

[Former Member]

Hi Vasana,

This is a bug with Oracle itself as it cannot resolve if there is parenthesis in the path where software is installed. Workaround is to install software in a folder where there are no parenthesis.

Or path Oracle10g with following

Windows 32-bit

9.2.0.7.0 Patch 6: Apply Patch 4928723 or later

10.2.0.1.0 Patch 4: Apply Patch 4923768 or later

10.2.0.2.0 Patch 5: Apply Patch 5383042 or later

10.2.0.3.0: Apply Patch 5337014 or later

Windows 64-bit AMD64 and INTEL EM64T

10.2.0.1.0 Patch 4: Apply Patch 4923787 or later

10.2.0.2.0 Patch 5: Apply Patch 5388871 or later

10.2.0.3.0: Apply Patch 5337014 or later

If possible, use a version of the Oracle software that contains the fix for Bug 3807408

[vasana_perera]

I installed patch 4923768 , still it does not work.

[AKHUMBI]

May be of some help

Regards

Ashwini

[vasana_perera]

I tried the junction suggession, but it did not work. So far I have applied Oracle client patch and did the junction and still no luck.

Next one I have is to re-install the application in a different folder. I will do more research before doing this, cos this is a pain to do.

[AKHUMBI]

Hi

Refer the "Oracle connectivity issues", in CR 2008 server v1 release notes (page number 18)

http://help.sap.com/businessobject/product_guides/crs2008V1/en/crs_08_v1_releasenotes_en.pdf

This should solve your issue

Regards

Ashwini

[vasana_perera]

I was able to fix this by installing the latest Oracle 32 bit client (10.2.0.3.0). It seems like 32 bit client 10.2.0.1.0 is not compatible with Windows server 2008 64bit.