none
unknown error returned for "Servers in Farm" and "Timer job Status" RRS feed

  • Question

  • When using central administration and SharePoint services 3.0 SP1 I receive an unknown error when I click on servers in farm or timer job status.  I can't seem to find any errors in the logs except for the ones listed below. I'm not sure if they have something to do with the problem. I currently have one server hosting the database and another server hosting the web applications. Is there something I can look at to try to correct this problem? Thank you for your help.

    Timestamp               Process                                  TID    Area                           Category                       EventID Level      Message  Correlation
    11/03/2009 11:50:43.56  OWSTIMER.EXE (0x0654)                    0x0660 ULS Logging                    Unified Logging Service        8wsv High     ULS Init Completed (OWSTIMER.EXE, onetnative.dll) 
    11/03/2009 11:50:43.57  OWSTIMER.EXE (0x0654)                    0x0660 Windows SharePoint Services    Topology                       0 Medium   Diagnostics settings: 32768 
    11/03/2009 11:51:43.09  wsstracing.exe (0x0664)                  0x0684 ULS Logging                    Unified Logging Service        uls1 Monitorable Tracing Service lost trace events.  Current value 1. 
    11/03/2009 11:51:43.68  OWSTIMER.EXE (0x0654)                    0x0660 Windows SharePoint Services    Timer                          75eb Monitorable SPTimerStore.InitializeTimer: SPConfigurationDatabase.RefreshCache returned SPConstants.InvalidRowVersion 
    11/03/2009 11:51:43.68  OWSTIMER.EXE (0x0654)                    0x0660 Windows SharePoint Services    Timer                          5utx Unexpected The timer service could not initialize its configuration, please check the configuration database.  Will retry later. 
    11/03/2009 11:52:43.55  OWSTIMER.EXE (0x0654)                    0x0660 Windows SharePoint Services    Timer                          75eb Monitorable SPTimerStore.InitializeTimer: SPConfigurationDatabase.RefreshCache returned SPConstants.InvalidRowVersion 
    11/03/2009 11:52:43.55  OWSTIMER.EXE (0x0654)                    0x0660 Windows SharePoint Services    Timer                          5utx Unexpected The timer service could not initialize its configuration, please check the configuration database.  Will retry later. 
    11/03/2009 11:52:49.26  psconfigui.exe (0x0C5C)                  0x0C60 ULS Logging                    Unified Logging Service        8wsv High     ULS Init Completed (psconfigui.exe, onetnative.dll) 
    11/03/2009 11:52:49.62  psconfigui.exe (0x0C5C)                  0x0C60 ULS Logging                    Unified Logging Service        8wsw High     Now terminating ULS (psconfigui.exe, onetnative.dll) 
    11/03/2009 11:52:49.26  psconfigui.exe (0x0C5C)                  0x0C60 Windows SharePoint Services    Topology                       0 Medium   Diagnostics settings: 32768 
    11/03/2009 11:53:00.59  w3wp.exe (0x0D94)                        0x0DE8 ULS Logging                    Unified Logging Service        8wsv High     ULS Init Completed (w3wp.exe, onetnative.dll) 
    11/03/2009 11:53:00.61  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    Topology                       0 Medium   Diagnostics settings: 32768 
    11/03/2009 11:53:01.73  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8dzw Medium   spHttpHandler:GetHash started 
    11/03/2009 11:53:01.81  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8dzx Medium   spHttpHandler:GetHash finished 
    11/03/2009 11:53:03.79  w3wp.exe (0x0D94)                        0x0E24 Windows SharePoint Services    General                        0 Medium   Windows SharePoint Services log file                                                                                                                                                                                                                                                                                                                                                                    
    11/03/2009 11:53:04.32  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        6y1a Medium   Creating reg key "SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports" 
    11/03/2009 11:53:04.71  w3wp.exe (0x0D94)                        0x0DE8                                435                            94vw Medium   Primary Domain = BELLCARTER, Computer Name = SPSVR01 
    11/03/2009 11:53:06.36  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "XomlUrl", keyfile core. 
    11/03/2009 11:53:06.36  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
    11/03/2009 11:53:06.36  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "RulesUrl", keyfile core. 
    11/03/2009 11:53:06.36  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
    11/03/2009 11:53:10.59  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "DistributionLists_Alias", keyfile core. 
    11/03/2009 11:53:10.59  w3wp.exe (0x0D94)                        0x0DE8 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'DistributionLists_Alias' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". 

    Tuesday, November 3, 2009 8:14 PM

Answers

  • 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
    • Marked as answer by Ray Rogers Wednesday, April 28, 2010 7:25 PM
    Wednesday, March 3, 2010 8:42 PM

All replies

  • Hi Ray Rogers,

     

    Please follow the steps below to clear the file system cache on all the servers in the server farm on which the Windows SharePoint Services Timer service is running:

    http://blogs.msdn.com/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx

    After clear the cache, start the timer service on all servers in the server farm and go to “Central Administration” à “Operations” à”Timer job status” to see if it solves the problem and ensure the status of “Config Refresh” is “Succeeded”.

     

    Hope this helps.

     

    Lu Zou

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com


     

    Wednesday, November 4, 2009 6:57 AM
  • Hi Lu,

    Thank you for the response. It is installed on a Windows 2003 server and this is the only subdirectory I have located in the "config" directory. This directory is currently empty and I did not see the.ini file in there. Could that be the problem the.ini file is missing?

    C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\00000000-0000-0000-0000-000000000000

    Thank you for your help,
    Ray
    Monday, November 9, 2009 6:31 PM
  • Hi Ray Rogers,

     

    Thanks for your update. I’m not sure if the error is caused by this. Does the GUID is all zero or you use zero to replace the actual number out of privacy consideration? Did you mean that when you get into the folder which name is the GUID, there is no file there? If so, please create a new notepad file called “cache.ini” and enter number “1” then save it. Wait for some time to see if the number will increase.

     

    What’s more, I suggest you install WSS SP2 and run configuration wizard as soon as possible.

     

    Lu Zou

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com

     

    Tuesday, November 10, 2009 10:00 AM
  • Hi Lu,

    The file is actually all zero's I did not change it.  I have created the following files C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\00000000-0000-0000-0000-000000000000\cache.ini with a 1 in it.  I will let you know if it changes.  I will also try to schedule SP2 upgrade in the next couple of days.  Thanks for your help.

    Ray
    Wednesday, November 11, 2009 7:54 PM
  • Hi Lu,

    Sorry for the delay on this.  We did finally apply SP2 and we are receiving the same problem.  Is there anything else I could look at?
    Sunday, January 24, 2010 10:17 PM
  • Hi Lu,

    this ie the error I receive every 15 minutes.  It is event ID 6772.

    There was an internal error invoking the timer job '{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}' for service '{00000000-0000-0000-0000-000000000000}'.

    Thanks
    Ray

    Monday, January 25, 2010 4:57 AM
  • 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
    • Marked as answer by Ray Rogers Wednesday, April 28, 2010 7:25 PM
    Wednesday, March 3, 2010 8:42 PM