I've tried it like that, but I have also run it as System with no desktop interaction and also as an admin account on the SA box. No difference.
At 07:59 PM 10/6/04 +0200, you wrote: >Are you using the sYSTEM account with DESKTOP interaction for the service? >I looks like the service isn't able to correctly authenticated and as such >it takes longer. > > >Dirk. > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >Of George McCashin >Sent: Wednesday, October 06, 2004 7:40 PM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] Checking Service problem > > >Oops... sorry about that. Note here that this isn't a huge issue for me >because the box that runs it is in a pretty secure place, so I can (and do) >just leave it running as an app. So this is just informational/academic >really, and I gather no one else has this issue or others would mention it. > >So feel free to bail on the exchange any time you wish. :-) > >Some oddness lies in the fact that I am doing this EventLog service check on >about 4 boxes... 1 is NT4 and the others are W2K Server. Running as an app >they all return a check time of about 40ms, and running as a service they >all hit either 2273ms to 2283ms. And I don't know that name resolution is >an issue because they are all specified by IP. > >And in case it halps/matters, when it runs as a service the log shows this >at the place where it does the EveentLog check: > >Wednesday, October 06, 2004 1:31:19 PM ERR: connect to host failed: 1312(A >specified logon session does not exist. It may already have been >terminated.) > >When running as an app, I see this one: > >Wednesday, October 06, 2004 1:36:45 PM GetServiceStatus Eventlog: Running > >At 05:54 PM 10/6/04 +0200, you wrote: >>That's info that you didn't give within the previous mail.... >> >>In both cases the same part of the code (source) is executed so Servers >>Alive as such isn't doing anything to make this slower. I can only presume >>that for some reason the OS is reacting slower when the request comes from >a >>service then from a application. One reason I could see was the one I >>explained in the previous answer but since that isn't the case (since both >>need the authentication), I can see as different possibility that a user >>(user running the application) does the name resolution differently then >the >>service-user. >> >>And no there is no digest version of the list. >> >> >>Dirk. >> >>-----Original Message----- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf >>Of George McCashin >>Sent: Wednesday, October 06, 2004 5:48 PM >>To: [EMAIL PROTECTED] >>Subject: RE: [SA-list] Checking Service problem >> >> >>I may just be a little dense about this as I don't quite understand it. >>While I agree that the user running the SA service has no direct rights to >>the box being checked, the user that I use when I run SA as an application >>doesn't either. So what makes the two cases different? >> >>And is there a digest version of this list (probably not since I don't see >>that as an option)? >> >>At 06:49 AM 10/6/04 +0200, you wrote: >>>When running as a service in most cases the user running the service has >no >>>direct rights on the remote system, therefore a username/password is >>>provided. The authentication towards the remote system can take some time >>>and as such the check takes longer. >>> >>> >>>Dirk. >>> >>>-----Original Message----- >>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >>Behalf >>>Of George McCashin >>>Sent: Wednesday, October 06, 2004 12:41 AM >>>To: [EMAIL PROTECTED] >>>Subject: [SA-list] Checking Service problem >>> >>> >>>I am currently using SA to check a few W2K boxes by looking for the Event >>>Log service. If I run SA as an application, it works just fine. But any >>>time I start it up as a service (either automatically at boot or by hand >>>after boot) the entries looking for that Event Log service all start >>>reporting return times of 3000-4000 milliseconds, which of course trips >the >>>alarm on SA. >>> >>>This is running on a W2K box with the latest version of SA. >>> >>>Thoughts? >>> >>> >>>George McCashin >>> >>> WTVC-TV >>> Engineering >>> Information Systems >>> 423-757-7360 >>> >>> >>> >>>------------------------- >>> >>>[This E-mail scanned for viruses by Declude Virus] >>> >>>To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >>>With the following in the body of the message: >>> unsubscribe SAlive >>> >>> >>> >>> >>> >>> >>>------------------------- >>> >>>[This E-mail scanned for viruses by Declude Virus] >>> >>>To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >>>With the following in the body of the message: >>> unsubscribe SAlive >>> >> >>George McCashin >> >> WTVC-TV >> Engineering >> Information Systems >> 423-757-7360 >> >> >> >> >>------------------------- >> >>[This E-mail scanned for viruses by Declude Virus] >> >>To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >>With the following in the body of the message: >> unsubscribe SAlive >> >> >> >> >> >> >>------------------------- >> >>[This E-mail scanned for viruses by Declude Virus] >> >>To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >>With the following in the body of the message: >> unsubscribe SAlive >> > >George McCashin > > WTVC-TV > Engineering > Information Systems > 423-757-7360 > > > >------------------------- > >[This E-mail scanned for viruses by Declude Virus] > >To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >With the following in the body of the message: > unsubscribe SAlive > > > > > > >------------------------- > >[This E-mail scanned for viruses by Declude Virus] > >To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] >With the following in the body of the message: > unsubscribe SAlive > George McCashin WTVC-TV Engineering Information Systems 423-757-7360 ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
