Batch Issue

I have a schdueled shutdown task schdueled and the user is part of the power user group. Job fails with error code could not start with status code 0x0. What could be wrong ?
Who is Participating?
dolomitiConnect With a Mentor Commented:
follow these attentions:

1) make a script, run it directely (not in task schedule) and test that it goes, and does not require any clicks.

2) Add this to scheduled task, verify user/pass (if task does not start for this issue, in the state you can see it, it is not your issue), and verify check box allowing running without user logged in.

3) Don't be logged on when the task starts. If you want see what your system does when shutdown,
re-login with a no-admin user. I have noted sometime this strange behavior: if I was logged in, no in shutdown case, the task did not started.

4) In the scheduled task, in Advance manu, there is a View Log, not great, but you can give a look.

John HurstBusiness Consultant (Owner)Commented:
Schedule the task with Administrator credentials and it should work. I schedule tasks for users this was (working tasks, not shutdown tasks) and they work fine. ... Thinkpads_User
quizkeyAuthor Commented:
user is power user
Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

for my knowns,
power user in a server can shutdown it
(that is user belongs in Power User Group of that Server)
quizkeyAuthor Commented:
I already checked that user is part of power users group .
snowdog01Connect With a Mentor Commented:
Check the Scheduled Task log under the Advanced Menu > View Log.  You may have to scroll down to locate the most recent entry.  Look for the line "[ ***** Most recent entry is above this line ***** ]", then read above.   Generally when their is a permissions issue, this log will give you a clue.  
If the user is a power user and power user's can shutdown the workstation (in the local sec policy), then the problem may be related to permissions, it also may be related to what else is running on the workstation at the time the shutdown command is issued.  If an application is hung, the shutdown command may not be able to close the apps and therefore fail.  
I agree with dolomiti, run the script manually and see if it succeeds, then worry about automation.  It it works manually, then the Scheduled Task log may hold the key to the automation issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.