correlation id is missing in the Log

Question

I have a handful of correlation id that I need to see in the log what happened this morning when a co-worker checkout the aspx file so he can modify something. upon checkout the whole portal became inaccessible and start giving "an unexpected error has occurred" which came with correlation ID. (see print shot).

I went through the log back and forth and not finding anything that matches those correlation ID. Could it be I need to turn on more logging via central admin diagnostic area? Please suggest.

I even open the Windows explorer search on sp server where the log is and still could not find it that way.

Answer 1

Maria , a common mistake while finding corelation ids is the way it is copied from the browser it generally comes with an extra space at the end. So when we search this using notepad or any other log reader using Ctrl + F it does not come up. Can you confirm this and let us know if the id is copied without spaces.

It suggested you copy the corelation id to notepad first and then copy the required text and then do a search on ULS.

--

Now , if you did copy the corelation id without that extra space, please ensure that you have sorted the ULS log files correctly according to the last modified date in the windows explorer. And then make a search on the sorted ULS files based on the time range.

A suggested way of exploring the ULS would be using the tool ULS Viewer , which can take inputs from multiple ULS log files and sort based on various columns like exception type, coorelation id ,etc.

--

Thirdly, from the nature of the problem that you posted it looks like checkout of a page causing this issue can have the scope of the root cause to the following :-

1. At any time there must be a masterpage or page layout not at approved or published state for the site where the page is located. This can cause a permission specific errors for the users when they try to access the site or this page. Please check that.

2. Ensure that there are no site quota locks that are reached while this file has been checkout.

3. Validate everything related to the health of the publishing infrastructure of sharepoint at the farm, web application and the site level.

All of the above are just pointers and not exact solution. If you can share the uls dump and corelation id messages we can assist you further.

Thanks.

Answer 2

If tracing is enabled, it should be there in trace logs. Apart from Correlation ID there are other columns in the logs which you can use to find a clue, Time stamp for example. Check the section 3. Trace(ULS) Logs for detailed information here:

Troubleshooting SharePoint 2010 : Tools & Techniques

Answer 3

Here are a few posts that can help you with the Correlation IDs -

• Easily determining the exact error by using Correlation ID in SharePoint 2010
• SharePoint 2010 Correlation ID in error messages: what it is and how to use it
• Working with SharePoint 2010 Correlation ID in PowerShell and code