Task Scheduler - Access Denied (x80070005) error

[joesil69]

Hello,

I'm currently trying to schedule something via Scheduled Tasks in Win Xp pro sp2, but I'm receiving the following error:


Task Scheduler and "Access Denied (x80070005) error

I have only 1 account on my pc and it does have admin rights and a pw. Even though i tried entering the pw with the correct user, i still get the same error mesg.

Any ideas what's causing this?

thank you.

 

[clayton74]

Have you tried creating a new admin account with a password, to see if the problem is profile related

 

[venusadora]

I had the same problem. I found an article related to this which solved mine.
Here it is:

PROBLEM:

“0x80070005: Access is denied" error message when you create a scheduled task in Windows XP Service Pack 2 or Windows XP Tablet PC Edition 2005

Article ID : 884573
Last Review : November 9, 2004
Revision : 4.0
On this page
SYMPTOMS
CAUSE
RESOLUTION
WORKAROUND
STATUS
MORE INFORMATION

SYMPTOMS

When you create a new scheduled task by using the Task Scheduler on your Microsoft Windows XP-based computer, you may receive the following error message after you click Finish:
The new task has been created, but may not run because the account information could not be set. The specific error is: 0x80070005: Access is denied. Try using the Task page Browse button to locate application.
Additionally, the scheduled task does not run as expected in this scenario. Instead, the following entry is logged to the Scheduled Task log file (Schedlgu.txt):
The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. 0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.

CAUSE

This problem occurs because of a regression that was introduced in both of the following updates: • Windows XP Service Pack 2 (SP2) and Windows XP Tablet PC Edition 2005.
• The update that is described in the following Microsoft Knowledge Base article:
841873 MS04-022: A vulnerability in Task Scheduler could allow code execution

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;

[LN];CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Date Time Version Size File name
-----------------------------------------------------------
27-Aug-2004 22:17 5.1.2600.1580 263,680 Mstask.dll
29-Jul-2004 23:35 5.1.2600.1580 10,752 Mstinit.exe
27-Aug-2004 22:17 5.1.2600.1587 172,544 Schedsvc.dll
30-Jul-2004 21:29 5.1.2600.1580 594,432 Xpsp2res.dll
27-Aug-2004 22:08 5.1.2600.2508 190,976 Schedsvc.dll

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, click Add User or Group, click Browse, and then add the user name or the group name that you want.
5. Click OK two times.
6. Click File, and then click Exit to quit the Group Policy editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


MORE INFORMATION

This problem may also occur when you create a new task and you do not type a password for that task. In this case, you must create a password for your user account if it does not have one, and use that password for any new task you create.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

----------------------------------------------------------------