Re: Comet As Service uses Local System Account -- any attempt to change this res


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Barbara Brazil on January 14, 2009 at 10:44:06:

In Reply to: Comet As Service uses Local System Account -- any attempt to change this results posted by Alvin Chin on January 09, 2009 at 09:30:26:

Alvin:

Well, Jim, Brian, and I discussed this. Admittedly we don't know enough about Active Directories to give you a definitive answer.

Are we correct in assuming that you have no problem if just the Servers are run as a service and that the problem is only with Comet running as a service?

You said Comet generates several errors. Are you getting errors logged to the startup details file? The E91 you sent generally indicates a bad object file, which is weird. Furthermore, you indicated that you suspect Comet does not have access to local dirs but the ERASE being attempted by QSTART (from your E91 report) shouldn't even be attempted if there was no TMP dir accessed.

Might be a good idea for you to send your Comet.ini and startup details. Also turn on the "Add Directory" log message in the file server and send the CometSrv.log file after the attempted login.

Anyone else out there using Active Directories and running Comet as a service?

bb


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]