Troubleshooting an issue

Russ Maxwell has written, another, totally, awesome script!  This one will help you when you’re troubleshooting an issue.  Here’s a link to the original post

It works with SharePoint 2010-2016

It allows you to reproduce the issue with logging dialed up to Verbose.


If you want VerboseEx then edit line 239 from

set-sploglevel -TraceSeverity Verbose


set-sploglevel -TraceSeverity VerboseEx

You could also do a find and replace for Verbose and replace with VerboseEx and that way you’ll see the script tell you that it is setting VerboseEx, versus Verbose.




Then to use this bad boy, just save it into a .ps1, call the ps1 from an administrative powershell session, and it will convert the powershell session to a SharePoint Management Shell before it executes.

e.g   c:\scripts  .\AwesomeLogCorrelatorScript.ps1

When prompted for a path to store the logs, give the script a local path on your server (e.g. d:\troubleshootingSharePoint)

Then reproduce the issue, while leaving the powershell window open.  If the issue is happening during powershell, go ahead and open a new powershell window.  Finally, after you have re-pro’d your issue, come back to the window where you first called Russ’s script and press 1, followed by the “Enter” key.

After you’re done, you can use ULS viewer to look at the logs that are now in your d:\troubleshootingSharePoint directory.


Only one warning: if you’re not sure if you are using the default logging levels, you should run get-sploglevel before using this script.  If you are using custom logging levels, they’ll be reset to the OOB levels, which are trace severity of medium for all logging area’s.