Prev: Windows 2008 Server Lockups
Next: Print Server
From: Anna on 9 Apr 2010 12:44
I have a scheduled task running on a server (Windows Server 2003) that
connects to another computer in the domain (of which the domain admin is an
administrator on that computer). When you manually click run on the task it
runs with status 0X0, when you let it run per the schedule the status is 0X1.
When I look in the log file it only indicates it exited with (1).
From: Pegasus [MVP] on 9 Apr 2010 12:53


"Anna" <Anna(a)discussions.microsoft.com> wrote in message
news:DCC3847A-0D09-48F8-AE4A-7D2800F9C4DD(a)microsoft.com...
> I have a scheduled task running on a server (Windows Server 2003) that
> connects to another computer in the domain (of which the domain admin is
> an
> administrator on that computer). When you manually click run on the task
> it
> runs with status 0X0, when you let it run per the schedule the status is
> 0X1.
> When I look in the log file it only indicates it exited with (1).

Let's have a look at the code you're running under the Task Scheduler.

From: Anna on 9 Apr 2010 13:53
copy \\6yf67f1\c$\ATTNDATA\*.* R:\Backups\Attendance_Professional /Y
exit


"Pegasus [MVP]" wrote:

>
>
> "Anna" <Anna(a)discussions.microsoft.com> wrote in message
> news:DCC3847A-0D09-48F8-AE4A-7D2800F9C4DD(a)microsoft.com...
> > I have a scheduled task running on a server (Windows Server 2003) that
> > connects to another computer in the domain (of which the domain admin is
> > an
> > administrator on that computer). When you manually click run on the task
> > it
> > runs with status 0X0, when you let it run per the schedule the status is
> > 0X1.
> > When I look in the log file it only indicates it exited with (1).
>
> Let's have a look at the code you're running under the Task Scheduler.
>
> .
>
From: Dave Patrick on 9 Apr 2010 23:41
Scheduled Tasks|Advanced|View Log may provide some details. If the job
connects to another machine you may need to add the user/ group 'logon as
batch job' rights (server side). Control Panel|Admin Tools|Local Security
Policy\Local Policies\User Rights Assignments
"Log on as a batch job"

If the task completes but the job does not then there is a problem in the
job itself. Remember that if it involves network resources to make sure the
user account has permissions to the resources and also use UNC paths as
mapped drives won't natively exist when no one is logged on.


--

Regards,

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

"Anna" wrote:
> copy \\6yf67f1\c$\ATTNDATA\*.* R:\Backups\Attendance_Professional /Y
> exit

From: Pegasus [MVP] on 10 Apr 2010 01:15
As Dave Patrick says, mapped drives will not exist in scheduled tasks. You
can easily home in on the cause of such problems by getting your command to
log itself:

copy \\6yf67f1\c$\ATTNDATA\*.* R:\Backups\Attendance_Professional /Y
1>c:\copy.log 2>&1


"Anna" <Anna(a)discussions.microsoft.com> wrote in message
news:31BC8B39-EFBA-4ECC-B57A-58A441823F77(a)microsoft.com...
> copy \\6yf67f1\c$\ATTNDATA\*.* R:\Backups\Attendance_Professional /Y
> exit
>
>
> "Pegasus [MVP]" wrote:
>
>>
>>
>> "Anna" <Anna(a)discussions.microsoft.com> wrote in message
>> news:DCC3847A-0D09-48F8-AE4A-7D2800F9C4DD(a)microsoft.com...
>> > I have a scheduled task running on a server (Windows Server 2003) that
>> > connects to another computer in the domain (of which the domain admin
>> > is
>> > an
>> > administrator on that computer). When you manually click run on the
>> > task
>> > it
>> > runs with status 0X0, when you let it run per the schedule the status
>> > is
>> > 0X1.
>> > When I look in the log file it only indicates it exited with (1).
>>
>> Let's have a look at the code you're running under the Task Scheduler.
>>
>> .
>>
 | 
Pages: 1
Prev: Windows 2008 Server Lockups
Next: Print Server