SharePoint 2010 'Immediate Alerts' Timer Job Stuck at 93% consumes all memory on server

Traitée SharePoint 2010 'Immediate Alerts' Timer Job Stuck at 93% consumes all memory on server

  • mardi 31 juillet 2012 08:14
     
     

    Hi all,

    I am having an issue with a timer job that consumes all the memory on my web front end. I have stopped the timer job for now, otherwise the server eventually stops responding.

    Problem

    The faulting timer job is:

    'Immediate alerts'

    This is an out of the box timer job that is scheduled to run every 5 minutes so I do not see why it should have any memory leaks.

    The timer job gets stuck at 93% and eventually consumes all the memory on the server.

    The only relevant message I can find in the ULS logs even with verbose logging is:

    The previous instance of the timer job '

    Immediate Alerts', id '{1CE8C3F8-3C64-4AAB-B6DB-41D5E44AE4D1}' for service '{8D36E1C8-CA62-4083-96A5-ED6E2D4D0D66}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.

    Attempted solutions

    1. Cleared the XML cache by deleting the XML files in the GUID folder and resetting cache.ini to 1.
    2. Stopped the SharePoint Timer Service and restarted it.
    3. Rebooted all SharePoint servers.
    4. Re-rant the SharePoint Products Configuration Wizard

    None of the above solutions have worked for me.

    Your advice would be greatly appreciated.


    • Modifié Andrew Toh mardi 31 juillet 2012 08:15
    •  

Toutes les réponses

  • vendredi 3 août 2012 04:37
     
     Traitée

    Hi,

    According to your error message, firstly, please check it you have installed any antivirus software on your SharePoint server, which could cause the alert timer job dysfunctions.

    Secondly, for high memory issue, you can also migrate some applications from the problematic SharePoint server to another server.

    Thanks,

    Rock Wang


    Rock Wang TechNet Community Support

  • mardi 7 août 2012 00:21
     
     Traitée

    It turns out that a custom solution was causing the timer job problems. Once we re-deployed the solution the timer job started working properly again.

    Thanks for the advice.

    • Marqué comme réponse Andrew Toh mardi 7 août 2012 00:21
    •