Different ways to troubleshoot/review the sharepoint error

Submit Blog | Blogs Home |

Hi All,

Below are the different ways by which you can troubleshoot your sharepoint error.

1st way

Correlation ID is unique for every single error

For Example : you will get the Correlation ID (e19484f7-c1c5-4085-bf75-7a69be4fdf12) like this for most of the sharepoint error page.

just take the correlation ID + Time Stamp and open the logs pertaining to your timestamp and search for the correlation ID

NOTE: Only for server side error's it will give correlation ids

Normally Administrators will follow this way.

2nd Way

Using PowerShell (C# or VB.NET)

700 command lines for the PowerShell

Use the below command in the SharePoint 2010 Management Shell to get the error details in the formatted file.

Ø  Get-splogevent|?{$_.Correlation -eq "e19484f7-c1c5-4085-bf75-7a69be4fdf12"} | select Area,category,level,eventid,message | format-List > d:\myerrors.log

Note : replace the correlation id with your correlation id.

3rd Way

VIEW - ULS TraceLog

There is a DataBase name called WSS_Logging  and a  VIEW called ULSTraceLog

You need to query the view using CorrelationID as the where condition like below

Use wss_logging

Select * from ULSTracingLog where

CorrelationId='e19484f7-c1c5-4085-bf75-7a69be4fdf12'.

NOTE: Some times View may not be created because of timer job is not created.

We need to run the timer job as below

Central Administration: Monitoring > Review Job Definitions >

Enable the "Diagnostic Data Provider: Trace Log" and set every 5 minutes and click ok and then again come to the same place click "Run Now" then go and check the database the view will be created.

4th Way

Ulslogviewer

ULSViewer allows users to open a ULS log file and display its contents in a user friendly format. Users can then perform advanced functions such as filtering, sorting, highlighting, loading logs, appending logs, etc in order to single out the data that is important to the user. This information can be used to diagnose problems with machines running ULS services, or to monitor machines and the events they create in realtime.

URL : http://archive.msdn.microsoft.com/ULSViewer

Used by administrators.

5^th Way

It is notmally not used in the production servers and only for the staging and development server

Make CallStack =" True", CustomErros = "Off" and debug = "true" in the C:\inetpub\wwwroot\wss\VirtualDirectories\7070\web.config

and also in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\web.config

to troubleshoot the error.

Hope, you all like this blog.

Thanks,

Chakradhar.