Welcome on my SharePoint 2010 blog


My name's Roy. I'm a dutch SharePoint & BI consultant/architect at Advantive B.V. At this moment I'm busy with some big SharePoint 2010 projects in The Netherlands. In all the projects I've got different roles, like: Business consultancy, Lead Consultant, Architect (logical and technical), Development and Teaching/courses.

Products where you can ask me about are: SharePoint, Visual Studio, SQL Server, PowerPivot, Analysis and Reporting Services, Visio Services, InfoPath, PerformancePoint Services, Team Foundation Server, Office line.

I love to work and to write about Microsoft SharePoint 2010 so, feel free and read/comment my Blogs!


Friday, May 14, 2010

Problem with unactived Managed Metadata features

If you want to use content type publishing on a consuming web application or you want to create metadata columns, the following things are important to keep in mind. Sometimes the UI gives some strange messages that can be solved by adding the features below and set permissions for the users (who need access) on metadata service applications level.

Error with Content type publishing:You can get an error, if you want to publish the content types: "Proxy (association between service app and webapp) cannot be reached". You don't have enough permissions to access the service application.

Error with creating managed metadata column:While creating a metadata column in a library or list you can get the following error: "You need to activate the feature to use the metadata service application". To solve this problem enable the features below.

Another error you can get is: "cannot get terms out of term store". This means you don't have enough permissions on the metadata service applications.

Solution:**First make sure that the users or groups have permissions (view or contribute or full control) to use the metadata service application.**

If you want to use this feature that's part of the metadata service application, you need to activate two features, these features can't be through the UI, so use the powershell script (or stsadm):

enable-spfeature -identity 7201d6a4-a5d3-49a1-8c19-19c4bac6e668 -URL http://<YourWebApp>

enable-spfeature -identity 73ef14b1-13a9-416b-a9b5-ececa2b0604c -URL http://<YourWebApp>

This enables the following features:

MetaDataNav                            7201d6a4-a5d3-49a1-8c19-19c4bac6e668    Web
TaxonomyFieldAdded              73ef14b1-13a9-416b-a9b5-ececa2b0604c      Site