Hi,
I just installed 8.3 version and did the configuration setup.
The server is running and and I can connect.
But when I am login to the Framework manager, it give the error message
CAM-AAA-0064
The function 'CAM_UnprotectData' failed.When I click details button on the error message it displays below
Quote<errorDetail><errorCode>-13</errorCode><errorMessage>CAM-CRP-0157 Unable to complete a call to the cryptographic provider's unwrap function.</errorMessage><errorStack><errorCode>-13</errorCode><errorMessage>CAM-CRP-0285 Unable to find an appropriate Common Symmetric Key (CSK) to decrypt the data.</errorMessage></errorStack></errorDetail>
I am using MS Active directory.
If am using with Anonymous login it works fine.
Any idea what went wrong?
Thanks in advance...
Solved!
There was multiple version.
The URL was still pointing to old version, changed to new location
It is working now fine !!!
Quote from: ipmurali on 10 Aug 2008 03:16:00 AM
Solved!
There was multiple version.
The URL was still pointing to old version, changed to new location
It is working now fine !!!
Which URL you are talking about ? We have two instances of Cognos 8 on the same server. and the same error 'CAM_UnprotectData' failed is seen after I enter the user name and password. We have temporary solution as restarting the Web Publishing Service. After re-start it works fine in one of the two environments but the second one still shows error
We had the same scenario. Had to install 10.2.1 and 10.2.2 versions in the same server, on different directories.
The error CAM-AAA-0064 The function 'CAM_UnprotectData' failed. with the detail 'CAM-CRP-0157 Unable to complete a call to the cryptographic provider's unwrap function' ocurred.
The possible cause: different applications on IIS 7 acessing different cognosisapi.dll, but in the same Application Pool.
The solution: separate the Application Pools. It's not possible as Virtual Directories. So, you'll have to convert the cgi-bin virtual directories in Applications.
Separating the 2 Cognos versions on 2 different Application Pools apparently resolved the issue.
See ya.
Igor Andrade