Problem
When you run SharePoint PowerShell on your SharePoint server you get the following error:
Error: "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered".
Solution
Make sure the logged in user who is trying to run SharePoint PowerShell commands is having the right "SharePoint_Shell_Access" to the SharePoint_Configuration database to do so:
So what happens when you don't have that little checkbox/option for "SharePoint Shell Access"? How do you get it there? It's not going to be there by default with a new installation of SQL Server.
what happens is that you wont be able to execute powershell commands ...
if you installed SharePoint with least permissions (i.e not assigning the farm admin as sysAdmin Db role) this permission might not be there
I am not able to do this operation. I am getting the below error message....
TITLE: Microsoft SQL Server Management Studio
------------------------------
Add member failed for DatabaseRole 'SharePoint_Shell_Access'. (Microsoft.SqlServer.Smo)
For help, click: go.microsoft.com/fwlink((SQL11_RTM).120210-1917+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Add+member+DatabaseRole&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot use the special principal 'dbo'. (Microsoft SQL Server, Error: 15405)
For help, click: go.microsoft.com/fwlink
BUTTONS:
OK
Can you please help me on this...
And when I check for this error "Cannot use the special principal 'dbo'. (Microsoft SQL Server, Error: 15405)"
I found the below solution
stackoverflow.com/.../cannot-use-special-principal-dbo-error-15405.
Excellent, it worked !!
Please check once "services.msc" if sqlserver (sharepoint) is running or not if service is not running. please run the service it may be one of cause for "SharePoint Powershell command problem - FeatureDependencyId are not registered".
I had the same issue and it was resolved by running right clicking and running as administrator as my security was correct.
Thanks :)