Powershell – “Powershell: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered” after installing SP (not configured)

powershellsharepointsharepoint-2013

I have 2 servers (Hyper-V clients) with Windows 2012R2 and SharePoint 2013 installed.

On the first server, I am installing SP and doing nothing with him. With second server, I am testing SP.

Many times configuring farm and doing "revert" on hyper-v host machine when in client machine something wrong in my work with farm, and I am starting work with previous snapshot. But once my SP console doesn't work and wrote me:

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

Remember, this SP is not configured, he hasn't any DB. This problem is on 2 servers! I am trying use revert, but always this error. What happened? How to resolve?

Best Answer

Usually this is because of a permission issue against the config database.

If you go in to your DB select the _config DB and check out the permissions for the user you are logged in as you will probably see you do not have shell access.

Check This out

You could always try Running powershell as another user much like one of the comments suggest but you will need to know who to run it as.

Cheers

Truez

Related Solutions

Powershell – Import-PSSession : Proxy creation has been skipped for ‘%’ command, because PowerShell couldn’t verify its name as safe

I resolved this by simply entering the remote session instead of importing it. I was then able to add the SharePoint snap-in installed on the remote machine and run my script.

$Session = New-PSSession -ConfigurationName "Microsoft.PowerShell" -ConnectionUri "http://app01-spl1:5985/wsman/" -Authentication "Kerberos" 
Enter-PSSession $Session
Add-PSSnapin Microsoft.SharePoint.PowerShell

<Cmdlets or script goes here>

Exit-PSSession
Remove-PSSession -ID $Session.ID
[GC]::Collect()

Another option is to use Invoke-Command cmdlet with the ScriptBlock parameter like so.

$Session = New-PSSession -ConfigurationName Microsoft.PowerShell -ConnectionUri "http://app01-spl1:5985/wsman/" -Authentication Kerberos
Invoke-Command -Session $Session -ScriptBlock { Add-PSSnapin Microsoft.SharePoint.PowerShell }

Invoke-Command -Session $Session -ScriptBlock { <Your cmdlet here.> }

Remove-PSSession -ID $Session.ID
[GC]::Collect()

C++ – How to access the sign bit of a number in C++

What about this?

int sign = number < 0;

Best Answer

Related Solutions

Powershell – Import-PSSession : Proxy creation has been skipped for ‘%’ command, because PowerShell couldn’t verify its name as safe

C++ – How to access the sign bit of a number in C++

Related Topic