Unable to access term store on site that is using a remote managed metadata service application

Issue:

After I configured The managed meta data service app on the host farm and then connected to the remote service from farm 2 I received the error below when trying to access the term store from a site hosted on the remote farm

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.

Resolution:

The problem ended up being that the remote farm did not have any permissions defined on the host farms Managed Meta Data Service Application. To fix you go to the host farm Managed Meta Data Service Application, and then properties, you then add the remote farms application pool account for the web app the site you are using is on into the permissions on the managed meta data sa and select the term store permissions needed. After this you can refresh the page on the remote farm and the term store will be accessible.

Ref articles

http://technet.microsoft.com/en-us/library/ff625176.aspx

http://technet.microsoft.com/en-us/library/ee530391.aspx

Configure AdobeIFilter on SharePoint 2010

Configure Adobe Ifilter on SharePoint 2010 

Install Ifilter on search server, make docicon.xml changes and copy icon file to all WFE servers in the farm

 

http://support.microsoft.com/kb/2293357

Unable to convert from standard to enterprise license

We ran into an issue in our environment as the farms were all built with standard license and we needed to convert them to enterprise. This should be easy you would think, but ended up requiring multiple MS cases resulting in a discovered bug. I was told the fix is slated to be released in SP2.

There is an msdn article out there that when implemented doesnt completly convert the license in the farm and leave you in a mixed state.

This msdn article was the first solution MS offered on this. After implementing this it did force the enterprise service apps to be available to build, but in Central Admin it still showed standard license.

All the Infopath links in CA also threw errors when you tried to open them.

If you have used this method to convert your farm then you will want to check the state of the farm. The following technet article provides the commands to run and registry key to check.

In our case we found that the guids returned are not both enterprise, but the registry keys are correct.

Solution:
In the end MS sent us a custom psconfig.exe that had the bad piece of code fixed or removed. We had to run psconfig with the dummy file on all servers, convert license to enterprise, run psconfig with original psconfig file.

If you are having this issue and need to correct prior to SP2, contact MS support. Since its a bug it will be a non dec case.