Pop Quiz: Troubleshooting SharePoint 2013
Applies to the "Maintain a Core SharePoint Environment" objective of Exam 70-331.
Q: A company's administrator needs to troubleshoot an error message reported; "Databases require upgrade or not supported" with SharePoint 2013.
Which of the following tools should the administrator use to troubleshoot the problem?
- SharePoint Health Analyzer
- Services console
- Application log
- System log
Answer and explanation are below.
Answer is A. SharePoint 2013 includes SharePoint Health Analyzer, which gives administrators the ability to diagnose and resolve configuration, performance, and usage problems. The SharePoint Health Analyzer runs predefined health rules against servers in the farm. A health rule runs a test and returns a message that tells provides the outcome of the test. The SharePoint Central Administration website is used to view alerts and resolve problems.
Quick Tip: SharePoint 2013 requires the 64-bit edition of SQL Server 2008 R2 Service Pack 1 or the 64-bit edition of Microsoft SQL Server 2012, and the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter.
Bonus Question: Which tool is the primary tool available from Microsoft that can help identify which applications, desktops, and servers, would make ideal candidates for virtualization? (The answer, of course, will be revealed next time!)
Answer to bonus question from last time: Branch Cache is the name of the Windows 7/Windows Server 2008 R2 technology that can help optimize access to SharePoint 2013 by caching content.
Andy Barkl, MCT/MCITP/MCSA, A+, Network+, Security+, CCNA has been studying technology for 30 years. Of the last 15 years, he has spent much of his time parting the knowledge and experience he has gained through IT exams, over 300, to help others be prepared and successful. He teaches classes in Phoenix, Ariz. where he has lived most of his life. He can be reached by e-mail at email@example.com.