Sharepoint Services 3.0 timer error

The Sharepoint 3.0 installation on my 2008 SBS is throwing out the following application errors daily.

Windows SharePoint Services 3      27745

This is immediately followed by

Windows SharePoint Services 3      6772            1
Event Details:    
There was an internal error invoking the timer job ''{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}'' for service ''{00000000-0000-0000-0000-000000000000}''.

How can I prevent this error?
DesertDawgAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
FastFngrzConnect With a Mentor Commented:
In Central Administration, you should be able to correlate the timing of the errors in event viewer with the Timer Job History.

Also, as noted above, the ULS Viewer tool at http://archive.msdn.microsoft.com/ULSViewer is a great tool to be able to analyse the ULS logs, which will most certainly identify the job in question.
0
 
shambhusingh2004Commented:
First of all you have to identify which service is create issue :

Look at registry : '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A} and find out which belong to this registry.

Then find out - why this service is causing issue.
0
 
DesertDawgAuthor Commented:
A registry search doesn't find that key.  Which category is it under?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
dhawalsethCommented:
Download a tool called ULC viewer. It will help you in analyse the sharepoint log files.

Mark as answer if helped.

Enjoy!!
0
 
CloudedTurtleCommented:
You could QUERY the SharePoint config database to determine a name of the Job based on those GUIDs.

WARNING: Microsoft does not support SharePoint if your databases have been modified through any means other than the UI, approved STSADM commands, or the object model. (Reading is okay, just don't change anything.)

Query would look something like this:
SELECT*
  FROM [SharePoint_Config].[dbo].[TimerRunningJobs]
  WHERE [JobId] = 'FD730E80-C470-4D92-B0E5-F57C98ABDF4A'

Open in new window

0
 
CloudedTurtleCommented:
Any new info on this issue?

-CT
0
 
mrwolfCommented:
Hi  DesertDawg,

I have this same error with SBS 2008 but only once or twice per week. Did you find what service it was?

I downloaded ULS Viewer but my logs only show jobs back as far as the 18th and the last time i had an error was on the 16th so i think i have missed my window of opportunity this time around. I'll watch for the next one though.

From Central Administration, i can only find a jobs last run time. I can't see a complete history so these two things correlate timings

 - I also can't find that in the registry
 - I don't know how to run that DB query

Thanks
0
 
mrwolfCommented:
I think it is OWSTIMER.EXE but in that case, i still don't know how to resolve this error
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.