Everything seems ok and working. Except when I attempt to create a new project in framework manager (10.2).
I name the project, click Ok, select the language, click ok, then I get the following error message
BMT-MD-0003 CCL-BIT-0005 A socket reported a communication error.
CAM_Connect=0xffffffff <errorDetail><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321 The GSKit function 'gsk_environment_init' failed with the error code '202'.</errorMessage><errorStack><errorCode>-
Has anyone seen this before?
Quote from: victorg on 23 Jun 2015 01:13:40 PM
Everything seems ok and working. Except when I attempt to create a new project in framework manager (10.2).
I name the project, click Ok, select the language, click ok, then I get the following error message
BMT-MD-0003 CCL-BIT-0005 A socket reported a communication error.
CAM_Connect=0xffffffff <errorDetail><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321 The GSKit function 'gsk_environment_init' failed with the error code '202'.</errorMessage><errorStack><errorCode>-
Has anyone seen this before?
Hi,
It sounds to me like an issue with the certificate authority - has Framework Manager been configured with the encryption keys of the Cognos BI server? Have these changed since FM was last configured?
What happens if you go into the Cognos Configuration for FM and save the configuration? Does it save successfully or do you get errors? If it saves successfully, does this then fix your issue above?
Cheers!
MF.
Hi,
Sorry for the late reply. It worked. I feel somewhat sheepish.
Thank you for your assistance.
Hi,
Can you plz let us know the steps you performed for rectifying this issue?
Plz help
VictorG, we are getting same error as you mentioned:
CCL-BIT-0005 A socket reported a communication error.
CAM_Connect=0xffffffff <errorDetail><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321 The GSKit function 'gsk_environment_init' failed with the error code '202'.</errorMessage><errorStack><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321
Your immediate help is required.
ShoMan
Quote from: shoman779 on 25 Nov 2015 07:11:05 AM
Hi,
Can you plz let us know the steps you performed for rectifying this issue?
Plz help
VictorG, we are getting same error as you mentioned:
CCL-BIT-0005 A socket reported a communication error.
CAM_Connect=0xffffffff <errorDetail><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321 The GSKit function 'gsk_environment_init' failed with the error code '202'.</errorMessage><errorStack><errorCode>-2113929065</errorCode><errorMessage>CAM-CRP-0321
Have you gone into the Cognos Configuration utility for Framework Manager and checked that the gateway URI and dispatcher URI are set to be the same as the gateway URI and dispatcher URI in your BI server instance? Have you saved the configuration and if so, does it generate the cryptographic keys successfully?
Quote from: shoman779 on 25 Nov 2015 07:11:05 AM
Your immediate help is required.
ShoMan
Immediate? Required? This sounds more like a demand than a request for help. Please read the forum etiquette rules here (http://www.cognoise.com/index.php/topic,24030.0.html), paying particular attention to point 2. Please be courteous to other forum members who help of their own free will and in their own time.
MF.
Sorry Boss I m new, next time I will be careful
We recently upgraded from 10.2.2 and I had a problem in the DEV environment publishing a new package so tried the same thing in PROD environment even though we will not be publishing from PROD. I had the same error as above and realized that I hadn't opened the 32 bit configuration tool and done a save since the install in the PROD environment. Once I opened the 32 bit configuration tool and saved, the problem was resolved. Thank-you MFGF.
The problem with the DEV environment was related to a particular model. http://www.cognoise.com/index.php/topic,29557.0.html
My issue still not resolved...............
Can somebody help............knock knock
Did you do what MFGF suggested?
Quote from: shoman779 on 02 Dec 2015 10:39:49 AM
My issue still not resolved...............
Can somebody help............knock knock
Can you tell us what you found when you looked into the suggestions I provided when you first asked the question? Did the URIs match the ones for the server component? Did the cryptographic keys generate successfully?
Can you tell us the answers to these questions? Knock knock...
MF.
Quote from: MFGF on 25 Nov 2015 07:33:18 AM
Have you gone into the Cognos Configuration utility for Framework Manager and checked that the gateway URI and dispatcher URI are set to be the same as the gateway URI and dispatcher URI in your BI server instance? Have you saved the configuration and if so, does it generate the cryptographic keys successfully?
MF.
I had the same issue and google brought me here. But to follow up with what you suggested here, I checked the configuration and yes the croptographic keys were generated successfully, and the gateway and dispatcher URIs are matched. But still I get this error in Framework Manager. Any help? Sorry, I made an account right away since this is the only thing that popped up when I tried to google for an answer.
Quote from: pixel8did on 16 Jan 2016 08:15:01 AM
I had the same issue and google brought me here. But to follow up with what you suggested here, I checked the configuration and yes the croptographic keys were generated successfully, and the gateway and dispatcher URIs are matched. But still I get this error in Framework Manager. Any help? Sorry, I made an account right away since this is the only thing that popped up when I tried to google for an answer.
Hi! If you managed to generate the crypto keys successfully then there's something else going on. My guess would be a mismatch between the build of Framework Manager and the build running on the Cognos server. Firstly, check they are the same overall version (eg 10.2.2, 10.2.1 etc), and if not, replace your FM install with the same version as the Cognos server. If they are the same overall version, check what patch level FM and the server are running - it's quite possible the server is running with a fix pack installed and FM needs the same version fix pack. To check the versions on each, look for a file called cmplst.txt in both your FM install and in the Cognos BI server install, then use the following IBM article to find the build:
http://www-01.ibm.com/support/docview.wss?uid=swg21343355
Cheers!
MF.
Hi, could not get Framework Manager V10.2.2 working with Cognos Server V10.2.1 not matter what (with or without Fix Pack).
Was getting that crypto error while saving the FM Configuration as well as "can not connect to service..." while testing my Datasource from within FM.
Problem went away after desinstalling FM V10.2.2 and installating FM V10.2.1 + saving the Configuration.
Quote from: jfm2nice on 24 Feb 2016 09:57:05 AM
Hi, could not get Framework Manager V10.2.2 working with Cognos Server V10.2.1 not matter what (with or without Fix Pack).
Was getting that crypto error while saving the FM Configuration as well as "can not connect to service..." while testing my Datasource from within FM.
Problem went away after desinstalling FM V10.2.2 and installating FM V10.2.1 + saving the Configuration.
Hi,
As above, the major versions of BI Server and Framework Manager need to be matched. You can't use a 10.2.2 version against a 10.2.1 version - either way around. Matching the versions then making sure the fix pack levels are the same is the way to go :)
MF.
Quote from: MFGF on 23 Jun 2015 02:38:54 PM
Hi,
It sounds to me like an issue with the certificate authority - has Framework Manager been configured with the encryption keys of the Cognos BI server? Have these changed since FM was last configured?
What happens if you go into the Cognos Configuration for FM and save the configuration? Does it save successfully or do you get errors? If it saves successfully, does this then fix your issue above?
Cheers!
MF.
Just wanted to thank you for this solution.