This stumped me for a while, kept seeing “No content types have been subscribed” message even having set up content type publishing and subscription.

Click on “Content type publishing error log” to see the cause of the problem: The content type cannot be published to this site because this site has Document Id Service feature enabled but the content type hub site does not. Please contact the administrator.
Enable the Document Id service on the content type hub site, click “Refresh all published content types on next update”, then “OK”. Run “Content Type Hub” and “Content Type Subscriber” timer jobs. Sorted.
Have you ever had the case where no errors were posted to the log (I made sure to check the checkbox that enables logging) and that it still says after manually running the jobs “No content types have been subscribed”
Is there any tiny step that maybe you assumed everyone would have done that you didn’t mention?
Can’t think why this would be, sorry Matthew.
Ian
I want to help everyone out there having the same problem I did.
The following things were wrong with my case:
1. I had created my Site Collections using the Blank site template. This is an issue and in order for the Content Type Hub stuff to work you must create your site collection using the Tema Site template (other templates might work, haven’t tested, the important thing is that the blank one doesn’t)
2. I did not realize that in order to set the content type up for subscription, you had to go into “Manage publishing for this content type” in the content type settings and actually click OK. It wasn’t obvious to me that going into the page and just clicking OK would actually kick off the publishing step.
Cheers!
Thanks Matthew, I didn’t know about clicking OK, must have done it though. You can actually get the blank site template to work with the content type publishing, but you have to activate a feature through the command line, see http://blog.pointbeyond.com/2010/04/24/can’t-find-“content-type-publishing”-link-or-use-managed-metadata-columns
Thanks
Ian
I’m still facing issues regarding the Content Type Hub.
-I’ve created a web application with a root site collection (publishing site).
-I’ve created an explicit managed path for the web application named ‘sitemanagement’.
-I’ve created a site collection for site management (publishing site).
-On both site collections I’ve activated the taxonomyfeaturestapler and document id features.
-On the sitemanagement site collection I’ve activated the Content Type Hub feature so I can publish my content types from here.
-I’ve created a Managed MetaData Service in central administration and entered the URL to the sitemanagement site collection
-When publishing a content type the error log is still complaining about the Document ID Service not enabled at the content type hub, but the feature is activated on all site collections, just double checked.
Does anyone have some tips for me?
Thank you. I also did not know that the content types were not published without submitting the “Ok” button. Saved me some headaches here guys!
You can also activate content type publishing using powershell. This particular script will activate content type publishing on all sites within a webapp so don’t run it in its written form if you do not want that.
###################################################
Example of how to run this script
C:\DirOfScript\.\powershellfile.ps1 -webapp “http://mywebapp”
###################################################
param([string]$WebApp)
$AllWebAppSites = Get-SPSite -Limit All | Where {$_.url -like “$WebApp*”}
#This is the content type publishing feature
$SolutionFeatureID = “73EF14B1-13A9-416b-A9B5-ECECA2B0604C”
Function ActivateSolutionFeature ($FeatureID, $AllSites){
foreach ($FilteredSite in $AllSites)
{
$SiteUrl = $FilteredSite.Url;
Write-Host -fore “yellow” “Enabling Feature on Site: $SiteUrl …..”
Enable-SPFeature -Identity $FeatureID -Url $SiteUrl -Force -confirm:$false;
}
Write-Host -fore “yellow” “Done” -nonewline
}
#Activates all of the specified solutions features on each site on the specified web app.
ActivateSolutionFeature -FeatureID $SolutionFeatureID -AllSites $AllWebAppSites
##############################################################
That’s great, many thanks Ian!