How to find a correlationID in SharePoint without an error?

Sometimes we are looking for some piece of a request that fails in our SharePoint web application / site-collection / site.....And we are not getting that nice SharePoint error that gives us the correlation id which will help us narrow / pin down the error in the ULS logs.

 In case SharePoint isn't registering an error when your so called "exception" hits it can be difficult to find the culprit in ULS logs. So how then do we get the correlation id if don't get one?

 Simple, download the debugging proxy called "fiddler" from http://www.telerik.com/fiddler. Install fiddler on your client that you are using to debug / analyze the issue at hand. Remember that fiddler must be installed on a client with the necessary access to the sharepoint web application / site-collection / etc.

Open up the fiddler client which will automatically integrate itself in to your browsers (firefox, IE, Chrome, etc.) as a proxy between your client and the SharePoint environment. (Some manual step in Firefox might be needed to allow the plug-in from Firefox to be used in runtime)

Next open up your site and you should see the request manifest itself in the left window inside the fiddler interface. In the fiddler top right window part rightside make sure "Inspectors" is selected and in the lower right side window after that  select "Headers".

The result should look something like:
 Figure A - Fiddler SharePoint Request ID aka Correlation ID

Now open up your SharePoint farm replay the issue and mark in ULS the request id which marked your issue. Open up the SharePoint farm with the issue and use the powershell CMDLet "Merge-splogfile -correlation "Your Request ID here" -path "path to dump log selection based on request guid"

If your SharePoint Site is running with SSL you need to do some more steps in fiddler to allow the traffic to be decrypted by fiddler. 

Open up Tools --> Fiddler Options -- https and make sure your flag the required settings.

 Figure B - Fiddler HTTPS Settings

Another cool tool to look at is ULSViewer. You can find this on codeplex and on MS downloads and other places if you Google or Bing around enough.  Fiddler and ULSviewer in my honest opinion are two tools at least every SharePoint pro should have in his toolbox.


Reacties

Een reactie posten

Populaire posts van deze blog

One ADFS to serve them all (Part I)!

Afbeelding
One ADFS to serve them all (part I)! The goal is to use a vanity URL host names that your site is using and to also use that same host name to resolve ADFS, without having you redirected back to the ADFS original service name (hostname + URL). Because for the end users this shouldn't look like anything else but the vanity domain they are already connected to. Thus how do we solve this? Follow this basic lab entry to get a feeling for the end solution. (I will post more about this subject in greater detail) The ADFS Limitation. The limitation I'm speaking of, in this case is the endpoint for SAML 2.0 / WS-Federation: "/adfs/ls"  (but as you can imagine it's pretty much every endpoint listed in ADFS) We connect with the 1 possible value set during installation for the federation service name: "your.host.name"  Which results in all endpoints only being accessibly under that federation service name.    Figure A: Federation service
Meer lezen

Microsoft Hub NVA configuration example.

Afbeelding
Microsoft Hub NVA configuration example. So in my previous post i gave a short description of implementing Microsoft Hub-Spoke model in IaaS. And i promised to publish some sample code you could use in CICD. Of course the main goal should be to get in to containers and such technologies but seeing as how slow large enterprises are willing to adopt and move to such technologies I'm guessing IaaS will be a standard for some time yet. So I'm going to give you a sketch of a private data center connection via express route (or a S2S VPN instead of the express route) to your azure subscription. And slowly start to explain a few basic configurations. The first overview:      So in this simple drawing you can see I've implemented a express route. I've not drawn a full blown resource drawing so you're bound to miss certain things like a circuit for instance but lets keep it simple. The green line is a express route configuration over whi
Meer lezen

RDS: Remote Desktop Gateway with NPS and Cross domain identities.

This post is about configuring a Remote Desktop Gateway in Resource Domain A while consuming the identities from Identity domain B. Setup: - NPS in Domain A  - RDG in domain A - MFA in Domain A Requirements a "TWO-WAY trust" with selective authentication (or wide if you have no security risks) It won't be possible to authenticate users from domain B in Domain A via the RDG until the computer account has gotten the permission "Allow to authenticate" on the domain controllers in Domain B. The simplest way to achieve this is by going to properties on the "Domain Controllers" OU in users and computers in domain B (RSAT tools) and going to the security Tab. (if you don't see the security tab in users and computers then make sure you've enabled "advanced features" under the view selection.) Then when you're in the security tab click the bottom advanced button. This will open the "Advanced Security Settings for Domain
Meer lezen