SharePoint Troubleshooting and ToolsKen PriceDedicated Support EngineerMicrosoft Corporation

2

Disclaimer

The opinions and views expressed in this presentation are those of the authors. They do not necessarily state or reflect the official or unofficial opinion, view, statement or position of the Microsoft Corporation.

What We’ll Review• About Me• Components of a SharePoint Problem• Where Do I Look?• How Do I Approach the Problem?• Which Tools Can I Use?• How Do I Know What I’m Doing is

Supported?• Common Issues

4

About Me

Have been a Dedicated Support Engineer and Technical Advisor for Microsoft’s Public Sector customers for more than 3 years

Work in various parts of SharePoint and doing so since 2006 Primary focus is to ensure customers understand and deploy

based on field-tested and repeatable guidance Employed in multiple verticals (F500, Military, State

Government) Based in Charlotte, North Carolina Twitter: @kennethprice

5

Components of a SharePoint Problem Active Directory (Account changes) SQL Server (Data Access) Network (Data Transport) Client software (Office, Internet Explorer) Deployed features and solutions (Customizations)

Change management

6

Where Do I Look? Error Messages ULS Logs Event Viewer IIS Logs Network or Client Traces Use tools that are specialized for the problem you are trying to solve

7

How Do I Approach the Problem? “It depends” What is the error message you are seeing? What are you trying to accomplish? What are the processes and tools telling you?

8

If I See a Network Problem? Cannot reach a destination Port or URL references Timeouts Non 200 (Success) HTTP status codes in traces

9

If I See a Database Problem? Refers to a SharePoint table, proc or query Entire farm (or farms) could be impacted Round trip to pull back data could be high I could user SQL Profiler or PerfMon

10

If I See a Web Front End Problem? Look at the error and grab the Correlation ID

Go to ULS Enable the Developer’s Dashboard Fire up SQL Profiler

11

If I Make Changes to My Farm… I understand how it impacts the current state of the farm

I try to make the process repeatable and document each step

I verify that there are not problems that exist from my action

I pick a time that will not impact my users I have a plan to back out my changes

12

Which Tools Can I Use? Netmon or Wireshark PerfMon SQL Profiler ULS Viewer Developer’s Dashboard Farm Documenting Tools

SPSFarm SPSReports

Windows PowerShell Process Explorer Central Administration Many more partner tools and processes

13

How Do I Know What I’m Doing is Supported? Does it make sense? Can I reverse it? Check Microsoft’s Support Site My Example

14

What We’ve Reviewed…• Create SharePoint Document Libraries, Lists and

Views• Modify SharePoint Document Libraries, Lists and

Views• Add/Edit Pages• Permissions• Create Groups• Add Users to Groups• USPSOIG-specific content• Labs

15

Questions?

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.