Friday, August 19, 2016

Odd Error with SP 2013 Central Administration

Just thought I would add this for those that might come across this error. You have some system updates and/or have to reboot your farm (you should be doing this once a month AT LEAST anyway). You go to open up Central Administration and uh-oh – you see this:

SPError

In case you can’t read the image, the  error message is:

This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database. To connect the server to the server farm, use the SharePoint Products Configuration Wizard, located on the Start menu in Microsoft SharePoint 2010 Products.

(Note – it says 2010, that’s not a typo)

The problem is typically that SQL Server failed to start – this unfortunately is a common problem in 2012 R2 and I have seen it in 2014 as well. If you login to the SQL Server system, open the Services console through Administrative tools (or use Start > Run  and enter services.msc). You’ll likely find that the SQL Server engine and SQL Server Agent are stopped (even though they are set to start automatically!):

SPErrorReason

You do NOT have to reboot SQL Server; just start both services, wait a minute and refresh Central Administration.

——————–

David Sterling is the Principal Consultant for Sterling International Consulting Group, SharePoint experts with more than 100 implementations and over 13 years of experience.

We provide on site and remote consulting services for SharePoint (on premise, hybrid or purely cloud), SharePoint Online/Office 365, Azure and others. We provide multiple services including infrastructure development, information architecture, governance, business continuity and disaster recovery planning.

Contact us today at (888) 847-3679 or David direct at david_sterling@sterling-consulting.com

by Sterling International Consulting Group

The post Odd Error with SP 2013 Central Administration appeared first on SharePoint Blog.


by SICG via SharePoint Blog

No comments:

Post a Comment