Title: Message
Well to be honest you should run it as system account with desktop interaction and not as a specific user....but if running it as a specific user is realy the cause of the problem isn't sure at all.  Normaly that should work too....
 

dirk.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bryan Lockwood
Sent: Fri Dec 13 9:21 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] SA stops updating when logged off

Recently upgraded to latest version. SA is running as a service with 'Log on as' set to a domain userid/password that has admin access to all monitored servers as well as the SA host system. This was working before upgrade, but now, SA stops updating the web page (and apparently stops all checks) unless I am logged onto the SA host server (with another username!). When I log off it even sends the 'SA stopped' mail. Yet the service is still running.
 
This has been going on since the upgrade to 3.3.1132.2. I've tried a complete deinstall/reinstall - no good. Tried giving the SA account 'act as part of the operating system' user rights - this helped, but only for about 8 hours, then the problem began again. On reboot, SA service starts (it is set 'automatic') but does not update the web page. Installation and all changes were made at the system console, not via Terminal Services.
 
What else should I be doing? I have seen other messages saying SA should use LocalSystem with 'interact with desktop', but had hoped to avoid editing all of my monitor items separately.
 
Am running Win2k SP3 and all critical hotfixes on the SA host machine.

Reply via email to