Monday, March 13, 2017

View error logs for content type publishing

View error logs for content type publishing

There are two different kinds of reports you can use to identify errors with content type publishing. The Content type service application error log, which is available on sites that are hubs for content type publishing, captures publishing error information for subscriber sites. The Content type publishing error log report captures publishing error information for a site.

What do you want to do?

View the content type service application error log for a hub site

View the content type publishing error log

View the content type service application error log for a hub site

If you are working on a hub site that publishes content types to other site collections, you can use the Content type service application error log reports to review publishing error information for subscriber sites.

You must be a Site Collection Administrator to view the Content type service application error log.

  1. Go to the top-level site in the site collection that is functioning as a hub for content type publishing.

  2. On the Site Actions menu Site Actions Menu , click Site Settings.

  3. On the Site Settings page, under Site Collection Administration, click Content type service application error log.

Top of Page

View the content type publishing error log

If you are working on a site that subscribes to content types that are published from a hub site, you can use the Content type publishing error log to view the content type publishing error information for your site.

You must be a Site Collection Administrator to view the Content type publishing error log.

  1. Go to the top-level site in the site collection for which you want to view content type publishing errors.

  2. On the Site Actions menu Site Actions Menu , click Site Settings.

  3. On the Site Settings page, under Site Collection Administration, click Content type publishing.

  4. Click the link titled Content type publishing error log.

Top of Page

No comments:

Post a Comment