This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, I'm helping with a SharePoint Upgrade from SharePoint Server 2013 to SharePoint Server 2019; most of its gone fine but one site is having issues with Javascript calls and it causes things like the Site Contents page not to load and some functions not to work, other sites we set up are working fine without this issue. It does use an URL that is set up in Alternate Access mappings with both a HTTP and HTTPS options that match the old servers, the other web app that is working has one as well; it does seem to work with the IP oddly enough when that URL is tried. I'm not finding any particular errors in the SharePoint logs or Event Viewer so any help would be appreciated. Thank you
Hi @William E. Fisher ,
Please follow the upgrade instructions. The upgrade scenario has not changed in SharePoint Server 2019. There is no direct upgrade path from 2013 to 2019. To upgrade to SharePoint Server 2019, you must upgrade SharePoint 2013 to SharePoint Server 2016, and then upgrade to SharePoint Server 2019. Your databases must be at a SharePoint Server 2016 RTM version or higher when you upgrade to SharePoint Server 2019. Any database with a lower version will be locked and upgrade will not start. The basic steps are:
On SharePoint Server 2013, use Convert-SPWebApplication to convert from Windows classic authentication to Windows claims (if using Windows authentication and if not previously done during a 2010 -> 2013 upgrade). This is a requirement prior to moving content databases to SharePoint Server 2016.
On SharePoint Server 2013, use Upgrade-SPSite to upgrade all site collections from V14.5 to V15 mode. This is a requirement prior to moving content databases to SharePoint Server 2016.
Migrate the CDBs to the new SQL Server supporting SharePoint Server 2016 and attach to an existing Web Application using Mount-SPContentDatabase to upgrade the content databases.
Once the databases are mounted, move them to the SQL Server supporting SharePoint Server 2019 and again on an existing Web Application, use Mount-SPContentDatabase to upgrade the content databases.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sorry maybe excluding some detailsmay have mislead this; the site has been upgraded via that method; the 2016 copy of the site appears to not have any issues and the rest of those steps had been done. The majority of the site is working other than the Javascript calls on the Modern features and as stated only seemingly for this specific Web Application as other sites that were upgraded on to the server are working fine.
Hi @William E. Fisher ,
Is there any site collections with TENANTADMIN template, using site subscriptions.
Sorry for the delay; we ran the check on the templates on that web application and got back the IDs of 1, 39, 7, 15 with the best guess being they are Team site (classic experience), Publishing Site,
Document Center, and Group Work Site so no there is not a TENANTADMIN Template in use