0x80070005 Access denied task scheduler windows 2003 server

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.
sactownraiders01Asked:
Who is Participating?
 
tanksportsCommented:
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.
0
 
sactownraiders01Author Commented:
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.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
sactownraiders01Author Commented:
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.
0
 
sactownraiders01Author Commented:
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>shutdown /m \\computername /r
computername: The logon session is not in a state that is consistent with the requested o
peration.(1365)
0
 
iiviitCommented:
I am experiencing the same issue on a few Server 2003 instances as well as a large number of XP SP2 machines.  Have you tried this on any XP machines that you have there?
0
 
sactownraiders01Author Commented:
just tried it in my xp sp2 pc same error
0
 
iiviitCommented:
There are three solutions that I have found online (at least for the XP SP2 issue):

- http://support.microsoft.com/kb/904423

- 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.
0
 
sactownraiders01Author Commented:
didn't try that on my xp machine, but I did try it on a server and it did not work.  This sucks!
0
 
iiviitCommented:
Did you have any tasks scheduled when this first started?  I know I had a few scheduled that stopped on 3/27/09, I'm just trying to see if this time line coincides with anyone else that is having this issue.  I have also noticed this does not affect Vista machines.
0
 
sactownraiders01Author Commented:
Yes I have a restart scheduled on all my servers so I can reboot them off hours if need be, and none of them are working with the expection of the Windows 2008 servers.  This started after we upgrade our domain from Windows 2000 AD to Windows 2008 AD.
0
 
iiviitCommented:
Is there any way you can add this question to the Windows XP zone as well?  We may get more responses that way and it may work with both Operating Systems affected.
0
 
sactownraiders01Author Commented:
I have added it to the XP zone also.
0
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.