Posted by Justin Reynolds on August 28, 2006 at 13:20:53:
In Reply to: CFAM disconnect posted by Grant Foraker on August 28, 2006 at 09:39:27:
We've had what sounds like a similar issue. (We just recently upgraded to 2006.)
On a client machine, 'COSW' would crash, but it would leave COSC/COSP/CFAM running; re-launching Comet would either crash with an error message, or just do nothing.
Killing all the Comet processes using 'task manager' seemed to fix the problem.