The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

You may fire up the SharePoint 2010 Management Shell (which allows you to run PowerShell commands to do cool SharePoint stuff, very technical… I know) and get the following error:

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

I have found there are two places you may get this error:

The first is kind of a “duh” moment if you will: not running the Management Shell as an administrator will produce this error every time if UAC is turned on.  So simply right click and choose the option to Run As Administrator.

The other situation is probably why you are really here (unless you’re like me and did the first case a time or two).  The user that is logged in and running the management shell needs some access to the SharePoint config database. Inside SQL Server Management studio connect to the SQL Server instance where the farm config database is stored. In the Security section give the user the following rights on the config database: SharePoint_Shell_Access

Bradley Schacht

Bradley Schacht is a Cloud Solution Architect on the state and local government team with Microsoft based in Jacksonville, FL. He has co-authored 3 SQL Server books including "SQL Server 2014 Professional Administration". As a former consultant and trainer, he uses his experience on many parts of the Microsoft BI and data platform to help customers deliver the best possible solutions. Bradley frequently presents at community events around the country. He is a contributor to sites such as and an active member of the Jacksonville SQL Server User Group (JSSUG).

You may also like...

3 Responses

  1. Glenn says:

    Well there must beother reasons too because both of these issues have been checked and its still happening…

    Sad Face… 🙁

  1. December 18, 2012

    […] I’m sure we’ve all come across this error once in a while when launching SharePoint 2010 Management Shell – mostly because (as security-conscious devs and admins) we’ve got UAC on and have not chosen to run the shell as an administrator. Then there’s the other reason, which is the lack of SharePoint_Shell_Access role assignment in SQL Server for the logged in user. These are both extensively documented on the internet, in places such as Bradley Schacht’s blog. […]

Leave a Reply to Bradley Schacht Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.