I recently cleared the cache on all 3 servers in my farm and the Health Analyzer (HA) showed " One or More Servers is not responding" for both the APP and WFE server. This happened once before where the Profile Synch config file was locked as a .tmp file. I paused the synch service, timer and administration service and removed the files, did an IIS reset and unpaused stuff. The cache rebuilt successfully. Problem solved right? Nope.
Now instead of the APP and WFE both not responding the HA reported only the WFE was not responding. I ran the config wizard and hit reanalyze on the HA rule. Still came up as not responding.
Next I removed and reattached the WFE to the farm using the config wizard. This all went successfully but the rule persisted after reanalyzing.
In the Manage Services on Server page in CA for the WFE I change the view from 'Configurable' to 'All' and there is no entry under Status and Action for 'Microsoft SharePoint Foundation Administration' and 'Microsoft SharePoint Foundation Timer' but this is the same on all servers in the farm so perhaps this is normal?
I ran Initialize-SPResourceSecurity on the WFE, reanalyzed but the HA still reports this issue.
The following entries are in the ULS Logs:
The following error occured while trying to initialize the timer: System.NullReferenceException: Object reference not set to an instance of an object.
at System.Object.GetType()
at Microsoft.SharePoint.Administration.SPTimerStore.GetLocalProvisionedServices(Boolean cacheOnlineInstances)
at Microsoft.SharePoint.Administration.SPTimerStore.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy)
at Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy)
The timer service could not initialize its configuration, please check the configuration database. Will retry later.
Exiting the process because the timer could not be initialized after multiple attempts.
The timer service is stopping
Now terminating ULS (OWSTIMER.EXE, onetnative.dll)
When checking the services.msc the timer service is in fact running
Any ideas on what to try next?
Love them all...regardless. - Buddha
