Unable to start Cognos Configuration after upgrading to 10.1.1 FP1

[santoshtalks]

Hi All,

After upgrading my Cognos BI software from 10.1.1 to 10.1.1 FP1, I am seeing below error while trying to open Cognos Configuration tool:

A fatal error occured. Unable to run the Application.
An exception occured.
java.lang.UnsatisfiedLinkError: JCAM_Crypto_JNI (D:\Program Files\ibm\cognos\c10_64\bin\JCAM_Crypto_JNI.dll is not a valid Win32 application.)
You should re-install the software.

[MFGF]

It looks like one or more of the files were corrupted when copying them across during the install. If you look at the transfer log, does it report any errors during the unpack/copy process? As the final part of the message suggests, you need to run the install again.

Good luck!

MF.

Sent from my iPad using Tapatalk HD

[santoshtalks]

Thanks MF. Even after trying couple of times the issue exists.
I have raised a ticket with IBM for this.

[Grim]

Let us know what the results are.

Kinda sounds like you had a bad DLL. Hopefully it was just your install and not the actual FP1 download.  :o *yikes*

[MFGF]

What do the transfer logs for the install show? Any clues as to why the install isn't copying over?

MF.

Sent from my iPad using Tapatalk HD

[santoshtalks]

The transfer logs suggest the new dll did get copied over successfully. It looks like there was issue with the dll itself packaged along with FP1 release. I will let you know what happens with the bug raised with IBM.

[MFGF]

The transfer logs suggest the new dll did get copied over successfully. It looks like there was issue with the dll itself packaged along with FP1 release. I will let you know what happens with the bug raised with IBM.

Yikes! That's a little worrying! Please do let us know how this turns out.

Cheers!

MF.

Sent from my iPad using Tapatalk HD

[Grim]

Yikes! That's a little worrying! Please do let us know how this turns out.

Cheers!

MF.

Sent from my iPad using Tapatalk HD

Yes please do as I'm about to install FP1 soon. I'd rather wait if they are going to "re-release".   :-\

[EarthDog]

I have it installed since release with no problems until now...

any news?

[luisventura]

I'm suffering the same problem...

Did you have any information from IBM?

[sir_jeroen]

Just to be sure: Did you install the 32-bit Fixpack or the 64-bit Fixpack? The install location indicates it's the 64-bit, so use the x64 FP1

I've done multiple x64 installs after the FP1 release, and i've never had this error.

[luisventura]

I installed the x64 FP1, as my server is x64. Anyway, as I have x86 components installed too (Transformer and FM) I've asked support if I'd need to install the x86 Fixpack too.

I'm sure the fixpack misconfigured my servers, as I've unistalled it in one of them, and Cognos has started working again.

I've opened a PMR with IBM in order to get the Fixpack installed in my servers, but I've got no response yet.

[EarthDog]

I am also having both 64bit and 32 bit components as you BUT i ahave them installed in different directoriies. That is giving me 2 configurator applications. the 64 bit has the full options for the server and the 32 bit only the config that FM needs

Do you have them installed under the same directory?

[luisventura]

I have them installed in separate directories two.

I've just tested the x86 Cognos Configuration app, and it's working. I'm thinking about applying the x86 FP1 to the server, and see if it helps, but I'd like to wait for the Support answer (they are being quite slow answering...)

[Rahul Ganguli]

Hi All,

I have recently installed FP1 in Windows as well as Linux platform. Both are working fine. (Both the install are 64 bit)
In Windows machine I have 32 bit components installed too. Everything working smooth.

Regards,
Rhaul

[Jaro2]

I had the same problem, on a windows server 2K8 (64) with 10.1.1 (64 bit).

The fixpack worked well on the test-machine but not on the acceptation-environment. On this machine I had tested with TM1 once and had left a value in the environment viariable 'PATH'; the path to the TM1-installationpath. After removing this string from the variable I could start cognos configuration again and eventualy cognos...

I figured this out by running the cogconfig.bat in the bin64-directory. It gives you somewhat more information about the error....

[luisventura]

It did the trick!

I have added the 64 bits jre directory to the System Path and now it's working.

Thank you very much for your help!

[Jaro2]

It did the trick!

I have added the 64 bits jre directory to the System Path and now it's working.

Thank you very much for your help!

That's the other way around, but it shows that the startup-scripts do something with this variable. I think it's strange that they have changed this routine with this fixpack without apparantly knowing it....

In any case, I reported it to IBM (together with a single signon via ADS problem, see other topic) and they did not come up with a solution for it.