• Like
  • Save
Correlation id token in share point 2010
Upcoming SlideShare
Loading in...5
×
 

Correlation id token in share point 2010

on

  • 2,572 views

 

Statistics

Views

Total Views
2,572
Views on SlideShare
2,572
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Correlation id token in share point 2010 Correlation id token in share point 2010 Document Transcript

    • SP 2010: Find error messages with a <br />Correlation ID token in SharePoint 2010<br />Author: Tobias Zimmergren http://www.zimmergren.net | http://www.tozit.com | @zimmergren<br />Introduction<br />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.<br />In this article I will try to explain how you can fetch that token from SharePoint, and also provide a small snippet of code to be able to build your own “Log Searcher Web Part” for your administrators.<br />Correlation ID, what’s that?<br />In SharePoint 2010, you get a Correlation ID (which is a GUID) attached to your logs/error messages when something happens. This ID can then be used to lookup that specific error from the logs.<br />This Correlation ID is used per request-session in SharePoint 2010, and if you are in the process of requesting some information from SharePoint and bump into some problems along the way – your Correlation ID will be the best starting point for searching for what went wrong along that request!<br />You might get an error message like this in SharePoint 2010 (don’t worry, if you haven’t seen one like this one yet – just hang in there, sooner or later you will.. )<br />Search for the log messages based on the Correlation ID token<br />So if you’ve gotten such an error message and want to find out more information about the actual error and don’t have the time to go around poking in the logs and searching – there’s a few methods you can do this rather easily, as described below. <br />Using PowerShell to lookup a log message based on Correlation ID token<br />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 <GUID> with the Correlation Id):<br />get-splogevent | ?{$_Correlation -eq " <GUID>" }<br />This will give you the details about your specific error like this in the console:<br />You might want to be more precise and get more specific details out of your query, then you can try something like this:<br />get-splogevent | ?{$_.Correlation -eq " <GUID>" } | select Area, Category, Level, EventID, Message | Format-List<br />This will give you the details about your specific error like this with some juicy details:<br />Finally if you would want these messages to be put into a text or log file instead, you could just add the classic “> C:Awesome.log” after the command like this:<br />get-splogevent | ?{$_.Correlation -eq " <GUID>" } | select Area, Category, Level, EventID, Message | Format-List > C:Awesome.log<br />On MSDN they have an overvoew of using SP-GetLogEvent which I would recommend!<br />Using SQL queries to find log message based on Correlation ID token<br />You can utilize the SQL logs database to fetch the specific error message based on Correlation id as well. In your logging DB (usually called WSS_Logging, but can be called something else if you’ve changed it) there is a view called ULSTraceLog which you can query with a simple SQL query and fetch the results.<br />I’ve created a query to fetch the items from the logging database like this: <br /> select [RowCreatedTime], [ProcessName], [Area], <br /> [Category], EventID, [Message] <br /> from [WSS_UsageApplication].[dbo].[ULSTraceLog] <br /> where CorrelationId=< pre>'B4BBAC41-27C7-4B3A-AE33-4192B6C1E2C5'<br />This will render your results in the SQL Query window like this:<br />This can of course be implemented in a Web Part for your convenience as well (I’ve created a bunch of diag. and logging web parts that I’ve got deployed to Central Admin) that could look like this (this way you don’t need physical access to the ULS logs all the time, but can do a quick lookup from the web part):<br />Get the current Correlation ID by using code<br />I got this piece of code from my good friend Wictor’s blog post. Thanks Wictor – this made my Logging-project more satisfying!<br />With the following code you can fetch the current Correlation Id of a request.<br />Create a method (in my case called GetCurrentCorrelationToken()) to wrap up the functionality of returning the current token like this:<br /> public class CorrelationId <br /> {<br /> [DllImport (" advapi32.dll" )]<br /> public static extern uint EventActivityIdControl(uint controlCode,ref Guid activityId);<br /> public const uint EVENT_ACTIVITY_CTRL_GET_ID = 1;<br /> public static Guid GetCurrentCorrelationToken()<br /> {<br /> Guid g = Guid .Empty;<br /> EventActivityIdControl(EVENT_ACTIVITY_CTRL_GET_ID, ref g);<br /> return g;<br /> }<br /> }<br />Then from wherever in your code you can simply call it by using this approach:<br /> protected void Button1_Click(object sender, EventArgs e)<br /> {<br /> Label1.Text = CorrelationId .GetCurrentCorrelationToken().ToString();<br /> }<br />(Normally you might want this in a try/catch statement or something like that)<br />Summary<br />This article should give you (administrator and developer) an insight in how you easily can track the specific errors your users encounter in their/your application(s). If a user gets an error message in SharePoint 2010, they’ll also see the Correlation ID. <br />If you can train your users to write down that Correlation ID along with a few simple steps on how the error might have been occurring, you’re going to have a much easier way to find the details about that specific error than ever before.<br />