Posted by jim guerber (66.180.141.237) on September 24, 2003 at 22:16:10:
In Reply to: Comet 2004 startup error posted by Jeff Cinelli on Wed, 24 Sep 2003 07:23:20 :
Sorry, The program that transferrs the email to the forum, somehow inserted a "3D" into that error number. It should have been error=0.
This is indeed a strange error, and must be some sort of timing error, but I sure do not know what to do about it. I bet that Comet 2004 with CFAM will fix this only because it is a much more robust communications method between the Comet client and the Server.
: We are experiencing an intermittent problem when we start our Comet =
:Anywhere host using a scheduled task, since installing Comet 2004. On 3 =
:occassions during the past week, we've received "Unable to Access =
:Directory" (not verbatim) error messages when Comet starts. The =
:directories that fail have been different each time. Reviewing the =
:startup details shows this error message after checking this "S" type =
:directory:
:
:06:45:02 Check Failed, error=3D0.
:
:We are running the latest version of the Security Server and Cometsrv32 =
:as well, installed a few days before Comet 2004.
:
:Shutting down Comet and restarting has corrected the problem each time. =
:We have not yet received this error message on any machines other than =
:this Comet anywhere host. Most users start Comet manually, and 1 other =
:user starts a normal session automatically at the same time that the =
:Comet Anywhere host starts up, and that session has not failed either.
:
:Starting a Comet Anywhere remote session verified that the directory =
:that experienced the problem was indeed unavailable.
:
:I can forward a copy of the startup log, if you are interested.
:
:Thank you!
: