Contents
Why is the local farm not accessible in PowerShell?
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. It worked once I set “Sharepoint_Shell_Access” to the Sharepoint_Config database.
How to launch a SharePoint shell access cmdlet?
Launch this cmdlet by using (for example) the account used to install your farm. To get the list of all the users having the ” SharePoint_Shell_Access ” role, use the Get-SPShellAdmin cmdlet.
When did the local farm is not accessible cmdlet appear?
2010 – Suddenly getting “The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.” – SharePoint Stack Exchange Suddenly getting “The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.”
How to fix ” cannot access local farm ” error?
PowerShell Error: Cannot access the local farm 1 Open the SharePoint PowerShell as Administrator 2 Run the below code in the Shell Get-SPDatabase | Add-SPShellAdmin SomeDomainSomeUserName 3 Log off and login again , This will resolve the issue. More
Cmdlets with FeatureDependencyId are not registered. PowerShell: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. Article History PowerShell: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. Table of Contents Question Environment
What to do when local farm is not accessible?
What got me here was searching for the first message: “the local farm is not accessible” Perform the following script in the SharePoint Management Shell, as a farm administrator and it will remove the error. This will grant the user both access to the configuration database as well as the content database.
Is the local farm with featuredependencyid not registered?
PowerShell: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. – TechNet Articles – United States (English) – TechNet Wiki
Perform the following script in the SharePoint Management Shell, as a farm administrator and it will remove the error. This will grant the user both access to the configuration database as well as the content database. Alternatively, you can revoke that granted access with the opposite command.