CCL-BIT-0005 A socket reported a communication error

[roxsap]

Hi Everyone!

I was able to add a data source already using Cognos Administration. Now I have to create a Framework Data Model, but encountered an error when I clicked "Create a new package".

Error states:
CCL-BIT-0005 A socket reported a communication error. CAM_Connect=0xfffffff4 <errorDetail><errorCode>-12</errorCode><errorMessage>CAM-CRP-0026 The underlying socket: '127.0.0.1:9300' returned an error.</errorMessage><errorStack><errorCode>10061</errorCode><errorMessage>Could not connect the socket, errno: 0x274d(10061)</errorMessage></errorStack></errorDetail>

Some notes:
1. Firewall allows port 9300
2. External dispatcher URI: <ipadd>:9080/p2pd/servelet/dispatch

I  believe FM should be using 9080 instead of 9300. But I do not know how to edit it since the one who implemented our systems says we do not use Cognos Configuration to run Cognos BI. Instead, we use Websphere Application Server (WAS).

I hope someone could help me. Thank you in advance. :)

[bdbits]

Unless your admins have overridden the defaults, it should be port 9300. Why do you think it would be 9080?

I am assuming FM is installed on your computer and you are accessing Cognos on another server. There is a Cognos configuration utility in the folder in which you installed FM. It should have added a start menu item for you. You need to run this and set your gateway and dispatcher so that FM knows where to find Cognos and communicate with it.

This is all covered in the install guides.
http://www-01.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.2.doc/c_install_fm.html%23Install_FM?lang=en

[roxsap]

Unless your admins have overridden the defaults, it should be port 9300. Why do you think it would be 9080?

I am assuming FM is installed on your computer and you are accessing Cognos on another server. There is a Cognos configuration utility in the folder in which you installed FM. It should have added a start menu item for you. You need to run this and set your gateway and dispatcher so that FM knows where to find Cognos and communicate with it.

This is all covered in the install guides.
http://www-01.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.2.doc/c_install_fm.html%23Install_FM?lang=en

Our Cognos BI and Cognos FM are installed on the same server. I  am accessing it using remote desktop. The Set-Up that we have uses Websphere Application Server (WAS) to run Cognos. As what I learned from the team who implemented this, we do not use cognos configuration to start cognos.

Based on what you said, Gateway URI and Dispatcher URI under the Gateway Settings of Framework Cognos Configuration should be aligned with the values stored in Cognos Configuration.

However, I could not access Framework Cognos Configuration because of another error:
A fatal error occurred. Unable to run  the application.
An exception occurred.
java.lang.UnsatisfiedLInkError: JCAM_Crypto_JNI (C:\Program Files\IBM\cognos\c10_64\bin64\JCAM_Crypto_JNI.dll is not a valid Win32 application.)


Now my concerns/questions regarding this are:
1. How would I know the Gateway URI and Dispatcher URI without accessing the IBM Framework Cognos Configuration?
2.  Is there a way to change the settings without accessing IBM Framework Cognos Configuration?
3. If I change the settings in Framework Cognos Configuration, would it be able to reflect the changes given our WAS set up?


Thank you! :D

[bdbits]

Decisions made when Cognos was installed determine the gateway and dispatcher URIs. You have to either go by what that person said they set up, or look it up yourself in Cognos configuration. You do not start Cognos services with Cognos configuration but that is where a lot of information that determines how Cognos runs is set up. Likewise, configuration has to be correct for FM to function. Configuration parameters are normally stored in encrypted form, and that error is referencing part of the encryption components.

Do you have local administrator rights on the machine you are RDPing? This is required, as is stated in the install guide. This could explain the error. That or something in the installation is corrupted and a reinstall of FM might be worth a shot.

Personally I do not recommend running FM on the Cognos server. There are not a lot of good reasons to do it that way, in my opinion. You would be better off installing it on your computer (or a VM separate from the Cognos server), and configuring it to use your Cognos server. I recognize this may be outside your control, but if possible I would try a local install.

[roxsap]

Personally I do not recommend running FM on the Cognos server. There are not a lot of good reasons to do it that way, in my opinion. You would be better off installing it on your computer (or a VM separate from the Cognos server), and configuring it to use your Cognos server. I recognize this may be outside your control, but if possible I would try a local install.

Thanks for the tip. Installed Framework Manager on my laptop. It works now! Thank you for help.


God bless you :)

[bdbits]

You're welcome. Glad it works now.

God bless you, too.

[Ian Leslie]

Hi, I was getting the same error on a Cognos Express Install 10.2.1 FP3, the resolution I found which worked for me was to locate the cogstartup.xml file located in the FM Client Install configuration folder and change the instances where the url was set to look at Port 9300, in this case there were 9 places to 19300 (standard CEX port), I also changed to point to the FQDN as well. Hope this helps anyone else who has the same issue. Whether this is an issue with FP3 I don't know, but FM is now working as expected.