Strange issue with scheduled jobs

[David]

I have 2 computers running WinXP Pro, both NTFS, both SP1, both part of the
same workgroup (not domain) and up-to-date in everything. In one of them (A)
I can schedule jobs to be run when nobody is logged on. I try with this
little batch file:

[runme.bat]
echo it works > c:\works.txt

As I said, I can schedule it and it runs perfectly when nobody is logged on
in A, but in the other computer B there must be someone logged on in order
to for the tasks to be executed. Computer A was installed dec/2001 and how
to say it... it is not a fresh install... However computer B was installed
last month and I installed IIS as an option. I would understand that this
issue arose in A but this is not the case, the problem happens in B, the
recently installed computer.

I completely reinstalled WinXP Pro from scratch in B using a spare hd and
tried again to schedule the job. It worked!!! (without IIS and any SP
applied). Then I simply applied SP1a and installed XP's IIS 5.1 and the same
issue arose again: None of the scheduled jobs run if nobody is logged in. In
all cases, the error the jobs return is 0x80.

I have checked the account under with scheduler service runs is LocalSystem
and is allowed to interact with desktop. I have checked also that the
account under with the job runs is granted to 'logon as a batch job' (see
Local Security Policy), in fact, it belongs to administrators group, not to
power users. I don't know what else it could be.

Is this a known issue? Is it related to IIS? Is there any workaround?

Thanks for all in advance.

[Robert Moir]

David wrote:
> I have 2 computers running WinXP Pro, both NTFS, both SP1, both part
> of the same workgroup (not domain) and up-to-date in everything. In
> one of them (A) I can schedule jobs to be run when nobody is logged
> on. I try with this little batch file:
>
> [runme.bat]
> echo it works > c:\works.txt
>
> As I said, I can schedule it and it runs perfectly when nobody is
> logged on in A, but in the other computer B there must be someone
> logged on in order to for the tasks to be executed. Computer A was
> installed dec/2001 and how to say it... it is not a fresh install...
> However computer B was installed last month and I installed IIS as an
> option. I would understand that this issue arose in A but this is not
> the case, the problem happens in B, the recently installed computer.
>
> I completely reinstalled WinXP Pro from scratch in B using a spare hd
> and tried again to schedule the job. It worked!!! (without IIS and
> any SP applied). Then I simply applied SP1a and installed XP's IIS
> 5.1 and the same issue arose again: None of the scheduled jobs run if
> nobody is logged in. In all cases, the error the jobs return is 0x80.
>
> I have checked the account under with scheduler service runs is
> LocalSystem and is allowed to interact with desktop. I have checked
> also that the account under with the job runs is granted to 'logon as
> a batch job' (see Local Security Policy), in fact, it belongs to
> administrators group, not to power users. I don't know what else it
> could be.
>
> Is this a known issue? Is it related to IIS? Is there any workaround?

And does the account the job runs under have a password of it's own. IIRC
that's required too.

[David]

Yes, in both cases (comp. A & B) the jobs are run with an account that has
a password (not blank).


"Robert Moir" > escribió en el mensaje
...
> David wrote:
> > I have 2 computers running WinXP Pro, both NTFS, both SP1, both part
> > of the same workgroup (not domain) and up-to-date in everything. In
> > one of them (A) I can schedule jobs to be run when nobody is logged
> > on. I try with this little batch file:
> >
> > [runme.bat]
> > echo it works > c:\works.txt
> >
> > As I said, I can schedule it and it runs perfectly when nobody is
> > logged on in A, but in the other computer B there must be someone
> > logged on in order to for the tasks to be executed. Computer A was
> > installed dec/2001 and how to say it... it is not a fresh install...
> > However computer B was installed last month and I installed IIS as an
> > option. I would understand that this issue arose in A but this is not
> > the case, the problem happens in B, the recently installed computer.
> >
> > I completely reinstalled WinXP Pro from scratch in B using a spare hd
> > and tried again to schedule the job. It worked!!! (without IIS and
> > any SP applied). Then I simply applied SP1a and installed XP's IIS
> > 5.1 and the same issue arose again: None of the scheduled jobs run if
> > nobody is logged in. In all cases, the error the jobs return is 0x80.
> >
> > I have checked the account under with scheduler service runs is
> > LocalSystem and is allowed to interact with desktop. I have checked
> > also that the account under with the job runs is granted to 'logon as
> > a batch job' (see Local Security Policy), in fact, it belongs to
> > administrators group, not to power users. I don't know what else it
> > could be.
> >
> > Is this a known issue? Is it related to IIS? Is there any workaround?
>
> And does the account the job runs under have a password of it's own. IIRC
> that's required too.
>
>