Upgrade from v8.2 to v9.0 - Blank dashboard

Matt Fothergill asked on June 22, 2018 16:00

After upgrading from v8.2 to v9.0, I have launched the site (from Visual Studio) for the first request in order to complete the upgrade and the page loaded just says:

"The web site doesn't contain any content. Sign in to administration and edit the content."

Once logged in as administrator I get a blank dashboard and the browser console errors such as:

GetResource.ashx:1 Failed to load resource: the server responded with a status of 404 ()
CMS/BreadcrumbsPin.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/Mole.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/Header.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/ContextHelp.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/Breadcrumbs.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/UserMenu.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/GlobalEventsHandler.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/BootstrapTooltip.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/AdvancedPopupHandler.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/EventHub.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/Loader.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/Application.js:1 Failed to load resource: the server responded with a status of 404 ()
CMS/AppList.js:1 Failed to load resource: the server responded with a status of 404 ()

I have tried removing {%AppPath%} from file ~\CMS\CMSScripts\RequireJS\config.js as mentioned here but get similar errors e.g.

"GET https://localhost:44399/Admin/CMS/Header.js 404 ()"

upgrade form 8.2 to 9

Recent Answers

Brenden Kehren answered on June 22, 2018 16:29

Check out this article on the DevNet, should help resolve your issue. Most likely caching.

0 votesVote for this answer Mark as a Correct answer

Matt Fothergill answered on June 22, 2018 16:59 (last edited on June 22, 2018 17:05)

I have tried deleting the temporary files from path below which is where VS/IIS Express is storing them, but no luck, same errors.

C:\Users\<user>\AppData\Local\Temp\Temporary ASP.NET Files

In terms of .dll's, Newtonsoft.Json had been updated (to v 7.0.1) previously while on Kentico v8.2 and System.Net.Http.Formatting is v5.2.6.0. The web.config has these entries:

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-5.2.6.0" newVersion="5.2.6.0" />
</dependentAssembly>

At what point is the 'upgrade_82_90.zip' package imported? I have checked the Event Logs via the database and can only see a few events for the site starting but nothing relating to the final steps of the upgrade and I can't get to the 'Sites' application yet in order to manually import the package.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on June 25, 2018 10:28

Hi,
you can find out more on the upgrade procedure and how it works in this article. The package is being imported on the first launch of the site after the upgrade.
I assume you checked the files - and they are present on file system. I meant the files returning 404. Just to be sure - does this happen in all browsers? Have you cleared the browser cache too?

0 votesVote for this answer Mark as a Correct answer

Matt Fothergill answered on June 25, 2018 11:56 (last edited on June 25, 2018 11:59)

Hi Juraj, None of the javascript files exist in the locations shown in the errors e.g. "CMS/BreadcrumbsPin.js" is actually in path "CMS\CMSScripts\CMSModules\CMS\BreadcrumbsPin.js".

After removing {%AppPath%} from file ~\CMS\CMSScripts\RequireJS\config.js, the 404 path then changes to "Admin/CMS/BreadcrumbsPin.js". The first error in the console is:

Loading failed for the <script> with source “https://localhost:44399/CMSPages/GetResource.ashx?scriptfile=%7e%2fCMSScripts%2fRequireJS%2fconfig.js&resolvemacros=1”.

I've tried different browsers and clearing cache, all give same 404 errors.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on June 25, 2018 12:00

Yes, those files should be in CMSScripts folder. It looks like something went wrong during the upgrade - so I would try upgrading again from the backups and if possible, start the site using normal IIS and not Visual studio - the debugger starts the application in a different mode. So, maybe some procedures were skipped.

0 votesVote for this answer Mark as a Correct answer

Matt Fothergill answered on June 25, 2018 12:17

Just to give a bit of background, I'm aiming to upgrade from v8.2 to v9, then v.9 to v10 and finally v10 to v11.

It's a web application solution under source control with a few extra custom projects that are referenced from CMSApp and CMSApp_AppCode projects (CMSApp_MVC project is not used).

Will it be possible to run the upgrade against the IIS deployed site (a backup, not production) and merge the changed files back in to the original code base that is under source control?

I'm starting to wonder if it would be simpler to create a fresh web application based on Kentico 11, run each database upgrade (v9, v10, v11) against the existing database and then try and merge custom code in to the fresh v11 project. I don't have any experience in upgrading Kentico solutions so not sure if this would/could work?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on June 25, 2018 12:22

Ho to upgrade projects under source control is described in the documentation. I would recommend to follow these instructions.
Your idea to upgrade just the DBs sounds logical but it is not possible in the way you wrote. I will correct it a little bit. You can start with a fresh Kentico 11 project files - this part is OK. But for the upgrade of the DB, you will need to install e.g. a fresh instance of Kentico 8.2 - connect it to the v8.2 database and upgrade and launch the site to finish the upgrade. This way you do not need to take care of the code files upgrade. Then repeat this when upgrading to Kentico 10 and 11. Once the DB is upgraded and you got the Upgrade - Finish logs after each upgrade, you can connect the DB to the fresh Kentico 11 instance. Assuming that you have ensured all your custom code.

0 votesVote for this answer Mark as a Correct answer