Copy-SPTaxonomyGroups - The local farm is not accessible.

%3CLINGO-SUB%20id%3D%22lingo-sub-969473%22%20slang%3D%22en-US%22%3ECopy-SPTaxonomyGroups%20-%20The%20local%20farm%20is%20not%20accessible.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969473%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22thread-message-content-body-text%20thread-full-message%22%3E%3CP%20class%3D%22%22%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20configuring%20Hybrid%20Taxonomy%20and%20am%20running%20into%20the%20following%20error%20when%20I%20run%20the%20Copy-SPTaxonomyGroups%20cmdlet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3EThe%20local%20farm%20is%20not%20accessible.%20Cmdlets%20with%20FeatureDependencyId%20are%20not%20registered.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3E%3CSPAN%20class%3D%22%22%3Ecmdlet%20Get-Credential%20at%20command%20pipeline%20position%201%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3ESupply%20values%20for%20the%20following%20parameters%3A%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CEM%3E%3CSTRONG%3ECopy-SPTaxonomyGroups%20%3A%20The%20'username'%20argument%20is%20invalid.%3C%2FSTRONG%3E%3C%2FEM%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20account%20I%20am%20using%20is%20a%20global%20admin%20in%20Office%20365%20and%20a%20farm%20admin%20in%20SharePoint%202016%20on-premise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%20what's%20causing%20this%20error%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3CP%3EBob%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-969473%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-969636%22%20slang%3D%22en-US%22%3ERe%3A%20Copy-SPTaxonomyGroups%20-%20The%20local%20farm%20is%20not%20accessible.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969636%22%20slang%3D%22en-US%22%3EUsually%20this%20error%20arises%20when%20you%20don't%20run%20the%20SharePoint%20Management%20Shell%20'as%20Administrator'.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-969669%22%20slang%3D%22en-US%22%3ERe%3A%20Copy-SPTaxonomyGroups%20-%20The%20local%20farm%20is%20not%20accessible.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969669%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F130%22%20target%3D%22_blank%22%3E%40Trevor%20Seward%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20quick%20response.%20I'm%20running%20PS%20as%20my%20admin%20account%3B%20which%20is%20a%20global%20admin%20in%20O365%20and%20a%20farm%20admin.%20Let%20me%20try%20some%20other%20combinations%20and%20just%20run%20as%20admin.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3CP%3EBob%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-969728%22%20slang%3D%22en-US%22%3ERe%3A%20Copy-SPTaxonomyGroups%20-%20The%20local%20farm%20is%20not%20accessible.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969728%22%20slang%3D%22en-US%22%3EWell%2C%20again%20you%20have%20to%20run%20PoSh%20%22as%20administrator%22%20otherwise%20you%20will%20not%20be%20running%20with%20an%20admin%20token.%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20the%20cmdlet%2C%20make%20sure%20to%20specify%20a%20cloud-only%2C%20non-MFA%20enabled%20account%20for%20connecting%20to%20Office%20365.%20But%20you're%20not%20getting%20quite%20that%20far.%3CBR%20%2F%3E%3CBR%20%2F%3EOnly%20other%20thing%20I%20can%20think%20of%20is%20make%20sure%20that%20you're%20patching%20with%20both%20the%20sts-x-none%20and%20wssmui%20patches%20for%20a%20given%20month.%20I%20find%20people%20often%20only%20patch%20the%20sts-x-none%20patch%20(typically%20a%20security%20patch)%20and%20miss%20that%20they%20also%20need%20to%20install%20the%20wssmui%20patch%2C%20if%20one%20is%20available%20for%20that%20month%2C%20or%20the%20most%20recent%20month%20one%20is%20available.%3C%2FLINGO-BODY%3E
Occasional Contributor

Greetings,

 

I am configuring Hybrid Taxonomy and am running into the following error when I run the Copy-SPTaxonomyGroups cmdlet.

 

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

cmdlet Get-Credential at command pipeline position 1

Supply values for the following parameters:

Copy-SPTaxonomyGroups : The 'username' argument is invalid.

 

The account I am using is a global admin in Office 365 and a farm admin in SharePoint 2016 on-premise.

 

Any idea what's causing this error?

 

Thank you!

Bob

3 Replies
Usually this error arises when you don't run the SharePoint Management Shell 'as Administrator'.

Hi @Trevor Seward,

 

Thank you for the quick response. I'm running PS as my admin account; which is a global admin in O365 and a farm admin. Let me try some other combinations and just run as admin.

 

Thank you!

Bob

Well, again you have to run PoSh "as administrator" otherwise you will not be running with an admin token.

For the cmdlet, make sure to specify a cloud-only, non-MFA enabled account for connecting to Office 365. But you're not getting quite that far.

Only other thing I can think of is make sure that you're patching with both the sts-x-none and wssmui patches for a given month. I find people often only patch the sts-x-none patch (typically a security patch) and miss that they also need to install the wssmui patch, if one is available for that month, or the most recent month one is available.