Forum Discussion
GetDefaultSiteCollectionTermStore returns null on several Tenants via JSOM/CSOM
We are seeing an issue in SPO with GetDefaultSiteCollectionTermStore method returning null or property or method not found via CSOM and JSOM. Anyone else running into this?
Has something changed here? VesaJuvonen are you aware of a change or is this simply a bug again?
10 Replies
Using the super cool SharePoint Client Browser from Bram de Jager we found out that two Termstores had been associated with those tenants with none of them set as default. Microsoft kindly removed one of them and everything seems to be working again now. So it was a bug / configuration issue from Microsoft!
- VesaJuvonen
Microsoft
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.
