Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Everybody Lies: Troubleshooting SharePoint with House MD - SharePoint Saturday Dayton 2012


Published on

For the cautious administrator, it’s not a question of if something’s going to go wrong with a SharePoint environment it’s a matter of when. When it does, how will you react? What will you do? Do you know how to figure out what’s going on and how to fix it?

When misfortune strikes your SharePoint farm, you need to have a plan for handling it. Why not take some cues from the most brilliant doctor on TV, Dr. Gregory House? Sure, he’s a little rough around the edges, but so are most IT Pros. This session will introduce attendees to a repeatable process they can use to figure out exactly what’s wrong with their SharePoint environment, who and where they can turn to for help, and how to effectively work to resolve their problems.

Published in: Technology
  • Be the first to comment

Everybody Lies: Troubleshooting SharePoint with House MD - SharePoint Saturday Dayton 2012

  1. 1. SharePoint Saturday Dayton, Ohio June 30, 2012 Everybody LiesTroubleshooting SharePoint with House M.D. John L. Ferringer
  2. 2. General Information• Tweet it Out!! – Hashtag for this event: #SPSDayton – Follow us: @SPSDayton – Include your presenters• Check out SPTV – Tweets will display throughout the day on the screens. – Footage will be shown at
  3. 3. About me• Senior Manager, Sogeti• My blog:• Twitter: @ferringer
  4. 4. Who is Dr. Gregory House?• A diagnostician• An arrogant jerk• A cynic• An observer
  5. 5. What’s House got to do with SharePoint?• We often have to diagnose (troubleshoot)• Dealing with SharePoint can make you a jerk (just kidding)• Dealing with SharePoint will definitely make you a cynic• The more you observe, the better you diagnose
  6. 6. Does SharePoint make you feel like House?
  7. 7. SharePoint is….• Complex• Vast in depth and breadth• Made up of many subsystems• Influenced by many outside factors• Every farm and use case is unique• …• Just like the human body
  8. 8. How does House cure his patients?• Understand the Issue• Determine the Root Cause• Finding a Cure• Move ForwardWhy not do the same with SharePoint?
  9. 9. Before we start, let’s keep this in mind…
  11. 11. Identify the Problem• You can’t cure anything if you don’t know what’s wrong• Interview the patient• You also have to ask the right questions – What is the error? – How is it happening? – Who is seeing the error? – When does it occur? – What else do we know about the error?
  12. 12. SharePoint 2010’s Correlation ID• Your users may see it• You may see it• It’s a GUID• It is actually helpful
  13. 13. Let’s get REAL for a minute• SharePoint 2010 farm• 1 Web Server, 1 App Server, 1 SQL Server• Visual Studio on the Web Server
  14. 14. Review the Patient History• What has the patient done to get here?• What is their environment?• What happened before the error?• What was happening during the error?• How was SharePoint performing?• Do you have Change Management?
  15. 15. Know Your Logs!• They record what’s going on• Which logs? – Windows Event, ULS, IIS – Keep in mind other sources: SQL, DCs, etc• Know your tools! – ULS Viewer – Log Parser – PAL – Just to name a few
  16. 16. Why do we care about Change?• You have to know what you have!• How has it changed?• When were they made?
  17. 17. Back to Reality
  19. 19. Rule Out the Obvious• Understand what you know• Every problem is unique• But, someone’s probably seen it before…• So check your sources: – Internal – External: Google it! (with Bing!)• But be careful…
  20. 20. Remember…• Know your sources – Who wrote it? – Are they credible?• Read the entire post! – Everything! – All the comments too• Was there a follow up post?• Validate the information
  21. 21. Meanwhile, back at the Hall of Justice…
  22. 22. Talk to the team
  23. 23. What Doesn’t Fit?
  24. 24. It’s all about me, right?• Remember the database errors?• Here, have some SA rights…• No thank you.
  25. 25. Get a Different Perspective
  26. 26. In the Real World, who do I turn to?
  27. 27. FINDING A CURE
  28. 28. Review Possible Treatments• Reproduce the issue• Test it!• Understand the treatment• Always read the label
  29. 29. Back to John’s problem…Treatments:• Sysadmin rights in the database –Oh heck no!• Local development environment – Not possible• Proper rights in the database – Now we’re talking…
  30. 30. Fully Understand the Cause
  31. 31. Fully Understand the Remedy
  33. 33. Brixx Ice Co.500 East First St., Dayton
  34. 34. SharePoint Saturday Dayton has been made possible becauseof generous sponsorship from the following friends…
  35. 35. Questions and Evals…• Fill out your evaluations to receive – SPS Dayton T-Shirt