Your SlideShare is downloading. ×
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Everybody lies: Troubleshooting SharePoint with House M.D. - SPSTC fall 2012

226

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
226
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SharePoint Saturday Twin Cities Fall November 3, 2012 Everybody LiesTroubleshooting SharePoint with House M.D. John L. Ferringer
  • 2. About me• Senior Manager, Sogeti• My blog: http://www.MyCentralAdmin.com• Twitter: @ferringer
  • 3. Who is Dr. Gregory House?• A diagnostician• An arrogant jerk• A cynic• An observer
  • 4. 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
  • 5. Does SharePoint make you feel like House?
  • 6. 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
  • 7. How does House cure his patients?• Understand the Issue• Determine the Root Cause• Finding a Cure• Move ForwardWhy not do the same with SharePoint?
  • 8. Before we start, let’s keep this in mind…
  • 9. UNDERSTAND THE ISSUE
  • 10. 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?
  • 11. SharePoint 2010’s Correlation ID• Your users may see it• You may see it• It’s a GUID• It is actually helpful
  • 12. 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
  • 13. 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?
  • 14. 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
  • 15. Why do we care about Change?• You have to know what you have!• How has it changed?• When were they made?
  • 16. Back to Reality
  • 17. DETERMINE THE ROOT CAUSE
  • 18. 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…
  • 19. 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
  • 20. Meanwhile, back at the Hall of Justice…
  • 21. Talk to the team
  • 22. What Doesn’t Fit?
  • 23. It’s all about me, right?• Remember the database errors?• Here, have some SA rights…• No thank you.
  • 24. Get a Different Perspective
  • 25. In the Real World, who do I turn to?
  • 26. FINDING A CURE
  • 27. Review Possible Treatments• Reproduce the issue• Test it!• Understand the treatment• Always read the label
  • 28. 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…
  • 29. Fully Understand the Cause
  • 30. Fully Understand the Remedy
  • 31. MOVING FORWARDHTTP://TINYURL.COM/SPTROUBLE
  • 32. Questions…

×