Contents
In Windows Explorer, navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, and open the newest log in the folder using a text editor. Use Find function in the text editor to locate the correlation id.
The correlation ID is not an error number or code. Simply, it’s a GUID (globally unique identifier) that’s automatically generated for every request that the SharePoint server receives. The correlation ID is meant to be used to help a SharePoint Admin trace what was happening at the time of an error.
You have to check the ULS logs file ( from hive folder), you have to check for exact time logs ( by default, every 30 min SharePoint create a new log file). Another way is run the below mentioned PowerShell to get the logs for a correlation id.
When to use a correlation ID token in SharePoint?
In SharePoint 2010, you’ve got some new capabilities for error reporting and logs. One of the most noted features for me as a developer is that whenever you bump into an error message – you’ll be presented with a correlation ID token.
How to find log messages based on correlation ID token?
Using PowerShell to lookup a log message based on Correlation ID token One of the quick-n-awesome ways to do this is to simply hook up a PowerShell console (SharePoint 2010 Management Shell) and then just write the following command (replace the with the Correlation Id): get-splogevent | ? {$_.Correlation -eq “GUID” }
What is the correlation ID in an error message?
The correlation ID is notan error number or code. Simply, it’s a GUID (globally unique identifier) that’s automatically generated for every request that the SharePoint server receives. It’s unique to each request, not each error. However, when an error occurs, the error message contains the correlation ID that was valid for the request at the time.