Posted by Alvin Chin on August 23, 2005 at 16:02:28:
Prior to upgrading to Comet Security Server v05.07, we were able to stop and start the Comet Services from a DOS prompt using the following commands:
NET STOP CometServices
NET START CometServices
This capability was important to us because it allowed us to utilize these commands in a batch file to stop Comet Services, copy the Comet database files & indices to a backup folder, restart Comet Services, and then initiate a tape backup of the backup folder.
Doing backup in this manner allowed us to cut several hrs off the backup process, and create greater availability of COMET to our overseas offices in different time zones.
However, ever since upgrading to Comet Security Server v05.07, we have had nothing but problems.
All Comet Services seem to stop (shutdown) normally when executing the "NET STOP CometServices" command. And Comet Services appear to have restarted after executing the "NET START CometServices" command. However, when a Comet Client attempts to connect, they receive a "security violation -- security server not available" error msg.
When I check the COMET server, I see the Comet Security Server icon on the system tray. But when I click on it to open -- the icon disappears from the tray. The only icon left is the Comet File Server.
Attempts to recover from this are tricky, inconsistent and hit & miss.
One method that works 50% of the time is to manually go into "Services", stop CometServices (note: RESTART does not solve the problem), wait a few minutes, and then start CometServices.
Another method (that works intermittently), is to manually execute "CSecSrv.exe" in the C:\Program Files\Comet Server Products folder.
And if none of the above work, the last and most unpleasant method is to stop CometServices (in the "Services" panel), and perform a restart of the Windows 2000 server.
Is there a better way to stop and start CometServices from a DOS command line (that can be utilized in a batch file)?
Thanks.
-ac-