- Go to Central Administration
- Select Monitoring
- Select Configure Diagnostic Logging from the Reporting area
- Check the ALL checkbox at the top
- From the drop-downs select:
- Least event to report to the event log: Error (you can play with Critical vs. Warning as well)
- Least critical event to report to the trace log: Verbose (this will give you the full trace log for that Correlation ID)
- Replicate your issue and note the Correlation ID
- Before you do anything else, go back into the Configure Diagnostic Logging screen
- Check the ALL checkbox at the top
- From the drop-downs select:
- Least event to report to the event log: Reset to default
- Least critical event to report to the trace log: Reset to default
- This will make sure that your logs don't explode while you're troubleshooting.
Working full time with SharePoint, BI, and Project Server. A place for posting those things that I find useful and may help out others in the future.
Thursday, December 20, 2012
SharePoint ULS Logging for Better Troubleshooting
I started running into problems with Correlation IDs in SharePoint 2010 not showing up in my ULS logs. Here's how I ended up logging all of the details for a repeatable issue.
Subscribe to:
Posts (Atom)