cancel
Showing results for 
Search instead for 
Did you mean: 

BOE using Oracle 32 and 64 bit drivers side-by-side (Windows 2008)

former_member183781
Active Participant
0 Kudos

Baseline 4.0 (FP3)

We have installed BOTH the 32 and 64 bit Oracle Clients on the Windows 2008 (64 bit) servers that host our BO BI 4.0 (FP3) environment.

Had to install BOTH because the 64-bit CMS service (and others) need the 64-bit Oracle driver, but the 32-bit CrystalReports2011Processing service still needs the 32-bit Oracle driver.

Environment variable on Test servers:

ORACLE_HOME=C:\oracle64\product\11.1.0\client_1
ORACLE_HOME32=C:\oracle\product\11.1.0\client_1
PATH=C:\oracle64\product\11.1.0\client_1\bin
PATH32= C:\oracle\product\11.1.0\client_1\bin
BOE_USE_32BIT_ENV_FOR=ORACLE_HOME,PATH

The content is all in the Crystal Reports XI (R2) / 2008 / 2011 format - NOT the new CR for Enterprise 4.0 format.

CMS/AUDIT starts OK connecting to Oracle. (CMS is 64-bit service)

Crystal Reports can be run and viewed OK when SCHEDULE and View INSTANCE is used. (AdaptiveJobServer is 64-bit service)

Reports FAIL with the errors below when run as VIEW-ON-DEMAND...or when REFRESHING a Successful Crystal Report INSTANCE from within the Crystal Viewer in CMC or Launchpad. (CrystalReports2011Processing service is 32 bit)

Error message:
-----------------

The viewer could not process an event. Error in File ApplicationRoles:
Failed to load database information. []
---- Error code:0 [CRWEB00000119]

We have been around-and-around on this for a couple of weeks with SAP support (both "off-shore" and Vancouver) - and have worked with  following SAP NOTES...

1674528 - Unable to start the CMS in BI 4.0

Resolution

In BI 4.0, in order to connect with CMS database it is required to have64-bit client installed on the server.

If you have also installed 32-bit Oracle client for Crystal reports 2011 along with the 64-bit Oracle client, Check if the following Environment variables are set properly:


ORACLE_HOME=<64-bit version of the Oracle client>
ORACLE_HOME32=<32-bit version>
TNS_ADMIN=<64-bit version>
TNS_ADMIN32=<32-bit version>
BOE_USE_32BIT_ENV_FOR=ORACLE_HOME,TNS_ADMIN

If the problem still persists, remove ORACLE_HOME and ORACLE_HOME32 and restart the Server machine.

Start the SIA, the CMS.exe will come up

1679341 - Unable to View Crystal Reports after migration from BO XI R2

We appear to have completed all of these suggestions OK - but without any change of state.

Anyone else having this issue...? Anyone got other suggestions for us to try...?

Thanks in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Mark,

just a quick spot:

You didn't mention the TNS_ADMIN and TNS_ADMIN32 variables were set like mentioned in the KBA.

--

Thomas

graham_sturmy
Active Participant
0 Kudos

Hi Mark,

  If the above steps don't work (and I am not familiar with it to say if there is a problem with your implementation with it) then you might need to get creative.

The problem here is that the PATH need to include the .dlls for both the 32 and 64 bit .dlls.  A process (assuming were ignoring the steps above) would simply pick up the first .dll it finds with the appropriate name).

  So - here's my idea.  Create a second SIA on the machine with NO servers.  Add the

CrystalReports2011Processing service to this new SIA.  Now - we need to ensure that the first SIA's PATH points to the 64 bit drivers and the second sia's path (running the CrystalReports2011Processing service) points to the 32 bit drivers.

   In theory you should be able to do this by

  1) Removing the Oracle libraries from the System environment variable

   2) Running each SIA under a different user account

   3) Adding the PATH to the appropriate Oracle .dlls to the appropriate USER environment path (rather than the system one).

Now when you start the service it will pick up the user environment of the user that it is defined to run on and it should pick up the appropriate dlls.

  As I say earlier - they may be a much more elegant way to do it - maybe some variation or addition of the KBA that you referenced - but hopefully it's an alternative.

Regards,

Graham