AT job creation

[Adrian Marsh (NNTP)]

All,

Can anyone tell me why the following line in my logon script exits with
an error code of 9009 on an XP Pro SP2 machine, but not on a Windows
2000 Pro SP4 machine? (I get a 0 - OK)

Also this works fine if I type it on the same XP machine from a CMD prompt..

at 0:00 /every:m,t,w,th,f,sa,su
\\swocmpq01.uk-lab.lucent.com\software$\_logon\nightly\nightly.bat

(all one line)

Cheers,

Adrian

 

[Dave Patrick]

Try something else simple; to test. It may be the batch job and nothing to
do with AT

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| All,
|
| Can anyone tell me why the following line in my logon script exits with
| an error code of 9009 on an XP Pro SP2 machine, but not on a Windows
| 2000 Pro SP4 machine? (I get a 0 - OK)
|
| Also this works fine if I type it on the same XP machine from a CMD
prompt..
|
| at 0:00 /every:m,t,w,th,f,sa,su
| \\swocmpq01.uk-lab.lucent.com\software$\_logon\nightly\nightly.bat
|
| (all one line)
|
| Cheers,
|
| Adrian

 

[Adrian Marsh (NNTP)]

Dave,

It works fine on the 2000 machine, just not on this XP Pro box. Its
part of a set of a lot more complicated scripts, and all the rest work
OK. I tried loking 9009 up on google for error codes. Closest I get is
that its a DNS issue.. but that doesn't make sense.

 

[Dave Patrick]

Knowing that it work on Windows 2000 doesn't help. Try something else
simple; to test (on Windows XP). It may be something within the batch job
and nothing to do with AT. In other words you need to know which direction
to pursue.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Dave,
|
| It works fine on the 2000 machine, just not on this XP Pro box. Its
| part of a set of a lot more complicated scripts, and all the rest work
| OK. I tried loking 9009 up on google for error codes. Closest I get is
| that its a DNS issue.. but that doesn't make sense.

 

[ptwilliams]

Could it be that that XP box cannot resolve that name??

Also, have you tried encompassing the path in quotes? There looks like
there's a space in there...

--

Paul Williams

http://www.msresource.net
http://forums.msresource.net
______________________________________
Dave,

It works fine on the 2000 machine, just not on this XP Pro box. Its
part of a set of a lot more complicated scripts, and all the rest work
OK. I tried loking 9009 up on google for error codes. Closest I get is
that its a DNS issue.. but that doesn't make sense.