none
Sharepoint Timer Service Issue on Forefront Identity Manager Server 2010 R2 RRS feed

  • Question

  • Hello All,

    There is a rapid growth in log files upto 21 GB per file under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS which makes the C drive full in server that hold Forefront Identity Manager 2010 R2.

    On checking, one of the log files it shows below entry which is repeating multiple times which makes log files increase.

    Message in Log:

    12/08/2016 15:30:59.99  OWSTIMER.EXE (0x3838)                    0x13DC Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job 'Config Refresh', id '<id>' for service '<service>' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs. 

    Kindly help us on this how to resolve this rapid log file increase.

    Thanks

    Thursday, December 8, 2016 3:42 PM

All replies

  • Hi,

    I believe this will be solved by disabling SharePoint indexing:

    Disabling SharePoint indexing

    It is recommended that you disable SharePoint indexing. There are no documents that need to be indexed, and indexing causes many error log entries and potential performance problems with FIM 2010 R2.

    To disable SharePoint indexing in SharePoint Foundation 2010

    1. On the server that hosts the FIM Portal, click Start, click All Programs, click Microsoft SharePoint 2010 Products and then click SharePoint 2010 Central Administration.

    2. Under Monitoring, click Check job status.

    3. Click SharePoint Services Search Refresh.

    4. On the Edit Timer Job page, click Disable.

    To disable SharePoint indexing in WSS 3.0

    1. On the server that hosts the FIM Portal, click Start.

    2. Click All Programs.

    3. In the All Programs list, click Administrative Tools.

    4. Under Administrative Tools, click SharePoint 3.0 Central Administration.

    5. On the Central Administration page, click Operations.

    6. On the Operations page, under Global Configuration, click Timer job definitions.

    7. On the Timer Job Definitions page, click SharePoint Services Search Refresh.

    8. On the Edit Timer Job page, click Disable.

    Reference:

    https://technet.microsoft.com/en-us/library/hh332711(v=ws.10).aspx

    Best,

    Jeff Ingalls

    Thursday, December 8, 2016 4:23 PM
  • Hello Vignesh,

    Below are instructions on limiting the trace log space used by SharePoint and also deleting the logs.

    Low disk space caused by SharePoint:

    1. Go into SharePoint Central Admin (there will be a start menu shortcut)
    2. Select Monitoring
    3. Under the Reporting Heading select Configure diagnostic logging
    4. Under the Trace Log section ensure that the Restrict Trace Log disk space usage is selected and enter a limit in GB – I went with 2, then click Ok.
    5. Stop the SharePoint 2010 Timer service (in Windows Services) as it holds a lock on the files
    6. You can then either delete the files manually (after stopping the Windows Service Sharepoint Timer Service) or allow SharePoint to self-clean the files based on the new trace log limit.
    7. Delete the older files from C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\LOGS
    8. Startup the SharePoint 2010 Timer service again.

    Thanks.

    Friday, December 9, 2016 6:37 AM