Download SharePoint ULS Viewer 2016

Download SharePoint ULS Viewer 2016

In this post, we’ll learn how to download and use SharePoint ULS Viewer to view SharePoint ULS logs in SharePoint 2013 and 2016 by exploring the following:


What’s SharePoint ULS Viewer?

SharePoint ULS Viewer is a Windows application that provides a simplified view of ULS log files in SharePoint 2010/2013/2016. It supports filtering, highlighting, sorting, append, and more features.

SharePoint ULS Viewer

Why do you need to use SharePoint ULS Viewer?

By default, the SharePoint ULS logs files are opened using Notepad, which is actually difficult to be read and traced!

SharePoint ULS Logs

The SharePoint ULS Viewer will help you to read and trace your SharePoint ULS Logs in an organize and easy way!

Read SharePoint Logs using SharePoint ULS Viewer

Note: the SharePoint ULS Viewer doesn’t read the Event Viewer Log.


How to use ULS Viewer SharePoint 2013 and 2016?

SharePoint ULS Viewer Features

In this section, we’ll show how to use SharePoint ULS Viewer by exploring its main features:

  1. Filtering.
  2. Append from SharePoint Log File.
  3. Formatting Rule.
  4. Manage Notifications.
  5. Explore Edit Menu.

Filtering In SharePoint ULS Viewer

You can easily filter your logs by the following fields:

  • Time: The time of the log occurred.
  • Process: The name of Windows Process like OWSTIMER.EXE, w3wp.exe ..etc.
  • Product: Like SharePoint Server, SharePoint Foundation, Search …etc.
  • Category: Like Topology, monitoring, Claims Authentication …etc.
  • Level: Like Hight, Medium, Unexpected ..etc.
  • Correlation: The Correlation ID of the log entry like “10046c9f-b485-6006-1cce-6f80b5ec34fe”.
  • Message: The detailed description of the entry log.
  • Server: The server name.
  • Name.
  • EventID.
  • Thread.
Filtering by Fields In SharePoint ULS Viewer

You can also filter by the log entry priority

  • High.
  • Medium.
  • Verbose.
  • VerboseEx.
Filtering In SharePoint ULS Viewer

Append from SharePoint Logs File in SharePoint ULS Viewer

The “Append From” feature helps you to append logs from another log Files/ ULS / Clipboard to the current retrieved SharePoint log file.

Append File In SharePoint ULS Viewer

Formatting Rule in ULS Viewer

SharePoint ULS logs is very huge and difficult, to read, so the “Formatting Rules” feature helps you to format the result based on your defined filter/rules to be easily readable.

Manage formatting rule in SharePoint ULS Viewer

Beside that, you can also specify which column you would like to apply the color format or to apply the format on the whole list.

Manage Formatting in SharePoint ULS Viewer

Notification Filter in ULS Viewer

You can easily manage notifications to get only the important notifications based on your filter.

To configure Notification Filter in SharePoint ULS Viewer, you should do the following:

  • At the “Tools” menu.
  • Click on “Notification Filter”.
  • At notification
Notification filter in SharePoint ULS viewer

You can also explore your notifications list by clicking on the “Notification List” button.

Notification List in ULS Viewer

Monitor SharePoint ULS Logs file in Real Time

SharePoint ULS Viewer also helps you to monitor a SharePoint Logs in real time by specifying the SharePoint ULS Logs Location.

Monitor SharePoint ULS Log File in real Time

Edit Menu in ULS Viewer

Plus the above features, you can find the common Edit functionalities in Edit menu as shown below:

bookmark In SharePoint ULS Viewer

How to read multiple SharePoint farm logs in SharePoint ULS Viewer?

Merge SharePoint Logs PowerShell

You can merge all SharePoint logs files from all SharePoint servers within the farm in one file using PowerShell as the following:

  • Open SharePoint PowerShell as Administrator.
Run SharePoint Management Shell as Administrator
  • Run the “Merge-SPLogFile” cmdlet.
Merge-SPLogFile -Path "C:\FarmMergedLog.log" -Overwrite
merge SharePoint logs files using PowerShell
  • Then open the merged file using SharePoint ULS Viewer.
Open merged SharePoint logs in SharePoint ULS viewer

Where’s the SharePoint Log Path?

Below, you can find the default SharePoint ULS logs location per SharePoint version:

SharePoint Log Path In SharePoint 2016

%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\15\Logs

SharePoint Log Path In SharePoint 2013

%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\15\Logs

SharePoint Log Path In SharePoint 2010

%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\Logs

SharePoint Log Path In SharePoint 2007

%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\Logs

How to change the SharePoint Log Path?

You can change the default Trace SharePoint ULS logs location from Central Administration by doing following:

Steps

  • Open Central Administration > Monitoring > Reporting > Configure Diagnostic Logs.
SharePoint Diagnostic logging
  • Beside Trace Log, you can
    • Change the SharePoint trace log path,
    • Change the number of days to store log files.
    • Restrict the maximum amount of storage in gigabytes to use for logging.
SharePoint Trace Log

Note: The SharePoint ULS Log Location must be a valid location exist on all SharePoint servers cross the farm.


Download SharePoint ULS Viewer for SharePoint 2016 and 2013

You can download the SharePoint ULS Viewer for SharePoint 2016 and SharePoint 2013 from Official Microsoft download center at ULS Viewer for SharePoint 2013/2016.


Conclusion

In conclusion, we have learned how to use ULS Viewer SharePoint 2013 and 2016. Also we have provided the official link for ULS Viewer 2016 download.

Additionally, we have leaned how to Merge SharePoint Logs using PowerShell as well as how to change SharePoint ULS logs location.

Applies To
  • SharePoint 2016.
  • SharePoint 2013.
  • SharePoint 2010.
You might also like to read
Have a Question?

If you have any related questions, please don’t hesitate to ask it at deBUG.to Community.

3 thoughts on “Download SharePoint ULS Viewer 2016”

  1. Pingback: SharePoint: 500 Internal Server Error | SPGeeks

Leave a Reply