We have taxonomy fields as part of a proven solution (SP 2010 -- fields demonstrated to work & are provisioned properly). We decided to experiment with Service Application architecture and created a second Managed Metadata Service to perform content type syndication.

Now seemingly at random, all of the taxonomy fields in our publishing site are grayed out. We will fix them but they will become grayed out shortly after this again.

Is anyone aware of any limitations of using two Managed Metadata Service Applications that could cause this?

The first MMS is default for keywords & column specific term sets. The second performs syndication. Only the second is configured as a ctx hub.

BTW, we're experimenting with two MMS because we've had difficulty deleting syndicated content types. Seems as though once a content type is syndicated, it gets stuck in the hub forever (at least as far as Feature scoped content types go). Other options?

  • Have you not been able to unpublish the syndicated types on the hub? We have an application that uses many custom content types, created/deployed through a feature and published through a hub, and we have had no problems unpublishing the content types and removing them from the hub by deactivating the feature. Commented Jun 6, 2013 at 14:38

1 Answer 1


The problem here was the SSP ID for MMS Fields was being garbled after Content Type Syndication. Seemed like a bug.

We recreated the syndication MMS, reset the SSP ID's on the Taxonomy Fields to the keyword MMS. Then re ran syndication and have experienced no problems since.

I believe the problem was in the default Service Connection for the Web Application however we have not experienced this again so tough to give a concrete answer.

This is a safer model for when SHTF.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.