SharePoint 2013 upgrade shows as failed in Central Admin (But still shows as completed 100%) - Logs attached. RRS feed

  • Question

  • Hi there,

    Does this mean there is a cause to worry?

    - Test-Upgrade did NOT have any Upgrade Breaking errors. (Just some feature not available errors)

    - SQL Server: HAYSPSQL2013
    - SP Server: HAYSPSRV2013

    Logs are here

    Help will be appreciated.

    Thanks so much.

    Saturday, November 21, 2015 12:58 AM


All replies

  • taken a look at your log attached

    the cause of failure would be below some of several issues as captured in the log, did you reviewed below warnings and issues

    Health Rule Conflicting Content Types: The names of the following content types on your site conflict with new content types that may be added during upgrade

    Health Rule Conflicting Content Types: Please resolve any content type conflicts by renaming or removing these content types

    check this template also http://hayspsrv2013/operations/PM/Product Transfer/Forms/template.dotx 

    Also there are several features which could not get updated, you should take a look at them, what is causing them not to be upgraded


    Feature could not be upgraded. Exception: Feature definition id '4dae1df8-65fa-40f6-9b86-d77901a855a8' could not be found. 57eab31e-6e8e-4f55-b5f5-1b3edff45d33

    Mark ANSWER if this reply resolves your query, If helpful then VOTE HELPFUL
    INSQLSERVER.COM Mohammad Nizamuddin

    Saturday, November 21, 2015 6:00 AM
  • Hi Mohammad,

    1 - To resolve "Health Rule Conflicting Content Types" - Do I need to do anything on the SP 2010 to improve the upgrade?
    OR I just to resolve these on upgraded SP 2013 site?

    2 - On SP 2013 - should I do this before Visual Upgrade? 

    Thanks so much for your help.

    • Edited by ran009 Saturday, November 21, 2015 6:35 PM
    Saturday, November 21, 2015 5:06 PM
  • Hi,

    For the first issue, you need to rename the existing content types in SharePoint 2010 before upgrading.

    For the second issue, it is recommend to resolve the errors before doing visual upgrade.

    And it is better to use a trial upgrade to SharePoint 2013 to find potential issues before upgrading to SharePoint 2013.



    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact

    • Marked as answer by ran009 Thursday, November 26, 2015 12:05 AM
    Monday, November 23, 2015 6:22 AM