Posted by Alvin Chin on March 30, 2006 at 09:12:37:
We recently installed version 6.02 of COMET Serve32 on our existing COMET Server (which was running version 5.10 of COMET Serve32). The server hardware is an HP/Compaq ML370 Dual 2.80Ghz Xeon processors and 4gb of RAM. The operatins system is Windows 2000 w/SP4 and patched to the last known Microsoft updates.
We are experiencing two problems:
1. Using the command line "NET STOP COMETSERVICES" & "NET START COMETSERVICES" (prior/after performing a backup) is unsuccessful. The COMET Serve32 visually appears to have started -- the
icon is visible in the system tray. But as soon we click on it to open the console, it disappears from the tray. And the bizarre thing is that in the Windows SERVICES panel, the COMET SERVICES status indicates that it is already started. We have to shut it down manually (COMET SERVICES) using the Windows SERVICES panel and then restart the Comet Service.
2. CometServe32 is unstable -- the COMET Service has unexpectedly disappear twice in the last two days. Yesterday (Wednesday) at about 4:00pm EST, COMET disappeared and caused a massive disruption among the users. When we examined the server, we saw behavior similar to above -- Comet icon is visible in the system, but when we click on it, the icon disappears. And yet, the SERVICES panel indicates that COMET SERVICES are "started". We rebooted the server to start the COMET server anew. And at 10am EST this morning (Thursday), we had again a massive disruption among the users when COMET unexpectedly became unavailable. Examination of the server showed the COMET Serve32 console in an unstable state (we could the outline of the console, but the remainder of the console was gray), and clicking on the icon again made it disappear, and yet within the SERVICES panel, status of COMET SERVICES was "started" and active. We had to physically restart the server to restore COMET services.
Any thoughts on why this is happening?
--=Alvin=--