none
SP2010 to 2013 'upgrade completed with errors' - any suggestions? RRS feed

  • Question

  • I am attempting to upgrade to 2013 and after a few tests I was confident to proceed. On the production go live 2 subsites that never had this issue on testing starting doing exactly what this thread mentioned. Honestly I will copy/paste what they said because it's exactly what I've tried.

    technet.microsoft.com/Forums/en-US/8c5731cb-478e-4fb2-887b-514dd0cdecc3/sharepoint-2013-site-collection-upgrade-completed-with-errors-any-suggestion?forum=sharepointadmin

    "Site collection

    upgrade completes with errors and navigation breaks (see below how those funny images shows up on each page). Any suggestions what is going wrong? I'm upgrading from 2010 to 2013 through content attach approach. Apparently a number of other content database upgrades went fine except this one.

    Tried restoring DB twice and then upgrading with the same results. In 2010 mode the site shows up fine. Test-SPContentDatabase does show few missing setup file and webparts but none of them are upgrade blocking. "

    The parent site and 6 subsites are working just fine. I have two that are doing this in the logs. Only difference I see compared to the working ones are these errors. Please please help I really appreciate anyone's time.

    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/communications	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Upgrade [SPSite Url=###########.com/sites/communications] failed. Microsoft.Office.Server.Search.Upgrade.SiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence.	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/communications	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Inner Exception: The parent content type specified by content type identifier 0x0101 does not exist.	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/communications	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	   at Microsoft.SharePoint.SPFeature.HandleProvisioningException(Exception e, Boolean force)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionFieldsAndContentTypes(SPFeaturePropertyCollection props, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)     at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, Boolean fIgnoreMissing, SPFeatureDefinitionScope featdefScope)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)     at Microsoft.Office.Server.Search.Upgrade.SearchWebPartsFeatureActivation.Upgrade()     at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/communications	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Exception: Action 15.0.2.0 of Microsoft.Office.Server.Search.Upgrade.SiteSequence failed.	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/communications	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    10/16/2019 19:17:42.40	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)	e49a0e9f-6039-60fa-b4b2-660a2a56be4f
    
    
    
    
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/lifestyle	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Upgrade [SPSite Url=###########.com/sites/lifestyle] failed. Microsoft.Office.Server.Search.Upgrade.SiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence.	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/lifestyle	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Inner Exception: The parent content type specified by content type identifier 0x0101 does not exist.	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/lifestyle	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	   at Microsoft.SharePoint.SPFeature.HandleProvisioningException(Exception e, Boolean force)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionFieldsAndContentTypes(SPFeaturePropertyCollection props, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)     at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, Boolean fIgnoreMissing, SPFeatureDefinitionScope featdefScope)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)     at Microsoft.Office.Server.Search.Upgrade.SearchWebPartsFeatureActivation.Upgrade()     at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/lifestyle	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	Exception: Action 15.0.2.0 of Microsoft.Office.Server.Search.Upgrade.SiteSequence failed.	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	INFO	SPSite Url=###########.com/sites/lifestyle	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec
    10/16/2019 19:18:40.33	OWSTIMER (0x096C)	0x09A0	SharePoint Foundation Upgrade	SPUpgradeSiteSession	ajxnk	ERROR	   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)	f39a0e9f-1040-60fa-b4b2-6ce2632d68ec



    • Edited by nwallace Friday, October 18, 2019 2:51 PM
    Friday, October 18, 2019 2:51 PM

Answers

  • Everyone thanks for trying to help seriously. In desperation I spun up another Hyper-V of a SP2013 stand-alone instance. I did all that's needed to allow me to mount and migrate the 2 databases I had trouble with. They worked perfectly and for the first time I had 0 errors. 

    I exported the databases from SQL manager and imported them in to the production site and bam. Its looks perfect now. I can't provide any information as to why they wouldn't migrate on the prod but obviously I have something not set right in there. Time for the 2016 install. Thanks!
    • Marked as answer by nwallace Tuesday, October 22, 2019 2:47 PM
    Tuesday, October 22, 2019 2:47 PM

All replies

  • Hi nwallace,

    Even though you got some error during upgrade - can you verify is it impacting to your application why because I am suggesting is, this is generally common in migration project. 

    Even I had also faced the similar kind of issue and figured this out by doing the proper analysis in the source system. One of the key parameter for succeeding the migration project is proper planning and analyzing the source environment. Try to get an inventory from your source system about all custom solution and where (in which sites) these custom features are activated, I am sure from the inventory report you will find there are many features those are not really being used in the source system. So you can clean those unwanted feature from target - after running the Test-SPContentDatabase command. 

    For cleaning up the the features you may use the below PowerShell script(available in the below link):

    https://blogs.technet.microsoft.com/dawiese/2017/05/09/post-upgrade-cleanup-missing-server-side-dependencies/

    PowerShell sample for running Test-SPContentDatabase:

    $wa= Get-SPWebApplication "https://sharepoint.contoso.com"
    $outputPath = "\\tools\files\Output\Test_Wss_Content_MissingAssembly_{0}.txt" -f (Get-Date -Format hhmmss)
    $dbName= "WSS_Content_MissingAssembly"
    $slqServer = "SPSQL"

    Test-SPContentDatabase -Name $dbName -WebApplication $wa -ServerInstance $slqServer -ShowLocation:$true -ExtendedCheck:$false | Out-File $outputPath Write-Host "Test results written to $outputPath"

    Reference Url: https://blogs.technet.microsoft.com/dawiese/2017/05/09/post-upgrade-cleanup-missing-server-side-dependencies/

    For planing and preparing the check list for content DB migration - you may refer the below content:

    https://www.advaiya.com/blog/sharepoint-2016-migration-checklist/

    https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/checklist-for-database-attach-upgrade-sharepoint-2013

    Various types of issues and their descriptions with fixes during running the Test-SPContentDatabase :

    https://sharegate.com/blog/sharepoint-content-database-migration-monitoring

    Notes:

    1. You may ignore the error or exception from Test-SPContentDatabase command, still your Mount-SPContentDatabase will work.

    2. While running the Mount-SPContentDatabase for certain content database - if you get an exception or up to some extend some errors, you can ignore those and continue in further migration, still your migrated site will work fine and in these scenario if you see database upgrade status from central admin, we can see upgrade completed with errors status but we can live with this.  

    3. After content db migration thru database detach and attach approach - we may see some issues in the migrated master page, css and java script code as a result we may expect some differences in the migrated site look and feel and other css and scripting related issue - this is a general behavior which we need to fix manually even though it is time consuming.    


    Thanks&Regards,

    Habibur Rahaman

    MCSA,MCP,MCTS

    My Certificates

    Note: If you feel the proposed answer is helpful, please mark as so or if this answered your question,please mark as answer.


    • Edited by Habibur Rahaman Saturday, October 19, 2019 4:01 AM Added more info
    Friday, October 18, 2019 4:42 PM
  • Thank you Habibur I am going to look in to what you said. I gravitated towards that post because I have the same formatting issues and CSS icons showing the whole thing. If I took a screenshot of the subsite it looks just like that in his post.

    I did all the usual testing before mounting.

    #Test-SPContentDatabase -Name "ourdatabasename" -WebApplication "http://url.com/" | Sort -Property DisplayName > c:\temp\logs\name.txt

    I got everything cleared even and the mount even shows no errors. I don't have a problem until after the ContentDatabase Upgrade to 2013 mode. I will submit a screenshot. It is only happening to these two subsites and it never did it during my testing.

    (I can't submit a picture or link until my account is verified)

    • Edited by nwallace Friday, October 18, 2019 5:00 PM
    Friday, October 18, 2019 4:50 PM
  • nwallace, like Habibur indicated, do a Test-SPContentDatabase first.  Get the report, and then determine if any upgrade problems listed in the report are upgradeblocking.  List the results of the report as best you can.  Non-upgrade blocking issues are fairly easy to resolve, but time-intensive.  We can help you work through these problems.
    Friday, October 18, 2019 7:35 PM
  • Hi nwallace,

    Based on the error: The parent content type specified by content type identifier 0x0101 does not exist, try to enable the SharePoint Server Publishing Infrastructure feature under Site Settings > Site Collection Features, and enable the SharePoint Server Publishing feature in the Site Settings > Site Features.

    Then use the PowerShell command to enable “CTypes” feature and check if the issue exists:

    Enable-SPFeature -identity "CTypes" -URL https://somesite

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, October 21, 2019 9:41 AM
    Moderator
  • Hello Grace WR,

    Thank you very much. I was messing with that months prior. I had to force enable the Publishing features with PS. If I try to enable them through the admin gui it gives me those general errors. However I can't create publishing related sites such as wiki but everything else works. I will get to the point 0x0101 is eliminated but then 0x0120 comes up. I have tried so much including stuff below. Again non of this on production.

    #--update column on tables
    USE WSS_Content_DBNAME;
    UPDATE ContentTypes
    SET NextChildByte = '1'
    WHERE ContentTypeId like 0x0120


    I am including just some of my notes I've used. I've even gone as far as doing direct SQL database edits (I know MS would not like that but it was in my test environment, not production)


    Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue
    
    
    #== Check Databases for errors and write logs
    <#-- 
    
    
    Test-SPContentDatabase -Name "WSS_Content_URL" -WebApplication "http://URLtest.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_URL.txt
    Test-SPContentDatabase -Name "WSS_Content_C" -WebApplication "http://URLtest.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_Cor.txt
    Test-SPContentDatabase -Name "WSS_Content_Hu" -WebApplication "http://URLtest.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_Humrces.txt
    Test-SPContentDatabase -Name "WSS_Content_L" -WebApplication "http://URLtest.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_Litxt
    Test-SPContentDatabase -Name "WSS_Content_S" -WebApplication "http://URLtest.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_Shs.txt
    Test-SPContentDatabase -Name "WSS_Content_hel" -WebApplication "http://helpdesk.URL.com/" | Sort -Property DisplayName > c:\temp\logs\WSS_Content_helk.txt
    --#>
    
    
    
    
    
    <#== Fix workflows
    New-WFScope -ScopeUri http://URL/SitePages
    
    
    Get-WFScope -ScopeUri http://URL/SitePages
    Get-WFFarm | select httpport,httpsport
    Register-SPWorkflowService -SPSite “http://URL.URL.com/” -WorkflowHostUri “http://URL:12291/” -AllowOAuthHttp -Force -ScopeName “SharePoint”
    
    --#>
    
    
    
    #== convert web app to claims after upgrade
    <#-- 
    $wa = get-SPWebApplication "URLtest.URL.com80"
    Convert-SPWebApplication -Identity $wa -To Claims –RetainPermissions -Verbose
    $wa.MigrateUsers($true)
    $wa.MigrateUsersToClaims
    --#>
    
    
    
    
    
    
    
    #== install_solution_after deployment
    
    <#-- 
    dp.sharepoint.workflow.wsp  Error None 
    microsoft.teamfoundation.sharepoint.dashboards.wsp  Deployed Globally deployed. 
    microsoft.teamfoundation.sharepoint.wsp  Deployed Globally deployed. 
    onboardtest8.wsp  Deployed Globally deployed. 
    orgchartpart.wsp  Deployed http://
    sharepointorgchart.wsp  Deployed http://URLtest.URL.com/ 
    taxonomy_webpart.wsp  Not Deployed None 
    tswawebpartcollection.wsp  Not Deployed None 
    usersadbrowser.wsp  Deployed http://URL.URL.com/ 
    veaaccordionlist.wsp  Deployed http://URL.URL.com/ 
    
    
    $wsp="usersadbrowser.wsp"
    Add-SPSolution –LiteralPath "C:\temp\2010to2013\2010 Custom Solutions Export\$wsp"
    Install-SPSolution –Identity $wsp –WebApplication http://URLtest.URL.com –GACDeployment -Force
    #Install-SPSolution –Identity $wsp –GACDeployment -Force
    
    
    --#>
    
    
    
    #== Install Missing Features 
    <#--
    Install-SPFeature -path "AccSrvSolutionGallery"  -CompatibilityLevel 14
    Install-SPFeature -path "BizAppsCTypes"  -CompatibilityLevel 14
    Install-SPFeature -path "BizAppsFields"  -CompatibilityLevel 14
    Install-SPFeature -path "BizAppsSiteTemplates"  -CompatibilityLevel 14
    Install-SPFeature -path "DataConnectionLibrary"  -CompatibilityLevel 14
    Install-SPFeature -path "ExcelServerSite"  -CompatibilityLevel 14
    Install-SPFeature -path "ExcelServerWebPart"  -CompatibilityLevel 14
    Install-SPFeature -path "FastEndUserHelpCollection"  -CompatibilityLevel 14
    Install-SPFeature -path "IPFSSiteFeatures"  -CompatibilityLevel 14
    Install-SPFeature -path "MobileExcelWebAccess"  -CompatibilityLevel 14
    Install-SPFeature -path "MossChart"  -CompatibilityLevel 14
    Install-SPFeature -path "PremiumSite"  -CompatibilityLevel 14
    Install-SPFeature -path "PremiumWeb"  -CompatibilityLevel 14
    Install-SPFeature -path "ReportListTemplate"  -CompatibilityLevel 14
    Install-SPFeature -path "SearchExtensions"  -CompatibilityLevel 14
    Install-SPFeature -path "VisioWebAccess"  -CompatibilityLevel 14
    
    --#>
    
    
    
    #-- Get features installed
    
    #$web = Get-SPWeb http://URL.URL.com/
    #Get-SPFeature | Sort -Property DisplayName > c:\temp\Features.txt
    
    
    #$web = Get-SPWeb http://URLtest.URL.com/
    #enable-SPFeature "fa564e0f-0c70-4ab9-b863-0177e6ddd247" -Url $web.Url -force
    
    <#--
    $siteUrl = "http://URL.URL.com/sites/kb"
                $siteCollection = Get-SPSite $siteUrl
                Enable-SPFeature "PublishingSite" -Url $siteCollection.Url -force
                Enable-SPFeature "PublishingWeb" -Url $siteCollection.Url -force
    --#>
    
    
    #-- Enable Publishing Features
    #Enable-SPFeature -Identity publishingSite -url http://URL.URL.com/ -force 
    #Enable-SPFeature -Identity publishingresources -url http://URL.URL.com/ -force
    
    
    
    
    
    #--check correlation ID
    get-splogevent | ?{$_.Correlation -eq "f881039f-3078-60fa-b4b2-63c88beddd0d"} | select Area, Category, Level, EventID, Message | Format-List
    
    
    #-- check fields for errors
    <#--
    $web = Get-SPWeb http://URL.URL.com
    $fields = $web.Fields
    foreach ($field in $fields) {write-host $field.id}
    --#>
    
    
    
    Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue
    
    #New-WFScope -ScopeUri http://URL/SitePages
    
    
    #Get-WFScope -ScopeUri http://URL/SitePages
    #Get-WFFarm | select httpport,httpsport
    #Register-SPWorkflowService -SPSite “http://URL.URL.com/” -WorkflowHostUri “http://URL:12291/” -AllowOAuthHttp -Force -ScopeName “SharePoint”
    
    
    #Get-SPFeature -Site http://URL.URL.com
    
    
    
    ===================================
    
    uninstall-spfeature -identity "WACustomReports" -CompatibilityLevel 14 -force
    
    uninstall-spfeature -identity "WACustomReports" -CompatibilityLevel 15 -force
    
    
    Install-SPFeature -path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\WACustomReports\feature.xml" -CompatibilityLevel 15 -force
    
    Install-SPFeature -path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\WACustomReports\feature.xml" -CompatibilityLevel 14 -force
    
    
    
    
    
    
    ===================================
    Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue
    
    #New-WFScope -ScopeUri http://URL/SitePages
    
    
    #Get-WFScope -ScopeUri http://URL/SitePages
    #Get-WFFarm | select httpport,httpsport
    #Register-SPWorkflowService -SPSite “http://URL.URL.com/” -WorkflowHostUri “http://URL:12291/” -AllowOAuthHttp -Force -ScopeName “SharePoint”
    
    SPList list = web.Lists.TryGetList("Pages");
    
                            if (list != null)
                            {
                                String url = list.RootFolder.ServerRelativeUrl.ToString();
    
                                PublishingSite pubSite = new PublishingSite(web.Site);
                                PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(web);
                                publishingWeb.PagesListId = list.ID;
                                publishingWeb.Update();
    
    }
    
    // Do your code
    
    
    
    
    
    
    ===================================
    
    Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue
    
    
    
    $web = get-spweb http://URLtest.URL.com
    
    Write-Output $web.lists > c:\temp\URLtest.txt
    
    #$list = $web.lists["YourList"]
    #$list.fields["YourColumnname"].id
    $web.dispose()
    
    
    
    
    
    ===================================


    Monday, October 21, 2019 5:09 PM
  • Thanks Stephan,

    Here are the results. Again nothing I saw that should be breaking the upgrade.

    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [Features\\PublishingResources\\dwp\\Media.webpart] is referenced [1] times in the database [WSS_Content_DBNAME], but is not installed on the current farm. Please install any feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database [WSS_Content_DBNAME], but are not installed on the current farm. Please install any feature or solution which contains these files.
    Locations       : 
    
    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [Features\\ReportServer\\ReportViewer.dwp] is referenced [1] times in the database [WSS_Content_DBNAME], but is not installed on the current farm. Please install any feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database [WSS_Content_DBNAME], but are not installed on the current farm. Please install any feature or solution which contains these files.
    Locations       : 

    So there are 6 subsites each with their own database tied to the main web app. Two of them are now coming over misformatted. I really wish I could post a screenshot. Before with all the pre-preemptive testing I did this never happened. I see no major errors before I mount the database to the web app using Powershell. Every other site looks like you would think after a 2013 content database upgrade and the default theming. I even reset site definitions, checked master pages, etc before database backup and restore.

    Honestly this SP install is not that intense with customization. Very basic but they have been on 2010 for a long time.
    • Edited by nwallace Monday, October 21, 2019 5:35 PM
    • Marked as answer by nwallace Tuesday, October 22, 2019 2:45 PM
    • Unmarked as answer by nwallace Tuesday, October 22, 2019 2:47 PM
    Monday, October 21, 2019 5:31 PM
  • Everyone thanks for trying to help seriously. In desperation I spun up another Hyper-V of a SP2013 stand-alone instance. I did all that's needed to allow me to mount and migrate the 2 databases I had trouble with. They worked perfectly and for the first time I had 0 errors. 

    I exported the databases from SQL manager and imported them in to the production site and bam. Its looks perfect now. I can't provide any information as to why they wouldn't migrate on the prod but obviously I have something not set right in there. Time for the 2016 install. Thanks!
    • Marked as answer by nwallace Tuesday, October 22, 2019 2:47 PM
    Tuesday, October 22, 2019 2:47 PM
  • Hi nwallace,

    Thanks for sharing your solution with us. I’m pleased to know that you have resolved your issue.

    Here I will provide a brief summary of this post for your information.

    [ SP2010 to 2013 'upgrade completed with errors' - any suggestions? ]

    Environment

    ====================

    SharePoint 2013

    Question

    ====================

    When upgrading from SharePoint 2010 to 2013 through content attach approach, two the content database upgrades completed with errors and site navigation breaks.

     

    Solution

    ====================

    Based on the nwallace’s post, the issue is resolved by using another Hyper-V of a SP2013 stand-alone instance to migrate the two problematic content databases, and export the databases from SQL manager and import them in to the production site and bam.

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, October 23, 2019 2:17 AM
    Moderator