• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 88
  • Last Modified:

Every time I log onto an SBS 2008 box I get a scheduler error?

When I log onto one of the SBS 2008 boxes I manage I get a scheduler error like this:

Scheduler error message when logged on.
The details of the error as follows:

Problem signature:
  Problem Event Name:      APPCRASH
  Application Name:      taskeng.exe
  Application Version:      6.0.6002.18342
  Application Timestamp:      4cd34898
  Fault Module Name:      ntdll.dll
  Fault Module Version:      6.0.6002.19623
  Fault Module Timestamp:      56ec4641
  Exception Code:      c000071b
  Exception Offset:      000000000007d645
  OS Version:      6.0.6002.2.2.0.305.9
  Locale ID:      2057
  Additional Information 1:      8975
  Additional Information 2:      803d51a048d13ed597ff94fe6ba3464e
  Additional Information 3:      8975
  Additional Information 4:      803d51a048d13ed597ff94fe6ba3464e

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Any help appreciated.
0
Siv
Asked:
Siv
  • 4
  • 2
1 Solution
 
KimputerCommented:
Try to run
sfc /scannow (from admin cmd box)

If nothing reveals to be corrupt, then proceed to check ALL the jobs (keep pressing the last history tab, and check for errors). The one that keeps throwing errors might cause it. Remove or recreate the job.
Please note, there might be up to 100 of jobs to plow through (dig through all the sub categories). Errors in the Application log might point you faster to the scheduled job in question.
0
 
SivAuthor Commented:
Kimputer,

I have done a bit more research in the event viewer on the server that's affected and every time I get the task scheduler error I also get this error at the same moment:

Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.

I googled that error and it seems to be something to do with a dud certificate. However before I raised this error here I had done some research on the scheduler error and the fix seemed to be to remove any expired certificates which I did yesterday.  I did that by opening the "certificate authority" application in Admin tools and revoked all expired certificates until there were only current certificates available.

I then waited to see if the error was gone, but again the error came up this morning when a user logged onto the server to change the backup drive so it is still present after clearing out the out of date certificates.

Given this extra information, do you think I still need to run sfc /scannow or is it more specific to the certificates?
0
 
SivAuthor Commented:
Googling further I found this blog which seems to cover the issue I am having and has a detailed step by step procedure which I have followed up to step 9 (can't do step 9 [reboot]) as there are too many staff working on the server at the moment) so I will continue after 7pm tonight when the users are out of the system and I will report back tomorrow

Resolving “PAUTOENR.DLL raised an exception” on David Moisan's IT Blog

Hopefully this may be the fix as it does seem to match the symptoms I am getting.
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

 
KimputerCommented:
Yes I suspect you need those reboots indeed.
0
 
SivAuthor Commented:
I completed the procedure last night and everything seems to be working properly this morning so full marks to David Moisan who's procedure did the business. I will close this question off as it does appear to be fixed.
0
 
SivAuthor Commented:
In the end it was my own research that located the fix. I am thankful to Kimputer for answering my call though.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now