Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

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).

enter image description here

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.

share|improve this question
    
I Have Same Error and the Error is this After getting Correlational information ........... Failed to determine the setup path of the list schema for feature {22A9EF51-737B-4FF2-9346-694633FE4416}, list template 850. db5cadbe-70de-4316-8029-57d353f5f896 Leaving Monitored Scope (Request (GET:address/_layouts/…)). Execution Time=830.7980db5cadbe-70de-4316-8029-57d353f5f896 Entering monitored scope (Request (GET:address/Pages/Forms/AllItems.aspx)) Name=Request (GET:addres/Pages/Forms/AllItems.asp –  Mum umar Oct 24 '12 at 1:45
add comment

3 Answers

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.

share|improve this answer
    
I did all that you mentioned in the first and second step (no space, using uls log, looking at the correct date/time stamped log file, etc.). I am going to concentrate on 3rd list of items you mentioned and see that's the case. –  Maria Burton Jun 1 '12 at 13:47
    
In addition to my answer , please try this powershell command. Get-SPLogEvent | ?{$_.Correlation -eq "yourcorelationidhere"} | ft Category, Message -Autosize –  Arko D Jun 1 '12 at 14:19
add comment

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

share|improve this answer
    
Yeap, Looked at the time frame when the error occurred. Trust me I exhausted all the possibilities before posting it here. –  Maria Burton Jun 1 '12 at 14:44
    
Try to enable debugging in web.config as mentioned in the article. You will see exact error on the page itself –  Amit Kumawat Jun 1 '12 at 15:20
    
cool. I will enable the debugging. –  Maria Burton Jun 1 '12 at 19:52
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.