Ulysses Ludwig’Blog


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

Date: 29 Jan 2010 | 13 Comments | Tags: ,,, | 2010,PowerShell,SharePoint | 
13

Problem

When you run powershell on your server you get the following error:

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

clip_image001

 

Solution

Make sure the logged in user has rights to the SharePoint_Configuration database

    • SharePoint_Shell_Access
    • DB_owner (try reducing the privileges after you get it working in order to support “least privileges”

clip_image002

VN:F [1.9.22_1171]
Rating: 7.4/10 (58 votes cast)
VN:F [1.9.22_1171]
Rating: +13 (from 23 votes)

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered, 7.4 out of 10 based on 58 ratings

Be Sociable, Share!



About the author


ujludwig
Ulysses Ludwig is a SharePoint architect with over 16 years in the IT and computer industry. Ulysses' primary focus is SharePoint but he dabbles in the latest web technologies and likes to develop software in his spare time.



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

Creating a State Service Database for SharePoint 2010 Using Windows PowerShell | Ulysses Ludwig's SharePoint blog

[…] NOTE: If you receive the “The Local Farm is Not Accessible” error see the following article: http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredepe…  […]

Reply

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered « SharePoint Fits and Starts

[…] found several articles with suggestions here and here. Having the appropriate SQL Server access is required but neither approached worked for […]

Reply

Ruchir

Hi,

I have recently cloned one of my Sharepoint 2010 VM. I tried to use Rename-SPServer options. However, when I try to run these commands in PowerShell, it gives me an error saying, “The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.” .Search on internet and your blog entry provided me with two possible solutions/remedies. (1) To ensure that the logged in user has Sharepoint_Shell_Access role membership in Sharepoint_Config database, and (2) To run the Management Shell as Administrator. Both the scenarios are true in my case. Can you suggest any other alternative solution?

Thanks in anticipation.

VA:F [1.9.22_1171]
Rating: 3.7/5 (3 votes cast)
VA:F [1.9.22_1171]
Rating: +2 (from 4 votes)

Reply

Raj

I had a samilar issue, but my problem was not running PowerShell utility as administartor.

Follow the steps below
1. Go to Start menu
2. Right click on PowerShell and select run as administrator option
3. This will open up PowerShell utility
4. Now type in add-PSSnapin Microsoft.SharePoint.PowerShell and hit Enter
5. Type in any other PowerShell command and Enter

VA:F [1.9.22_1171]
Rating: 4.3/5 (9 votes cast)
VA:F [1.9.22_1171]
Rating: +4 (from 14 votes)

Reply

Alexandre Bacchin

Direct database changes are not supported by Microsoft, please use

Add-SPShellAdmin
http://technet.microsoft.com/en-us/library/ff607596.aspx

VA:F [1.9.22_1171]
Rating: 4.3/5 (6 votes cast)
VA:F [1.9.22_1171]
Rating: -2 (from 10 votes)

Reply

Daniel Williams

Thank you thank you!

VA:F [1.9.22_1171]
Rating: 3.0/5 (2 votes cast)
VA:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Reply

Xopher

run sharepoint management shell with the service account
$db = Get-SPDatabase | Where {$_.Name -eq “SharePoint_ConfigDB”}
Add-SPShellAdmin “domain\user_to_add” -database $db

VA:F [1.9.22_1171]
Rating: 4.0/5 (4 votes cast)
VA:F [1.9.22_1171]
Rating: +3 (from 3 votes)

Reply

Xopher

If you want to give the user shell access to all dbs in the farm
run sharepoint management shell with the service account
$dbs = Get-SPDatabase
foreach($d in $dbs) {Add-SPShellAdmin “domain\user_to_add” -database $d}

VA:F [1.9.22_1171]
Rating: 3.8/5 (8 votes cast)
VA:F [1.9.22_1171]
Rating: +8 (from 8 votes)

Reply

    ujludwig

    Very nice

    VN:F [1.9.22_1171]
    Rating: 5.0/5 (1 vote cast)
    VN:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

    Reply

Stefan

As it turns out, I get this message when I create / use a file C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.config

VA:F [1.9.22_1171]
Rating: 3.0/5 (2 votes cast)
VA:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Reply

How to Backup/Restore Managed Metadata from one farm/environment to another | SharePoint interests

[…] Follow this article to fix the  error:  http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredepe… […]

Reply

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

[…] Article from: http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredepe… […]

Reply

List of SharePoint 2010 Management Shell Commands | Average Joe

[…] administrator. However, if do the networking side of SharePoint as well, I found that this link on SharePoint Assist and think it will help […]

Reply




Wanna say something?