02-21-2012 11:20 PM - edited 07-03-2021 09:38 PM
Hi Expert,
I found WCS Sytem Error Page was displayed after login completed for while. How can i fix about this? Thanks
WCS System Error Page
Error(s): You must correct following error(s) before proceeding: Error:COMMON-1: Some unexpected internal error has occured. If the problem presist please report to the Tech Support. Error:Detail: Cannot open connection
Solved! Go to Solution.
02-22-2012 12:13 AM
02-22-2012 12:13 AM
Rojer-bkk,
Did you try to stop and restart the WCS service?
Justin
02-22-2012 01:12 AM
Hi Justin,
WCS version7.0.172.0. Do you mean issue command StopWCS and StartWCS ?
02-22-2012 11:52 AM
Rojer,
Yes, those are the commands, and they work on both Windows and Linux. Also, if you are on Windows and RDP/console to the desktop, the application shortcuts to stop and start are in the WCS program group.
Justin
02-28-2012 10:45 PM
Justin, it's work!! Thanks
02-28-2012 10:52 PM
Rojer,
Great to hear it worked. Thanks for the update!
Justin
07-03-2012 02:34 AM
Just a heads up to anyone else that might do this... it took about 5 to 10 minutes for the 'StopWCS' process to complete.
We run Version 7.0.172.0 on a Windows Server 2003 VM.
We initially tried restarting the service from Windows Services (services.msc) - made no difference - had to run the stopWCS and startWCS programs in the installation folder.
NOTE: after launching the exe from the program files\WCSxxx\bin\ folder - it took a few moments and a Java console window appeared. It then spewed out the following over the space of 5 to 10 minutes...
"Stopping Health Monitor...
Waiting for shutdown to complete.
...
Health Monitor successfully shutdown.
Stopping WCS server
WCS server successfully shutdown.
Waiting for shutdown to complete.
Shutting down database server ...
Database server successfully shutdown.
Apache server is stopped.
WCS successfully shutdown."
The startup process was much quicker... taking no more than 5 minutes if that.
Again, after launching the exe from windows explorer - it took a little while for the java window to appear - it then quite quickly (compared with shutdown) produced the following output.
"Starting WCS
This may take a few minutes...
Starting Apache...
Starting Apache server ...
Apache server is running.
WCS started successfully."
And yeah - it resolved the issue for us too - many thanks.
07-06-2012 03:35 AM
Thanks Brett for sharing the detailed explanation which will be helpful to other
Vinay Sharma
Sent from Cisco Technical Support iPhone App
07-06-2012 03:36 AM
Thanks Justin. 5+
Sent from Cisco Technical Support iPhone App
09-28-2013 04:54 AM
it happed with me every two or three days ,can anyone help me ?what's reasons ? how to solve it?WCS on Linux system?
email me on ahmad_faroty@hotmail.com...appreciate your help..
09-28-2013 08:31 AM
Ahmad:
If you're still on WCS 7.0.172.0, that's almost to be expected. There were several catastrophic database bugs in 7.0.172.0 that showed themselves in these kinds of symptoms (CSCto88700, CSCtr97576, CSCtr33182, etc.) The very best thing you can do is take a backup, uninstall 7.0.172.0, install 7.0.240.0 fresh, then restore the backup into 7.0.240.0. If the database has become corrupted, you can open a case with TAC, provide a copy of the backup and see if the database can be repaired or recovered. 7.0.172.0 was **REALLY** **THAT** **BAD**!!!!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide