When I attempt to schedule a task on all my windows 2003 servers (with windows 2008 AD) I get the following error:0x80070005 Access denied task scheduler windows 2003 server. This task ran just fine in the past. The domain admin group has been manually added to the local administrators group. I did have a GPO for conflicker that I have since deleted.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I am running the job as administrator, creating the task while logged on at the console as administrator. This is a local resource. I didn't see anything helpful in the log. This seems to have started when we migrated from Windows 2003 AD to Windows 2008 AD, I went through all the policies in the Default GPO and did not see anything that would be preventing this.
I am able to schedule and run the exact same task on the Windows 2008 Domain contollers, just not the windows 2003 member servers. I am sure it is a pemissions problem I am just not seeing it. I have give the domain administrators account full contol over the shutdown.exe and schtask.exe programs and am still getting the same error message.
If I schedule the task to run on the DC for a remote 2008 DC it works perfectly if I try the same thing on a 2003 member server I get the message below on the DC. I have no idea what that means at this point.
C:\Windows\System32>shutdow
computername: The logon session is not in a state that is consistent with the requested o
peration.(1365)
There are three solutions that I have found online (at least for the XP SP2 issue):
- http://support.microsoft.c
- WORKAROUND
To work around this problem, add the "Access this computer from the network" permission to the user account that will run the
scheduled task. To do this for the local computer policy, follow these steps:
1. Click Start, click Run, type Gpedit.msc, and then click OK.
2. Expand the following items in the Local Computer Policy list:
Computer Configuration
Windows Settings
Security Settings
Local Policies
3. Click User Rights Assignment.
4. Double-click Access this computer from the network, and then click Add User or Group.
5. Add the new user name or the group name in the Enter the object names to select area.
6. Click Check Names to verify the entries.
7. Click OK two times.
-Ensure that the task is not set up as a user with no password. If this is the case create a password for the account the Scheduled Task is to run as.
As you are having this issue mainly on a Server I assume that you do have a password on the account you are creating the task with. I have attempted to use all 3 of these fixes on my own computers with this issue and have had no success.
Be aware that it is most likely that any scheduled tasks on XP SP2 machines that you may have around are probably no longer running as scheduled. Hopefully one of these things helps you out, but as I said, I have had no luck with them to this point in time.
Business Accounts
Answer for Membership
by: tanksportsPosted on 2009-04-13 at 15:49:25ID: 24133536
Remember that if it involves network resources,
make sure the user account has permissions to the resources and also use UNC
paths as mapped drives won't exist when no one is logged on. Scheduled
Tasks|Advanced|View Log may provide some details.
Sounds like the GPO you deleted may have had something to do with allowing the account to run the scheduled job.
Try running the job as administrator. Let me know what happens.