What?
We have setup a new SharePoint 2010 production farm with 2 web servers. (One WFE and one APP). In the new farm, we have started to see a critical issue in the health analyzer that says "The following servers have not executed any timer jobs in the last 2 hours"
Why?
After some trouble shooting which included restarting the timer service on both servers and executing the PowerShell script below, we have figured that the timer services are running fine. But the event logger is full of the above exceptions.
$farm = Get-SPFarm
$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
if ($disabledTimers -ne $null)
{
foreach ($timer in $disabledTimers)
{
Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status
}
}
else
{
Write-Host "All Timer Service Instances in the farm are online! No problems found"
}
It finally turned out to be an issue with time difference in the 2 web servers.
There was about 14 hours of time difference between the 2 web servers.
How?
We synced the time between the 2 servers and restarted SP timer service on both web servers and the error disappeared
We have setup a new SharePoint 2010 production farm with 2 web servers. (One WFE and one APP). In the new farm, we have started to see a critical issue in the health analyzer that says "The following servers have not executed any timer jobs in the last 2 hours"
Why?
After some trouble shooting which included restarting the timer service on both servers and executing the PowerShell script below, we have figured that the timer services are running fine. But the event logger is full of the above exceptions.
$farm = Get-SPFarm
$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
if ($disabledTimers -ne $null)
{
foreach ($timer in $disabledTimers)
{
Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status
}
}
else
{
Write-Host "All Timer Service Instances in the farm are online! No problems found"
}
It finally turned out to be an issue with time difference in the 2 web servers.
There was about 14 hours of time difference between the 2 web servers.
How?
We synced the time between the 2 servers and restarted SP timer service on both web servers and the error disappeared
No comments:
Post a Comment