Invoke-SPOSiteSwap Issues

%3CLINGO-SUB%20id%3D%22lingo-sub-1278015%22%20slang%3D%22en-US%22%3EInvoke-SPOSiteSwap%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1278015%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20to%20swap%20the%20root%20site%20of%20our%20O365%20tenant%20with%20a%20new%20communication%20site.%20The%20root%20site%20was%20never%20actively%20used%20so%20it%20ist%20a%20empty%20modernized%20classic%20team%20site.%20Publishing%20features%20are%20not%20enabled%2C%20so%20I%20have%20no%20configuration%20options%20for%20structural%20navigation%20or%20metadata%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20invoke%20Invoke-SPOSwapSite%2C%20I%20get%20an%20error%20that%20says%20I%20have%20to%20run%20the%20Sharepoint%20Page%20Diagnostic%20tool%20and%20resolve%20issues.%20When%20I%20run%20the%20tool%20against%20the%20source%20site%20(the%20communication%20site)%20the%20check%20displays%20no%20issues%20with%20that%20site%20(all%20checks%20green).%20When%20I%20run%20the%20tool%20against%20the%20root%20site%20(the%20classic%20team%20site)%2C%20I%20get%20the%20attached%20error%20stating%20I%20have%20to%20enable%20caching%20on%20structural%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20questions%20are%3A%3C%2FP%3E%3CUL%3E%3CLI%3EHas%20the%20page%20diagnostic%20tool%20really%20to%20be%20run%20on%20the%20source%20AND%20the%20target%20site%3F%3C%2FLI%3E%3CLI%3EHow%20can%20the%20error%20on%20the%20classic%20site%20be%20resolved%3F%20I%20already%20tried%20to%20turn%20on%20the%20publishing%20feature%20to%20get%20the%20site%20navigation%20options%2C%20but%20there%20is%20no%20checkbox%20to%20enable%20caching%20and%20switching%20to%20metadata%20navigation%20did%20not%20work%20either.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThanks%20for%20any%20hints%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMarkus%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22sppagediagnostic.PNG%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181851iFA10CF5A76CCA991%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22sppagediagnostic.PNG%22%20alt%3D%22sppagediagnostic.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%E2%80%83%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1278015%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1300889%22%20slang%3D%22en-US%22%3ERe%3A%20Invoke-SPOSiteSwap%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1300889%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F525463%22%20target%3D%22_blank%22%3E%40MarkusBundschuhDHBW%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20having%20the%20same%20issue.%20Did%20you%20ever%20get%20this%20resolved%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1359736%22%20slang%3D%22en-US%22%3ERe%3A%20Invoke-SPOSiteSwap%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1359736%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F618468%22%20target%3D%22_blank%22%3E%40RPuttnam%3C%2FA%3Eno%20unfortunately%20not.%20I%20guess%20I%20will%20open%20a%20support%20ticket%20in%20the%20next%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1388905%22%20slang%3D%22en-US%22%3ERe%3A%20Invoke-SPOSiteSwap%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1388905%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F525463%22%20target%3D%22_blank%22%3E%40MarkusBundschuhDHBW%3C%2FA%3E%26nbsp%3Bsame%20issue%20here...%20any%20updates%20on%20fixes%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1572473%22%20slang%3D%22en-US%22%3ERe%3A%20Invoke-SPOSiteSwap%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1572473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F525463%22%20target%3D%22_blank%22%3E%40MarkusBundschuhDHBW%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20the%20same%20issue%2C%20contacted%20MSFT%20Support%2C%20but%20they%20did%20not%20have%20any%20solution%20available.%20I%20went%20and%20solved%20it%20myself.%20Apparently%20for%20large%20organisations%20(10000%2B%20seats)%20you'll%20have%20to%20use%20the%20page%20diagnostic%20tool%20which%20works%20for%20Edge%20and%20Chrome.%20I%20don't%26nbsp%3B%20understand%20how%20this%20plugin%20communicates%20its%20findings%20back%20to%20Powershell%2C%20but%20apparently%20it%20does.%20Although%20I%20solved%20all%20the%20errors%20the%20diagnostic%20tool%20showed%20me%20the%20first%20few%20times%20I%20kept%20getting%20the%20same%20error%20in%20PS.%20What%20I%20did%20was%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Created%20a%20blank%20page%20on%20the%20classic%20teamsite%20(current%20root)%20and%20promoted%20that%20to%20Start%20Page%3C%2FP%3E%3CP%3E2)%20Created%20a%20blank%20page%20on%20the%20Communication%20Site%20(new%20to%20be%20root)%20and%20promoted%20that%20to%20Start%20Page%3C%2FP%3E%3CP%3E3)%20Reran%20the%20Page%20Diagnostic%20Tool%20on%20both%20site%20collection%20homepages%20(both%20old%20an%20new)%3C%2FP%3E%3CP%3E4)%20Relaunched%20my%20PowerShell%20session%20and%20executed%20the%20command%20(with%20-force%20and%20-nowait%20parameters)%3C%2FP%3E%3CP%3E5)%20Worked!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20some%20reason%20the%20new%20or%20old%20web%20parts%20on%20homepages%20block%20the%20siteswap%20from%20happening%2C%20but%20nobody%20knows%20what%20exactly%20goes%20wrong.%20Hope%20this%20helps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi all,

 

I want to swap the root site of our O365 tenant with a new communication site. The root site was never actively used so it ist a empty modernized classic team site. Publishing features are not enabled, so I have no configuration options for structural navigation or metadata navigation.

 

When I invoke Invoke-SPOSwapSite, I get an error that says I have to run the Sharepoint Page Diagnostic tool and resolve issues. When I run the tool against the source site (the communication site) the check displays no issues with that site (all checks green). When I run the tool against the root site (the classic team site), I get the attached error stating I have to enable caching on structural navigation.

 

My questions are:

  • Has the page diagnostic tool really to be run on the source AND the target site?
  • How can the error on the classic site be resolved? I already tried to turn on the publishing feature to get the site navigation options, but there is no checkbox to enable caching and switching to metadata navigation did not work either.

Thanks for any hints,

 

Markus

sppagediagnostic.PNG

4 Replies
Highlighted

@MarkusBundschuhDHBW 

I am having the same issue. Did you ever get this resolved? 

Highlighted

@RPuttnamno unfortunately not. I guess I will open a support ticket in the next days.

Highlighted

@MarkusBundschuhDHBW same issue here... any updates on fixes?

Highlighted

@MarkusBundschuhDHBW 

 

I had the same issue, contacted MSFT Support, but they did not have any solution available. I went and solved it myself. Apparently for large organisations (10000+ seats) you'll have to use the page diagnostic tool which works for Edge and Chrome. I don't  understand how this plugin communicates its findings back to Powershell, but apparently it does. Although I solved all the errors the diagnostic tool showed me the first few times I kept getting the same error in PS. What I did was the following:

 

1) Created a blank page on the classic teamsite (current root) and promoted that to Start Page

2) Created a blank page on the Communication Site (new to be root) and promoted that to Start Page

3) Reran the Page Diagnostic Tool on both site collection homepages (both old an new)

4) Relaunched my PowerShell session and executed the command (with -force and -nowait parameters)

5) Worked!

 

For some reason the new or old web parts on homepages block the siteswap from happening, but nobody knows what exactly goes wrong. Hope this helps.