locked
The previous instance of the timer job 'Workflow Failover', RRS feed

  • Question

  • Hi,

    My SharePoint log files are filling up enormously (almost in Giga Bytes) with the following error messages

    " The previous instance of the timer job 'Workflow Failover', id '{33A54D54-A6B2-4CC6-811A-511278D46DE9}' for service '{D418228F-D0D2-475C-BF75-0F52F01D4271}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs. "


    Can anyone explain how to solve this issue? Any help in this regard will be greatly appreciated...



    Muhammad Tariq khan
    Tuesday, February 22, 2011 6:28 AM

Answers

  • Hi Muhammand,

    Please restart your Time service to have a try.
    If it don't work. Please clear the file system Cache follow this KB.
    http://support.microsoft.com/kb/939308
    This issue occurs if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database. When this data became corrupted, we may have to manually clear the file system cache on the local server.

    Thanks & Regards,
    Emir 

    • Marked as answer by Emir Liu Wednesday, March 2, 2011 2:25 AM
    Friday, February 25, 2011 7:08 AM

All replies

  • Do you have Custom Timer Jobs running in your SharePoint environment?
    Thanks & Regards, Neerubee
    Tuesday, February 22, 2011 6:30 AM
  • No. I have not set any custom timer job.
    Muhammad Tariq khan
    Tuesday, February 22, 2011 6:33 AM
  • Hi Muhammand,

    Have you installed security update 931212 (MS07-040) on WSS 3.0/MOSS 2007 web frount-end server?
    If yes, please read this KB, and try the workaround.
    http://support.microsoft.com/kb/941789

    Best regards,
    Emir

    Wednesday, February 23, 2011 1:07 PM
  • Hi Muhammand,

    Please restart your Time service to have a try.
    If it don't work. Please clear the file system Cache follow this KB.
    http://support.microsoft.com/kb/939308
    This issue occurs if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database. When this data became corrupted, we may have to manually clear the file system cache on the local server.

    Thanks & Regards,
    Emir 

    • Marked as answer by Emir Liu Wednesday, March 2, 2011 2:25 AM
    Friday, February 25, 2011 7:08 AM