scan scheduler

  • Thread starter Thread starter margeo
  • Start date Start date
M

margeo

No matter how I set the scan scheduler, it always scans
the first scheduled time but never again after that.
Help??
 
No matter how I set the scan scheduler, it always scans
the first scheduled time but never again after that.
Help??

Hi,

What do you mean by "never again after that"? Are you logged on as a user
with the administrator rights at the time when the next schedule should
occur?
 
-----Original Message-----

Hi,

What do you mean by "never again after that"? Are you logged on as a user
with the administrator rights at the time when the next schedule should
occur?

Hi,

Thanks for your reply. Yes, I am logged on as a user with
admin rights at all times. By "never again after that" I
mean it does run the first scheduled scan but does not
run a scan the next several times it is scheduled to do
so. Hope this is clear. Any thoughts?

And kind regards to you, also.
Mark
 
Hi,
Thanks for your reply. Yes, I am logged on as a user with
admin rights at all times. By "never again after that" I
mean it does run the first scheduled scan but does not
run a scan the next several times it is scheduled to do
so. Hope this is clear. Any thoughts?

And kind regards to you, also.
Mark


Hi,

Yes, now it's clear (I'm sorry, but English is not my native language, so I
might have problems with understanding something, that is easy and clear for
a native English speaker :-) )

The limitation of the current MSAS Beta 1 version is that it does not run as
a system service, but as a process in the user mode (so MSAS has the same
rights and priviledges in the system as the currently logged on user). So
each time some action is performed by MSAS, there should be a logged on user
with administrator rights (and the best of all - it should be the same user
that has installed the MSAS).

Maybe you will take a look at the errors.log file in the MSAS folder? Maybe
it contains some valuable information about why the scheduled scan does not
start? And maybe there is some info in the System and/or Application event
logs, too?
 
Back
Top