Hi All,
We're currently testing SharePoint 2013 and aim to upgrade to it from 2010 fairly soon.
We have configured the diagnostic settings to only log the Unexpected events to the trace log, which is how we have it setup in 2010. However we are noticing that our trace logs are getting big very quickly and are filled with trace events that are lower then Unexpected, eg High and Medium. We also notice the vast majority of the events have [Forced due to logging gap...] in them and their original level can be as low as Verbose.
Does anyone have this same issue and is there a way to force the ULS trace logs to behave as they did in 2010; ie as they are configured to do so in Central Admin. Short of disabling the tracing service I'm at a loss. We don't really want to go live with this state as currently each page request results in the log file growing.
Any help on this would be much appreciated,
Andrew
EDIT: We've done a bit more testing and even setting all the categories in Central Admin to None still produces a lot of trace logs, which is completely unexpected from our point of view.
We've also noticed that we get a lot of entries like this:
07/24/2013 16:37:28.56 w3wp.exe (0x2204) 0x0DAC SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: (none)
I cannot find anything on the internet about Micro Trace at all. I've double checked the settings for this category in Central Admin and its trace level is set to None.
