locked
OWSTIMER.EXE - Not completing in 5 minute interval RRS feed

  • Question

  • 05/16/2011 12:22:29.99  OWSTIMER.EXE (0x0AF0)                    0x0B10 Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job 'Config Refresh', id '{AE41A525-5211-4751-B564-DC8C2DD3612B}' for service '{E6A1267B-7EB9-4ED6-8E1A-2B58A949C89A}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.

    Looking to find out how to trouble shoot this problem.   How do lookup the GUIDs and figure out why the timer job is not completing within 5 minutes.   Any Help would be great.  I cannot increase the interval due to business constraints.


    Moojjoo MCP, MCTS
    MCP Virtual Business Card
    http://www.mmebs.com
    Monday, May 16, 2011 4:28 PM

All replies

  • Hi,

    Thanks to share your post.

    For the issue, please get a handle on the logs and their size.

    1.       You should firstly install the Microsoft office SharePoint server 2007 Beta 2.

    2.       Open up c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\logs.

    3.       Startup Task Manager, find wsstracing.exe, and note its' neurotic CPU Utilization and growing memory usage

    4.       Start SharePoint 3.0 Central Administration (you might have to pause the Windows SharePoint Timer service before you can actually get there especially if you're using a VPC - for whatever reason, OWSTIMER.EXE can easily soak up whatever CPU cycles you have...)

    5.       Go to Operations

    6.       Under Logging and Reporting, choose Diagnostic Logging under Event Throttling, choose All as the category (this may be unnecessary, as it could be the default, but judging by the amount of

    7.       Logging, it probably isn't) Under Trace Log, set "Number of log files" to something reasonable – say.

    8.       You can leave "Number of minutes..." to be 30, unless you want those 5 files to be smaller in size. At the default rate, a 30 minute trace files in my case seems to be about 200MB.

    9.       Click OK.

    You can see that if you don't reduce logging amounts, you're likely to run out of disk space on your system drive.

    Hope this could help you!

    Leo

     

    Wednesday, May 18, 2011 8:18 AM
  • Leoyi Sun, The logs are not causing an issue. The logging is not a problem, I need to know why this timer job is not completing? Are you saying that the logging has to something to do with the timer job? Again we are having issues with immediate alerts completing every 5 mintus and we do notice this is only happening on 1 of our 3 Web Front End servers that is causing the problem. This raises another question if we turn the timer job off for that one server will the timer job for immediate alerts failover to one of the other servers?
    Moojjoo MCP, MCTS
    MCP Virtual Business Card
    http://www.mmebs.com
    Wednesday, May 18, 2011 2:16 PM