When working with SharePoint it’s inevitable that at some point you will come across a Correlation ID on your screen! These are invaluable for tracking down issues when you’re building new functionality – and are handily displayed in the onscreen error messages so that they can be plugged into ULS Viewer to track down the root cause…
However, what if there’s an issue that you want to track down that doesn’t result in the error message being displayed? E.g. perhaps something isn’t firing when it should and you need to track down this “non-event”.
Well, thanks to a little trick gleaned from working with the talented Jaap Vossers, I’ve seen that this is easy to do! Fiddler is an invaluable tool for all web development, and SharePoint is no exception. What is really useful in this scenario is that SharePoint returns the Correlation ID as a HTTP response header – as you can see in the screenshot below the SPRequestGuid is what we’re after.
Nice post. By the way in IE 9 you will see the correlation id too. All you need to do is enable network network capturing from the F12 developer tool bar. This will also only capture your current IE request which is quite handy.
greetings
Stefan
Thanks Stefan! I think it might be time for me to start using IE9…
Nice find.
You got to love these little gems … I should look at remote ULS to make the step to having relevant log entries short and right there on the client machine, so that the error can be quickly tied to logging info..