Windows Server 2000/2003 Thread, Scheduled Tasks No Longer Working in 2003 Server R2 in Technical; I'm having a huge problem with a Windows 2003 R2 Server and so far none of the fixes I've found ...
-
6th October 2010, 05:35 PM #1
- Rep Power
- 0
Scheduled Tasks No Longer Working in 2003 Server R2
I'm having a huge problem with a Windows 2003 R2 Server and so far none of the fixes I've found online has helped.
Some time ago the server stopped being able to run any of the scheduled tasks (around the time the SIMS.Net SQL platform was moved from SQL 2005 to SQL 2008 Server). I have binned all the tasks, and also removed the files in the c:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18\ folder and rebooted (as has been suggested elsewhere) but the problem remains. If I try and create a scheduled task I receive the following error:
Error 0x80070005: Access is denied
If I examine the Scheduled Tasks log file the following is shown:
0x8004130f: No account information could be found in the Task Scheduler security database for task indicated
I'm absolutely pulling my hair out here as the backups aren't running anymore (amongst loads of other things I need to run!). I'm doing everything via the adminstrator account so although I feel it must be some sort of permissions issue I'm totally stumped :-(
Any suggestions would be greatly appreciated!
Thanks,
Dan.
-
-
IDG Tech News
-
6th October 2010, 08:16 PM #2 What happens, assuming local system credentials will suffice, if you schedule a task via the command line using "at"?
-
-
7th October 2010, 08:43 AM #3
- Rep Power
- 0
Hi, thanks for the reply. This is what happens:
C:\>at 08:37 cmd /c copy C:\test.cmd C:\test.bak
Access is denied.
Once again I'm logged in as Administrator so in theory can do anything. Might be worth noting that if I log in with another account with administrative privileges the result is the same.
Any ideas?
Thanks,
Dan.
-
-
13th October 2010, 11:30 AM #4
- Rep Power
- 0
Fixed it! Turned out it was caused by a registry change that I rolled out via Group Policy some time ago to combat the spread of the Win32/Conficker worm. All I had to do was reverse the changes outlined in the 'mitigation steps' in the following article:
Virus alert about the Win32/Conficker worm
Dan.
-
SHARE:
Similar Threads
-
By cookie_monster in forum Windows Server 2008
Replies: 12
Last Post: 16th November 2011, 10:16 AM
-
By OutToLunch in forum Windows
Replies: 5
Last Post: 23rd October 2009, 02:39 PM
-
By techie08 in forum Windows
Replies: 0
Last Post: 15th December 2008, 03:05 PM
-
By cromertech in forum Windows Vista
Replies: 1
Last Post: 8th February 2008, 05:28 PM
-
By Jobos in forum Windows
Replies: 1
Last Post: 22nd June 2007, 12:07 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules