We currently have installed Microsoft Windows SharePoint services 3.0 SP2 in a farm environment with one database server and one application server. both servers are receiving this error about every 15 minutesSource : Windows SharePoint Services 3Event ID 6772 There was an internal error invoking the timer job '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service '{00000000-0000-0000-0000-000000000000}'. does anyone know what could cause this?Thanks,Ray

Hi Roy, I found that you post a related issue here two month ago. http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/de9d782f-d2d4-410b-a2be-5169b6edbd60. I did some initial research in our internal database, but could not find a constant cause to your issue. In order to know your issue better, I would like to ask you to help me to collect a SPSReport on your application server and send to the following workspace: Workspace URL: (https://sftasia.one.microsoft.com/ChooseTransfer.aspx?key=5ad62d1c-32ea-475a-985b-9fec61427b88) Workspace Password: UWE[3hGUpHqf To capture SPSReports, please follow the steps: 1) Download the SPSReport tool from http://spsreport.codeplex.com/ 2) Run the SPSReport.exe on the Application Server. 3) Choose option 3 (Full). 4) On your system a CAB file will be generated in the %systemroot%\SPSReports\Portal\rpt\Cab directory called %COMPUTERNAME%_SPSReports.CAB. 5) The CAB file will contain the reports generated by the SPS Reporting Tool. 6) Send the cab file to the workspace above. Thanks for your cooperation. Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact mtngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert,Thanks very much for your help. I did post a similar issue a couple of months back and was not able to resolve it. We are starting to use SharePoint a lot now so I was trying again to resolve some of our issues. It is basically the same issue with the timer service but slightly different error since upgrading to SP2.I just ran SPSReport and it comes up with an error. A Cut and Paste of the screen is below. It did create some cab files so I will upload them to the workspace in a few minutes. Tue 01/26/2010 9:00:27.04: Microsoft Platform Support Reporting Tool V3.0.0.8 - Portal - FULL - NOISY - OPEN beginTue 01/26/2010 9:00:32.43: Gathering Application Event LogTue 01/26/2010 9:00:34.32: Gathering System Event LogTue 01/26/2010 9:00:43.82: Gathering list of services installed and their current stateTue 01/26/2010 9:00:45.39: Gathering Operating System informationTue 01/26/2010 9:00:46.00: Gathering Hotfix timelineTue 01/26/2010 9:00:46.07: Gathering hotfix state informationTue 01/26/2010 9:01:16.85: Gathering hosts fileTue 01/26/2010 9:01:16.86: Gathering ULS Log filesTue 01/26/2010 9:01:18.05: Gathering PSC Diagnostic Log files Tue 01/26/2010 9:01:19.52: Gathering Windows SharePoint Services System Information (HKLM\Software\Microsoft\Shared Tools\Web Server Extensions)Tue 01/26/2010 9:01:19.57: Gathering Office Server Registry Information (HKLM\Software\Microsoft\Office Server) Error: The system was unable to find the specified registry key or valueTue 01/26/2010 9:01:19.58: Gathering file version information from the SharePoint bin folderThanks you for your help.Ray

Hi Roy, Thanks for your cooperation. I found that you installed Windows SharePoint Service 3.0 with Standalone installation type. I noticed that the error 6772 occurred every 15 minutes, then I checked the corresponding ULS logs, here is the result for your information: OWSTIMER.EXE (0x0528) 0x08C4 Windows SharePoint Services Timer 8nbb High The following exception was thrown when updating the progress of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition, id 395883a2-2250-4f0a-ac1b-a18647954425. Object reference not set to an instance of an object. OWSTIMER.EXE (0x0528) 0x05B4 Windows SharePoint Services Timer 6772 Critical There was an internal error invoking the timer job '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service '{00000000-0000-0000-0000-000000000000}'. Based on the logs, the issue should be related with Windows SharePoint Services Search Service. You could check if the Indexing Schedule was set to Every 15 minutes in Central Administration > Operations > Services on Server > Windows SharePoint Services Search Service Settings. If so, please try the following action plans and see if it is helpful for your issue. 1. Try to start a full crawl by using Stsadm -o spsearch -action fullcrawlstart commands. 2. Wait for 15 minutes or longer, If the error continues to persists, try to stop and start the service following Spsearch: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288507.aspx). 3. Wait for another 15 minutes or longer, If the error continues to persists, try to reprovision the Windows SharePoint Services Search Service in Central Administration > Operations > Services on Server > Windows SharePoint Services Search Service Settings by stop and start the service with a new search database. Hope the information can be helpful. Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact mtngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Roy, Could you please let me know how is going with your issue? If you need further assistance, please feel free to let me know. Have a nice weekend! Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact mtngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert,Thanks for getting back to me on this. I am going to try your solution on thursday when we are doing some upgrades on the server. I will let you know how it goes.ThanksRay

Hi Lambert,I tried all 3 steps listed above. Sorry no luck. The error still comes up every 15 minutes. It is " There was an internal error invoking the timer job '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service '{00000000-0000-0000-0000-000000000000}'."Would you like me to run SPS report again?ThanksRay

Hi Roy, Thanks for your update. Could you please let me know if the error disappeared after stop the Windows SharePoint Services Search Service? I need to narrow down the source of the issue. Yes, I would like to get a new SPS report and see if there are any changes. Thanks! Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact mtngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert,After stopping the service the error did keep coming up every 15 minutes.One thing that happened when I stopped the service on the application server is I got this error.Event ID 2426Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.Context: Application 'Search', Catalog 'index file on the search server Search'Details:(0x80041812) I tried starting serch service on both the database server and the application server. It does not matter which one it is started on both servers get Event ID 6772There was an internal error invoking the timer job '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service '{00000000-0000-0000-0000-000000000000}'.Everything in sharepoint works fine with the exception of two other things besides these errors. When clicking on "Servers in Farm" or "Timer job status" in central administration you get an unknown error. All other features in Sharepoint work fine.Hope this helps. I will send a new report file.Thank you for your help with this.Ray

Hi Roy, Thanks for your update. I get some new information to you after researched more cases, the error may be the result of the database lock refresh code not expecting a web application with no content dbs. The event is completely harmless and can be ignored. As the SPSReport do not contains your SharePoint farm architecture, could you please check if there is a web application with no content dbs? For the unknown errors when clicking "Servers in Farm" or "Timer job status" in central administration, could you please disable the CustomErrors in web.config and see if there is any more information in the web UI? Hope the information can be helpful. Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact mtngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

hi Lambert,Could you tell me how to do this step please. For the unknown errors when clicking "Servers in Farm" or "Timer job status" in central administration, could you please disable the CustomErrors in web.config and see if there is any more information in the web UI?ThanksRay

Hi Lambert,Also I am not sure if this helps any but this is on the logs files also.02/05/2010 12:00:45.40 OWSTIMER.EXE (0x0528) 0x0128 Windows SharePoint Services General 8dyt High The following error occured while trying to read the ConnectionString property. Object reference not set to an instance of an object.

Hi Roy, Sorry for the later reply. To disable the CustomErrors in web.config, you need to find the correct Central Admin web.config in C:\Inetpub\wwwroot\wss\VirtualDirectories. Find the customErrors section following http://msdn.microsoft.com/en-us/library/h0hfz6fc.aspx and change the value to Off. I noticed the ConnectionString error, but I am not sure if it is related with your issue as the error source is not logged. Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert,No Problem.I disabled CustomeErrors in web.config in the following 4 locations. C:\inetpub\wwwroot\wss\VirtualDirectories\80C:\inetpub\wwwroot\wss\VirtualDirectories\80\wpresourcesC:\inetpub\wwwroot\wss\VirtualDirectories\24609C:\inetpub\wwwroot\wss\VirtualDirectories\24609\wpresourcesafter editing the files I rebooted the server and still come up with the same generic errror. "Unknown Error". This comes up on both servers in farm and timer job status. All other links in central administration work fine. Also error 6772 still comes up every 15 minutes. After 2 reborts it always comes up on the hour or a few seconds after, then exactly 13, 30, and 45 minutes after the hour or a few seconds after. I am not sure if any of his helps but I am not sure what to try next.ThanksRay

hi Lambert,I am not sure what else I should try, do you think I have to re-install Sharepoint Services?ThanksRay

To resolve the problem we did the following. We disconnected the existing configuration database from the farm and created a new configuration database using the sharepoint products and technologies configuration wizzard. We created a new web application with blank site template and deleted the empty database from the content database from the web application. We attached the old content database to the web application.All the errors are gone and the links work now. Although it sounds like a lot it took about 10 minutes to do.Ray