PDA

View Full Version : Task Scheduler and Batch files


Richard Schad
December 5th 03, 12:20 AM
I am attempting to use the Task Scheduler and a batch file to backup
files to a CD drive. I get the following error:

My BackUp.job" (Lifesave01.bat) 4/27/2003 2:00:00 PM ** ERROR **
The attempt to log on to the account associated with the task
failed, therefore, the task did not run.
The specific error is:
0x8007052f: Logon failure: user account restriction. Possible
reasons are blank passwords not allowed, logon hour restrictions, or a
policy restriction has been enforced.
Verify that the task's Run-as name and password are valid and
try again.
"Task Scheduler Service"

I would appreciate your help.

Thanks

David Candy
December 5th 03, 12:20 AM
Did you read the message.
Possible reasons are blank passwords not allowed, logon hour =
restrictions, or a
policy restriction has been enforced.
It's your computer and only you know.


--=20
http://www.g2mil.com/Apr2003.htm
http://prorev.com/forbesrussia.htm
---------------------------------------------------------------
David Candy
http://www.mvps.org/serenitymacros
---------------------------------------------------------------
"Richard Schad" > wrote in message =
...
> I am attempting to use the Task Scheduler and a batch file to backup
> files to a CD drive. I get the following error:
>=20
> My BackUp.job" (Lifesave01.bat) 4/27/2003 2:00:00 PM ** ERROR **
> The attempt to log on to the account associated with the task
> failed, therefore, the task did not run.
> The specific error is:
> 0x8007052f: Logon failure: user account restriction. Possible
> reasons are blank passwords not allowed, logon hour restrictions, or a
> policy restriction has been enforced.
> Verify that the task's Run-as name and password are valid and
> try again.
> "Task Scheduler Service"
>=20
> I would appreciate your help.
>=20
> Thanks

Richard Schad
December 5th 03, 12:21 AM
On Thu, 1 May 2003 05:24:37 +1000, "David Candy" >
wrote:

>Did you read the message.
>Possible reasons are blank passwords not allowed, logon hour restrictions, or a
>policy restriction has been enforced.
>It's your computer and only you know.

Yes.

There are three other scheduled tasks none of which have a password or
any setup differences from my task that I can discern. They a all
tasks put in by Norton. Could that make a difference?

David Candy
December 5th 03, 12:22 AM
Must have a password.

--=20
http://www.g2mil.com/Apr2003.htm
http://prorev.com/forbesrussia.htm
---------------------------------------------------------------
David Candy
http://www.mvps.org/serenitymacros
---------------------------------------------------------------
"Richard Schad" > wrote in message =
...
> On Thu, 1 May 2003 05:24:37 +1000, "David Candy" >
> wrote:
>=20
> >Did you read the message.
> >Possible reasons are blank passwords not allowed, logon hour =
restrictions, or a
> >policy restriction has been enforced.
> >It's your computer and only you know.
>=20
> Yes.
>=20
> There are three other scheduled tasks none of which have a password or
> any setup differences from my task that I can discern. They a all
> tasks put in by Norton. Could that make a difference?

David Candy
December 5th 03, 12:22 AM
That means the account you use to run the task must have a password.

--=20
http://www.g2mil.com/Apr2003.htm
http://prorev.com/forbesrussia.htm
---------------------------------------------------------------
David Candy
http://www.mvps.org/serenitymacros
---------------------------------------------------------------
"Richard Schad" > wrote in message =
...
> On Thu, 1 May 2003 05:24:37 +1000, "David Candy" >
> wrote:
>=20
> >Did you read the message.
> >Possible reasons are blank passwords not allowed, logon hour =
restrictions, or a
> >policy restriction has been enforced.
> >It's your computer and only you know.
>=20
> Yes.
>=20
> There are three other scheduled tasks none of which have a password or
> any setup differences from my task that I can discern. They a all
> tasks put in by Norton. Could that make a difference?

Google