locked
All events logging at 'High' level RRS feed

  • Question

  • Hello forum,

    Appreciate your thoughts on this unusual problem that I've discovered in my SharePoint 2013 event log.

    In looking back through my SharePoint logs, they're filled with nothing but 'High' level entries whose descriptions all start with 'Forced due to logging gap'. I can't find anything to help identify what's happening here.

    Here's some samples of what I'm seeing:

    • 04/20/2014 20:42:35.46 w3wp.exe (0x2B08) 0x1BD8 SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 8d3e899c-7d83-8001-0d61-da28a6f1201c
    • 04/20/2014 20:42:35.46 w3wp.exe (0x2B08) 0x1BD8 SharePoint Foundation General 8dzx High [Forced due to logging gap, cached @ 04/20/2014 20:42:32.98, Original Level: Medium] SPHeaderManager:GetHash finished 8d3e899c-7d83-8001-0d61-da28a6f1201c
    • 04/20/2014 20:42:35.46 w3wp.exe (0x2B08) 0x1BD8 SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 8d3e899c-cd29-8001-0d61-d001954ce706
    • 04/20/2014 20:42:35.46 w3wp.exe (0x2B08) 0x1BD8 SharePoint Foundation Asp Runtime aj1kl High [Forced due to logging gap, cached @ 04/20/2014 20:42:32.80, Original Level: Verbose] SPRequestModule.PreRequestExecuteAppHandler 8d3e899c-cd29-8001-0d61-d001954ce706
    • 04/20/2014 20:42:30.76 w3wp.exe (0x2B08) 0x216C SharePoint Foundation Monitoring nass High [Forced due to logging gap, cached @ 04/20/2014 20:42:30.64, Original Level: Verbose] ____{0}={1} 8b3e899c-0d98-8001-0d61-de94d28f2443
    • 04/20/2014 20:42:30.64 w3wp.exe (0x2B08) 0x216C SharePoint Foundation Monitoring b4ly High [Forced due to logging gap, Original Level: High] Leaving Monitored Scope ({0}).{1} 8b3e899c-0d98-8001-0d61-de94d28f2443
    • 04/20/2014 20:42:30.96 w3wp.exe (0x2B08) 0x216C 0x119005 8x0b High [Forced due to logging gap, cached @ 04/20/2014 20:42:30.79, Original Level: Medium] AppDomainUnloadListener.RegisterSelf() about to call HostingEnvironment.RegisterObject(this={0}) 8b3e899c-0d98-8001-0d61-de94d28f2443
    • 04/20/2014 20:42:30.76 w3wp.exe (0x2B08) 0x216C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 8b3e899c-0d98-8001-0d61-de94d28f2443
    • 04/20/2014 20:42:30.64 w3wp.exe (0x2B08) 0x216C SharePoint Foundation General ejq6 High [Forced due to logging gap, cached @ 04/20/2014 20:42:30.37, Original Level: Medium] Storing a(n) {0} object in the site property cache.  Value: {1} 8b3e899c-0d98-8001-0d61-de94d28f2443

    Am planning to apply the latest CU's to the system but feel like I want to have a handle on what I'm looking at here before starting something else.

    Thanks for your thoughts.
    Jamie

    Monday, April 21, 2014 1:34 AM

Answers

  • Hi Jamie,

    Turn OFF Verbose Logging

    In Central Administration, on the home page, click Monitoring. On the Monitoring page, in the Reporting section, click Configure diagnostic logging. On the Diagnostic Logging page, in the Event Throttling section, configure event throttling as follows:

    To configure event throttling for all categories:

    1. Select the All Categories check box.

    2. Select the event log level from the Least critical event to report to the event log list. Set to Warning

    3. Select the trace log level from the Least critical event to report to the trace log list. Set to High

    Use the Verbose setting sparingly! only when trouble shooting and issue. Then turn it off. The Logging GAP is most likely due to having Verbose Logging enabled on all categories and along with Event Log Flood Protection.

    Leave event flood protection enabled  and monitor after you have made the changes above..

    Reference: http://technet.microsoft.com/en-us/library/ee748656(v=office.15).aspx 

    clip_image001 clip_image002 clip_image003 clip_image004 clip_image006 clip_image008


    -Ivan

    Monday, April 21, 2014 2:11 AM

All replies

  • Hi Jamie,

    Turn OFF Verbose Logging

    In Central Administration, on the home page, click Monitoring. On the Monitoring page, in the Reporting section, click Configure diagnostic logging. On the Diagnostic Logging page, in the Event Throttling section, configure event throttling as follows:

    To configure event throttling for all categories:

    1. Select the All Categories check box.

    2. Select the event log level from the Least critical event to report to the event log list. Set to Warning

    3. Select the trace log level from the Least critical event to report to the trace log list. Set to High

    Use the Verbose setting sparingly! only when trouble shooting and issue. Then turn it off. The Logging GAP is most likely due to having Verbose Logging enabled on all categories and along with Event Log Flood Protection.

    Leave event flood protection enabled  and monitor after you have made the changes above..

    Reference: http://technet.microsoft.com/en-us/library/ee748656(v=office.15).aspx 

    clip_image001 clip_image002 clip_image003 clip_image004 clip_image006 clip_image008


    -Ivan

    Monday, April 21, 2014 2:11 AM
  • Thank you Ivan! I just realized I never wrote back my thanks to you. That did the trick.

    Best regards,
    Jamie


    Jamie T

    Monday, May 5, 2014 5:56 PM