
General Notice: No events within the next 45 days. |
Author |
Message |
jayesh_deshpande Senior Member


Joined: 21 Jul 2009
         Posts: 75

|
Posted: Mon Jul 12, 2010 8:05 am Post subject: Unable to open a socket to talk to CMS Error |
|
|
Hi,
While trying to login to Infoview/Cmc I am getting following error:
Error: Unable to open a socket to talk to CMS ps5990:6400 (FWM 01005) null
I am not sure whats wrong here. I also checked CCM and found that SIA is running. However I was not able to login using Manage Servers.
thanks in advance for your reply. |
|
Back to top |
|
 |
Shane.Graser Forum Member


Joined: 28 Jun 2010
        Posts: 19 Location: Newport News, VA

|
Posted: Mon Jul 12, 2010 10:14 am Post subject: Re: Unable to open a socket to talk to CMS Error |
|
|
Here is a possible solution...
Either the port number given for Central Management Server at the time of login is incorrect or the port is already in use by another application.
Make sure to give correct port number for CMS at the time of login. The CMS server default port is 6400.
In the "System" field in the authentication box, type in "server:port" (without " "). For e.g., if it is default, you may either type myservername or myservername:6400
In order to change default port number at which the CMS server runs, do the following steps:
* Stop the Server Intelligence Agent (SIA) from Central Configuration Manager (CCM).
* Right Click > Go to Properties > Startup tab.
* Click on the Central Management server > Properties tab.
* Change the port number to some other number which is not in use by any other application. Click OK.
* Apply > OK.
* Start the SIA.
__________________________
Shane Graser
www.datamanagementgroup.com
“Transforming Data Into Information” |
|
Back to top |
|
 |
Lugh Forum Enthusiast


Joined: 16 Jul 2009
         Posts: 1155 Location: Herndon, VA

|
Posted: Mon Jul 12, 2010 1:03 pm Post subject: Re: Unable to open a socket to talk to CMS Error |
|
|
Just as a wacky thought, you have called your network people, yes? I mean, if this was working before, then it is clearly a network issue that has cropped up. I'd check to see if there were any configuration changes made over the weekend. Especially ones with top secret documentation. |
|
Back to top |
|
 |
|
|