WCS 7.0.172.0 is stopped.

[Sandeep Choudhary]

I rebooted the WCS server yesterday and now it is not working anymore.

Here is WCS Status :

Health Monitor is running with an error.

WCS is stopped.

Database server is running

Apache server is running

Logs from hm_launchout.txt

Starting Health Monitor as a primary

Checking for Port 8082 availability... OK

Key entry exists; Update Apache config from Keystore

Configuring Apache server for key

Starting Health Montior Web Server...

Health Monitor Web Server Started.

Starting Health Monitor Server...

Health Monitor Server Started.

Starting WCS Server

Could not create the Java virtual machine.

Unrecognized VM option ''

Failed to start WCS server.  Check launchout.txt for details.

Log files are located under webnms\logs in the WCS install directory.

launchout.txt - it is empty

How can I proceed Now.

Regards

[Scott Fella]

Tray to reboot the server again and wait a while for WCS to startup before you run the status. If that doesn't work, then you might want to open a TAC case as you might have to rebuild it,

Sent from Cisco Technical Support iPhone App

[Sandeep Choudhary]

I tried this but couldnt get suceed.

I will raise a TAC case and let u know the outcome:)

Regards

[Naveen Kumar]

Here are collections of the Cisco WCS fails to start up.

Case 1: Apache server is not running.

Case 2: If the WCS were installed as a service, try to rebooted the machine.

Case 3: Check if the scripts are manually run from the bin directory. You must not manually run scripts from the bin directory. You must use the links from the Windows WCS programs menu or the scripts from Linux <Install Dir> (that is, /usr/local/bin/WCS22/StartWCSServer).

Case 4: Make sure the following ports are available to WCS.
*Checking for Port 1299 availability... OK
*Checking for Port 80 availability... OK
*Checking for Port 443 availability... OK
*Checking for Port 8009 availability... OK
*Checking for Port 8456 availability... OK
*Checking for Port 8457 availability... OK
*Checking for Port 8005 availability... OK
*Checking for UDP Port 69 availability... OK
*Checking for Port 21 availability... OK

Case 5: WCS does not start if the database is corrupt. If you reinitialize or restore the database, it fixes the issue. Navigate to the WCS installation directory and issue the dbadmin.bat reinitdb command from the command prompt to reinitialize the database.

case 6: Collect the log files from the <WCS Installation Dir>\webnms\logs. These log files can be used to identify the root cause of the issue.

Case 7: Check if the Windows SNMP trap service is active on the server. Disable the service because it uses Port 162 that is required by WCS. For more information on list of ports used by WCS, refer to the