We have a Sharepoint 2013 Farm up and running. This is a new farm with a site collectoins brought over from 2010 as well as the BCS and managed metadata service database following the Microsoft instructions.
To store the application pool for a particular service application as a variable, at the Windows PowerShell command prompt, type the following command:
$applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'
$mms = New-SPMetadataServiceApplication -Name 'Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'Managed MetaData'
New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service Application" -ServiceApplication $mms -DefaultProxyGroup
Close PowerShell and Reopen
$applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'
$mms = New-SPMetadataServiceApplication -Name 'Managed Metadata Service Application2' -ApplicationPool $applicationPool -DatabaseName 'Managed MetaData2'
New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service Application2" -ServiceApplication $mms -DefaultProxyGroup
Everything has been working fine the past few months however we have noticed when we publish new content types in the Content type HUB and replicate these content types to the site collections all site
collections are displaying the following error in there Content type publishign error log.
"The version of the package 14.0.0.0 is different from the current version this program supports, 15.0.0.0."
The strange thing is the content types have been replicating just fine and are available and usable on every site collection.
