Forum Discussion
GetDefaultSiteCollectionTermStore returns null on several Tenants via JSOM/CSOM
Sorry Oliver for the delay around this, but thanks for sharing the resolution around this.
This issue is occuring on two of our tenants (since yesterday). Both are version vti_extenderversion:SR|16.0.0.6330. A third tenant still works fine, this is version
vti_extenderversion:SR|16.0.0.6323.
Is this a problem relating to upgrades of farms in SharePoint Online?
It is also likely to be what is stopping PnP templates being provisioned on the two tenants with an exception in https://github.com/SharePoint/PnP-Sites-Core/blob/master/Core/OfficeDevPnP.Core/Framework/Provisioning/ObjectHandlers/TokenParser.cs VesaJuvonen
We have issued a support ticket to get it fixed on the affected tenants, just posting this in case it is a recurring issue that ought to be resolved permanently.
- Sam LarsonApr 06, 2017
Microsoft
Hello,
We are currently investigating this issue and are hoping to have a resolution ASAP.
Regards,
Sam
- Sam LarsonApr 06, 2017
Microsoft
This should now be resolved.
Please refer to your service health dashboard for more details.
- DeletedApr 07, 2017
Hi Sam
My company have several customers experiencing the exact same issue.
Since this is a bug in tenant creation, I assume the fix is done on all tenants with this issue as we speak?
Or how to we make sure it is fixed on our customers?
Brgds
Jesper, Webtop A/S