I Thought *You* Silenced the Guard
Jul. 30th, 2013 05:28 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
billroperWhen we install our Server product, the DLLs for Essbase integration are installed, which include a number of DLLs for connecting to an Oracle database.
When we have a user who wants to use our Extended Analytics feature to connect to an Oracle database, we tell them to install the Oracle OLE DB DLLs.
Some of the DLLs that are installed by these two processes in the two different directories have the same name and are, in theory, the same DLL. However, there is no guarantee that the user has selected the right version of the Oracle OLE DB DLLs to install on his server machine, where -- in this case -- "right" can be translated as "the same version as were installed for Essbase integration".
If you run the Essbase integration, everything works.
If you run Extended Analytics, everything works.
If you run them both, hilarity ensues, at least if you have not managed to successfully match the DLL versions between the two installs.
Oops!
When we have a user who wants to use our Extended Analytics feature to connect to an Oracle database, we tell them to install the Oracle OLE DB DLLs.
Some of the DLLs that are installed by these two processes in the two different directories have the same name and are, in theory, the same DLL. However, there is no guarantee that the user has selected the right version of the Oracle OLE DB DLLs to install on his server machine, where -- in this case -- "right" can be translated as "the same version as were installed for Essbase integration".
If you run the Essbase integration, everything works.
If you run Extended Analytics, everything works.
If you run them both, hilarity ensues, at least if you have not managed to successfully match the DLL versions between the two installs.
Oops!