This could be cause for some reason the wrong powershell version starts up.
Try running />powershell –version 2
If need be to add sharepoint modules, use following:
/> add-ps-snapin Microsoft.sharepoint.powershell
Wednesday, February 06, 2013
Powershell on Sharepoint server bonkers
If sharepoints powerhell starts with ”the local farm is not accessible. Cmdlets with featuredependencyid are not registered.”
This could be cause for some reason the wrong powershell version starts up.
Try running />powershell –version 2
If need be to add sharepoint modules, use following:
/> add-ps-snapin Microsoft.sharepoint.powershell
This could be cause for some reason the wrong powershell version starts up.
Try running />powershell –version 2
If need be to add sharepoint modules, use following:
/> add-ps-snapin Microsoft.sharepoint.powershell
Subscribe to:
Post Comments (Atom)
-
Problem: In a customer environment they wanted to install RDS and DC on the same server. A nice cheap solution, which have worked perfectly...
-
I had some problems with the old familiar "Working on it" for mysites in Sharepoint 2019. It was difficult to find information ab...
-
Error received for no apparent reason when creating workflow. Errors were found when compiling the workflow. The workflow files were save ...
No comments:
Post a Comment