OWSTIMER.exe message overflow Sharepoint log files

A somewhat known issue of getting Sharepoint log messages like,

03/19/2010 16:25:05.95  OWSTIMER.EXE (0x0794)                    0x0A54 Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{98B057E8-AD9C-46DC-A5EC-F69ED2550AF1}’ for service ‘{A1E122AE-D22D-46F7-A5F1-EF4DA0D549C4}’ is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.


03/19/2010 16:25:05.95  OWSTIMER.EXE (0x0794)                    0x0A54 Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{98B057E8-AD9C-46DC-A5EC-F69ED2550AF1}’ for service ‘{A1E122AE-D22D-46F7-A5F1-EF4DA0D549C4}’ is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.
03/19/2010 16:25:05.95  OWSTIMER.EXE (0x0794)                    0x0A54 Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{98B057E8-AD9C-46DC-A5EC-F69ED2550AF1}’ for service ‘{A1E122AE-D22D-46F7-A5F1-EF4DA0D549C4}’ is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.

Couple of workarounds and/or fixes:

  1. Check the Central Admin Operations Diagnostic Logging. Often the log level is set to log “Warning” level – set higher
  2. Add more time for the Config Refresh job: stsadm -o setproperty -pn job-config-refresh -pv "Every 5 minutes between 0 and 59"

2 thoughts on “OWSTIMER.exe message overflow Sharepoint log files”

Comments are closed.