Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SPManagedMetadataServiceApp sets incorrect defaults
See original GitHub issueThe SPManagedMetadataServiceApp does not properly support the configuration of multiple MMS service apps. When multiple service apps are configured, each will be set as the default for keywords and column specific term sets. This leads to an error in CA when editing the MMS Connection (select service app proxy in CA and click “Properties”). To fix this issue, the New-SPMetadataServiceAppProxy logic in the resource (see below) should be parameterized to allow the configuration to control which MMS service app will be the default.
265 $app = New-SPMetadataServiceApplication @params
266 if ($null -ne $app)
267 {
268 New-SPMetadataServiceApplicationProxy -Name $pName 269 -ServiceApplication $app
270 -DefaultProxyGroup 271 -ContentTypePushdownEnabled
272 -DefaultKeywordTaxonomy `
273 -DefaultSiteCollectionTaxonomy
274 }
275 }
This issue is confirmed in multiple versions of SharePointDSC, including the “release-1.9” and “preview-2.0” branches.
Environment in which the issue was discovered: SP2013, Windows 2012R2.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@andikrueger I thought you were already working on this 😃 If you have the opportunity to finish this by the end of this week, we can include it in v2.0…no pressure :-p
Closed via PR 699