I am facing a strange problem with BOXI-3.1. In BOXI-3.1, in CCM, to change the properties of any server, we need to log in to Manage Servers section and updated the server settings. The problem that I am facing now is after logging in to the Manage Servers section, I had stopped the CMS service but before restarting it, I closed the Manager Server Window. Now when I am again trying to log in to the same Manage Servers section, I am asked for authentication, but as the CMS service is down, I am not able to do so. This is a strange problem and a kind of deadlock is created here. As per the Help document of CMC, it is mentioned that under the properties of Server Intelligence Agent(SIA), we should select the Auto Start CMS option which will automatically start the CMS service everytime the SIA is started. I tried this option, but still the CMS service is not starting.
Does anyone knows how can I get this issues resolved? Any help on this will really be appreciated. In case anyone knows how to start the CMS from command line, then please suggest.
Thanks in advance!!
-Tushar
If you want to change the properties of any server, logon to CMS, Go to Servers window and change the properties of any server. In CCM, you can’t able to change the properties of any server.
Restart the SIA, and check in the task manager is CMS service is running or not? If it is running then follow the above steps to change the properties of server.
Even if the CMS is down, it should allow you to login to the manage servers authentication option
It might not be allowing due to some other reason, what is the error message you are getting in the authentication window
The CMS database may not be reachable or you are using incorrect username/password
The login credentials that I am using are correct only, as I had used the same credentials to login to Manage Servers Section before stopping the CMS service.
The error that I am getting now is 'Unable to logon: Could not connect to Server -servername:6400. Please check that the server name is correct, and the server is running.
Can anyone tell me how to start the CMS again?
You need to dig into it by first checking the windows event viewer for a more detailed error description
And stop the SIA, go to properties -configuration tab
Does it open up normally or any error is thrown
Also ensure that correct port number is given with servername (servername: portnumber) in the system box while authenticating for manage servers
There is no CMS Service in Task Manager (see the attached screenshot)
The following info/errors are repeatedly displayed under the Event Viewer Logs…everytime I restarted the SIA…
information-Central Management Server stopped
information-Server Intelligence Agent: server Servername.CentralManagementServer stopped with exit code = 5 (0x5).
error-Server Intelligence Agent: server Servername.CentralManagementServer stopped unexpectedly.
info-Server Intelligence Agent: server servername.CentralManagementServer has been started.
info-Central Management Server started
error-An unexpected problem (exception) happened. Reason given: The port number specified for the server is already in use., The server has problems using TCP/IP. The port number you are using is probably already in use…
error-The root server reported an error Initialization Failure. (Reason: An unexpected problem (exception) happened. Reason given: The port number specified for the server is already in use., The server has problems using TCP/IP. The port number you are using is probably already in use…). CMS Error.doc (111.0 KB)
The CMS may have been configured on port 6400
You need to contact your windows or network administrator to check the port being used by any other application
Thanks for your inputs…as suggested, I Created a new SIA i.e. SIA2 with the option ‘Create default servers on the new node’ and specified the same System DB and Audit DB names as that of SIA1.
As more than one SIA can’t run simultaneously, I stopped SIA1 and started SIA2. Then I was able to login to the Manage Servers Section.
Now there were 2 instances of each servers and the servers those belong to SIA1 were stopped and I was not able to start them again as SIA1 was down.so finally I deleted the SIA1 and now able to work with SIA2 only.
But you also suggested to point the new CMS to same FRS(IFRS and OFRS). I could specify the same system & audit DB for the new CMS while creating the new SIA but I am not gettig as how to point it to the previous FRS?
Either way now I have deleted the SIA1 and Just need to confirm whether there will be any problem with the current setting as this is the new installation only and there were no objects in the system. Please confirm whether this is ok or not.
No need to worry about FRS. Whenever you create SIA with the option '‘Create default servers on the new node’ then it will assign default properties to all the servers. If you want to check the path of FRS location, then logon to CMC-> Servers, open the properties of Input FRS / Output FRS, and click on placeholders. Here you can find the both FRS path.
Dleting SIA won’t affect your current setting.
I checked the path for FRS and it’s correct only…
Thanks for your inputs…
So finally creating a new SIA with default servers on new node is the best option to solve this problem whenever CMS is down and the manage servers section cannot be accessed to restart it…
Not always as you will have see the symptoms too.
CMS is down or manage servers is not accessible doesn’t necessarily mean that you will create an SIA
It can be due to database issue or any other problem
Yes…whle analysing this issue, I got the same error when I was trying to restart SIA, which is automatically supposed to restart the CMS through the start-up dependancy.
Server Intelligence Agent: server Servername.CentralManagementServer is considered failed because it has stopped 5 time(s) within 60 minute(s). Please restart this server.
(BOB member since 2007-03-20)
(BOB member since 2005-07-18)
(BOB member since 2005-07-18)
(BOB member since 2007-03-20)
(BOB member since 2008-05-17)
