Using the Task Scheduler in W-XP, I encounter an error message ""0x80070005: Access is denied. You do not have permission to perform the requested operation."
I have a single-user machine, no network. The "status" message for the particular task states that the task "could not start."
I have tried to set passwords, but that doesn't work either.
Any ideas?
See if this link helps.
http://support.microsoft.com/default.aspx?scid=kb;en-us;884573
I tried the link you suggested. Seems MS doesn't have a fix, either. The answer -- wait for SP3.
They suggested a "work around," however that doesn't work either. Error message said that it couldn't find the program that was supposed to be run to do the fix (gpedit.msc).
Guess I'll just have to wait.
Thanks, again!!
Once we get past that concept, we might find an answer.
Scheduled Tasks in XP do require more work and is documented at http://support.microsoft.com But the usual (first) roadblock I see here is the "single user" concept.
Bob
I was able to remove the Task Scheduler patch (KB841873) and get my Tasks to execute again, correctly.
There is a suitable workaround for the original security problem described on http://www.microsoft.com/technet/security/bulletin/ms04-022.mspx under "Vulnerability Details"->Workarounds for Task Scheduler Vulnerability".
If you have SP2 installed, I assume uninstalling SP2 would also allow it to be fixed. I don't have SP2 installed, as when I did install it, too many different things all failed at once. I went through all the proper "procedures", making sure there were no programs running that might interfere, but after installation, previous programs I depend on refused to run or wouldn't work over the internet (I disabled the SP2 firewall as I already have that covered with a 3rd party, two way firewall).
I find it amusing that Microsoft claims Longhorn is faster than Windows XP -- so it was faster over Win98, but both Service Packs slowed down WinXP. In some cases the slowdown was "permanent" -- no workaround to be provided. Indeed MS security updates broke my Outlook-2002 working with the IMAP protocol. I wasn't able to roll those back as my saved system states were corrupted after installing the MS Critical Security fixes. I did analyze the IMAP traffic generated by Outlook -- and when it would hang/ hangs (doesn't always hang, some timing problem), Outlook doesn't send the IMAP equivalent of "end of commands, now run". The result is the IMAP server waits (I think it waits about 20-30 minutes), and the Outlook client is "waiting" for a response from the server that never comes. About 50% of the time, trying to cancel the operation in Outlook will result in Outlook hanging (program not responding) and having to be killed from the Task Manager.
In short -- back out the broken MS patches and wait till MS has a patch to correct the problem(s) introduced by the "critical patches".
I don't think your solution is my problem. I am not on a client server and have installed SP-2 and am current with the fixes.
I'm not sure that I want to un-install SP-2, which works fine. I have not experienced any issues or problems with my programs, even a third party firewall that I use along with W-XP firewall.
Thanks, anyway for your input.
| Forum legend: | |
| Locked thread | |
| Moderator | |
![]() |
CNET staff |
![]() |
Samsung staff |
| Norton Authorized Support team | |
| AVG staff | |
| Windows Outreach team | |
![]() |
Dell staff |
| Intel staff | |