Scheduled Task "Run As" Bug ??

[Guest]

I have a scheduled task on a Win 2000 server that executes a batch file
which in turn launches an Access app. The server is on a network, and
I have specified the scheduled task to "run as" the domain administrator.
If I execute the batch file manually, everything runs fine. But when the
scheduled task launches the process, my Access app hangs up. I have
good reasons to believe the problem is related to the scheduled task
trying to operate under the local administrator instead of the domain
administrator. Has anyone heard of anything like this? Is there maybe
something I'm not doing properly to make the scheduled task truly run
as Domain Administrator?

Thanks,
Tom

 

[Pegasus \(MVP\)]

I have a scheduled task on a Win 2000 server that executes a batch file
which in turn launches an Access app. The server is on a network, and
I have specified the scheduled task to "run as" the domain administrator.
If I execute the batch file manually, everything runs fine. But when the
scheduled task launches the process, my Access app hangs up. I have
good reasons to believe the problem is related to the scheduled task
trying to operate under the local administrator instead of the domain
administrator. Has anyone heard of anything like this? Is there maybe
something I'm not doing properly to make the scheduled task truly run
as Domain Administrator?

Thanks,
Tom

Embed your commands in a batch file so that you really
see what's causing the application to hang instead of relying
on guesswork:

@echo off
echo %date% %time% Start of task > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log
"c:\program files\microsoft office\office10\msaccess.exe" 1>>c:\test.log
2>c:\test.err
echo %date% %time% End of task >> c:\test.log

Now have a look at the two log files!

 

[Guest]

Thanks, but I already am using a batch file and updating a log file.
I am unfamiliar with the 1 and 2 parameters on your Access command,
but using other troubleshooting approaches I have already identified
the problems within my Access app. They pertain to a drive mapping
reference and usage of Outlook. I can see where these would be issues
when I log in as the Local Administrator. That's why I'm thinking that
my Scheduled Task is not correctly following through on my directive to
"Run As Domain Administrator".

Tom

 

[Pegasus \(MVP\)]

So what do you see in the two report files?

Thanks, but I already am using a batch file and updating a log file.
I am unfamiliar with the 1 and 2 parameters on your Access command,
but using other troubleshooting approaches I have already identified
the problems within my Access app. They pertain to a drive mapping
reference and usage of Outlook. I can see where these would be issues
when I log in as the Local Administrator. That's why I'm thinking that
my Scheduled Task is not correctly following through on my directive to
"Run As Domain Administrator".

Tom

 

[Enkidu]

Thanks, but I already am using a batch file and updating a log file.
I am unfamiliar with the 1 and 2 parameters on your Access command,
but using other troubleshooting approaches I have already identified
the problems within my Access app. They pertain to a drive mapping
reference and usage of Outlook. I can see where these would be issues
when I log in as the Local Administrator. That's why I'm thinking that
my Scheduled Task is not correctly following through on my directive to
"Run As Domain Administrator".

"cmd 1>file.log 2>file.err" send the ordinary output of the
command to "file.log" and any error output to "file.err".

I'm very much inclined to agree with Pegasus. It is unlikely
that you have found a bug.

How do you specify that the Domain Administrator is used?

Cheers,

Cliff

 

[Guest]

Hi Cliff,

In the Scheduled Task properties is a field called "Run As". In this field
I specify DOMAIN\Administrator and put the password in as prompted.

Note: When logged into the server as the Domain Administrator, I can
execute my batch file with no problems. But when the batch file
is executed from the Scheduled Task, it hangs up.

Thanks,
Tom