WCS- Issue

Prasan Venky — Sun, 04 Jul 2021 07:43:08 GMT

Hello All,

WCS installed on windows server is suddenly stopped responding to console/https etc..what should i check ...?

Re: WCS- Issue

Scott Fella — Tue, 27 Aug 2013 10:43:39 GMT

Have you checked in windows if the service has stopped? Have you tried to
Stop and start wlc's again or reboot the server? I usually would do these and then verify by checking the WCS status.

Sent from Cisco Technical Support iPhone App

WCS- Issue

Prasan Venky — Tue, 27 Aug 2013 10:57:47 GMT

Hello Mr.Scott,

Thanks for your reply.. Will get back to you with the details shortly

WCS- Issue

Amjad Abdullah — Tue, 27 Aug 2013 12:35:09 GMT

Adding to what Scott suggested; try to use the latest version of WCS that is compatible with your WLCs.

The newer versions usually have more bug fixes.

Rating useful replies is more useful than saying "Thank you"

WCS- Issue

Prasan Venky — Tue, 27 Aug 2013 13:14:38 GMT

Its a appliance not a windows server... It's live in network and able to ping also. But no access of GUI... Not yet restarted due to production hours

WCS- Issue

aqjaved — Tue, 27 Aug 2013 14:12:04 GMT

Troubleshooting Guide for WCS on Windows

Please perform the following Step to troubleshoot your problem

Step 1:

Checking the Status of WCS on Windows. Follow these steps to check the status of WCS when it is installed as a Windows application or Windows service. You can check the status at any time.

Log into the system as administrator.
Perform one of the following:
From the Windows Start menu, click Programs > Wireless Control System> WCSStatus.
From the command prompt, navigate to the WCS installation directory (C:\Program Files\WCS32\bin) and

Enter WCSAdmin status. The WCSAdmin window appears and displays messages indicating the status of WCS.

Close the WCSAdmin window when the Close button becomes active.

Step 2: Stopping WCS on Windows. Follow these steps to stop WCS when it is installed as a Windows application or Windows service. You can stop WCS at any time.

Log into the system as administrator.
Perform one of the following:
From the Windows Start menu, click Programs > Wireless Control System > StopWCS.
From the command prompt, navigate to the WCS installation directory (C:\Program Files\WCS32\bin) and enter WCSAdmin stop. The WCSAdmin window appears and displays messages indicating that WCS is stopping.
Close the WCSAdmin window when the Close button becomes active.

Step 3: Starting WCS on Windows

Follow these steps to start WCS when it is installed as a Windows application or Windows service.

Log into the system as administrator.
Perform one of the following:
From the Windows Start menu, click Programs > Wireless Control System> StartWCS.
From the command prompt, navigate to the WCS installation directory (C:\Program Files\WCS32\bin) and enter WCSAdmin start. The WCSAdmin window appears and displays messages indicating that WCS is starting.
Close the WCSAdmin window when the Close button becomes active. WCS is now ready to host WCS user interfaces (clients). Go to the "Logging into the WCS User Interface" section to use a web browser to connect to the WCS user interface. Starting WCS on Windows

Restoring the WCS Database.

If problem not solved and no other solution found, then you can restore it.

Follow these steps to restore the WCS database from a backup file on a Windows server. If you are restoring the WCS database in a high availability environment, refer to the "Restoring the WCS Database in a High Availability Environment" section.

Step 1 Log into the system as administrator.

Step 2 Perform one of the following:

•Follow these steps from the Windows Start menu:

a. Click Start > Programs > Wireless Control System> Restore. The DBAdmin and Enter Information window appears.

b. Browse to the backup directory that you created and choose the filename or enter the full path and filename of the backup file (such as C:\WCS7.0.X.X_Backup\Nov11.nmsbackup) and click OK.

< OR >

•Follow these steps from the command prompt:

a. Navigate to the WCS installation directory (C:\Program Files\WCS7.0.X.X\bin).

b. Enter DBAdmin restore backup-filename, where backup-filename is the full path and filename of the backup file (for example, C:\WCS7.0.X.X_Backup\Nov11.nmsbackup).

Step 3 If you have a large event table to migrate, you must limit the size of the event table. You cannot decline this process, but it generally only affects pre-5.1 to 5.2 or later migration. The following warning message appears:
WARNING: You are migrating from a pre-5.1 database to a post-5.1 database. This may take a very long time -- possibly several hours. You can considerably speed this migration by retaining only the most recent events from the restored database. Even if you do this, the event table will be repopulated within seven days. This does not affect current alarms. This does not affect the backed-up database.
Would you like to retain only recent events?

If you type Y or Yes (or click Yes from the GUI prompt), the restore retains only the most recent 40,000 events.

Step 4 Click Yes if a message appears indicating that WCS is running and needs to be shut down.

Step 5 The DBAdmin window appears and displays messages indicating that WCS is shutting down (if applicable) and the WCS database is being restored. Close the DBAdmin window when the Close button becomes active.

For complete reference please check the below guide:

http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0main.html#wp1077188

topic WCS- Issue in Wireless

WCS- Issue

Re: WCS- Issue

WCS- Issue

WCS- Issue

WCS- Issue

WCS- Issue