7

This might sound noob but it's pretty annoying. Instead of receiving a nice error message, SharePoint 2010 throws you a page saying that there is an error and it gives you a Correlation ID.

WTF is a Correlation ID. What can I do to find out the exact error that actually occurred?

It seems like we've returned to the good old win98 days where the error was 0x80002330.

Aakash Maurya
  • 8,481
  • 4
  • 42
  • 74
Mihai Lazar
  • 191
  • 1
  • 3
  • 11

6 Answers6

14

You can use the ULS logs in the 14-hive/logs, and search for the correlation ID. You will then get all messages related to that correlation ID. You can either look through the text file, or use the ULS Viewer.

Alternatively, you can execute e.g. this Powershell command to get the messages with this correlation id:

Get-SPLogEvent | ?{$_.Correlation -eq "YOUR-CORRELATION-ID-HERE"} |
ft Category, Message -Autosize
Aakash Maurya
  • 8,481
  • 4
  • 42
  • 74
tarjeieo
  • 2,538
  • 1
  • 27
  • 39
  • 1
    One caveat to this method is that it will peg resources to the max. On our prod server this took us to 99% utilization, and we had to cancel the query after 5 minutes, no result yet. – Tom Halladay Jul 28 '11 at 15:17
  • 3
    Also, for us newbies who don't have the 14-hive location memorized, it's: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS – Tom Halladay Jul 28 '11 at 17:35
  • 1
    Tom; Yes, that's definitively something to be vary of. You can limit the search interval by time though, by adding starttime and endtime parameters, example: Get-SPLogEvent -StartTime "12/04/2007 17:00" -EndTime "12/04/2007 18:00" (http://technet.microsoft.com/en-us/library/ff607589.aspx) – tarjeieo Jul 29 '11 at 07:49
3

The correlation ID is the unique identifier for the request, not for the error itself.

In simple cases, it can be used to quickly search the logs to get a more detailed error message (e.g with a stack trace) than what was shown to the user. You can either search the trace log files or the logging database with that correlation ID and you'll get every log message related to that request. In more complex cases, the error might have been caused by something that happened earlier in the page's life cycle, so being able to narrow your search will get you the information you need faster.

The correlation ID is written to the end of each line in the trace log files, which are by default stored in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGSlike Tom Halladay said. Alternatively, you can search the WSS_UsageApplication database's ULSTraceLog view, which has a separate field for the correlation ID.

Hirvox
  • 202
  • 1
  • 7
0

If you have a multi-server farm, a correlation ID or other parameters can be used to correctly merge the logs from every server into one file using the Merge-SPLogFile cmdlet, which I highly recommend.

Alexey Krasheninnikov
  • 2,750
  • 2
  • 24
  • 42
0

There are 2 ways to find the solutions:

  1. Run the Get-SPLogEvent Windows Powershell cmdlet:

    Get-SPLogEvent | ?{$_.Correlation -eq "Correlation ID"} | ft Category, Message -Autosize

  2. View the ULS (Unified Logging Service)

    This is a tab on the Developer Dashboard.

Paul Strupeikis
  • 3,818
  • 4
  • 20
  • 33
ervistrupja
  • 5
  • 1
0

You can use SharePoint 2010 Management Shell and use this command to read error behind correlation ID

get-splogevent | ?{$_.Correlation -eq "CORRELATION ID"} | select Area, Category, Level, EventID, Message |Format-List

Read more How to find real error in Sharepoint 2010 based on Correlation ID of the error

Aakash Maurya
  • 8,481
  • 4
  • 42
  • 74
user18553
  • 1
  • 1
-2

You can execute query shown below inside your SharePoint database.

select [RowCreatedTime], [ProcessName], [Area],
[Category], EventID, [Message]
from [WSS_UsageApplication].[dbo].[ULSTraceLog] where CorrelationId= 'B4BBAC41-27C7-4B3A-AE33-4192B6C1E2C5'

You can find more details available here