Error on page tab after upgrade

Danny Winbourne asked on November 26, 2021 16:09

I am getting the following error after updating from CMS 12 to 13 including applying the latest hotfix. (13.0.52)

Try reloading the administration interface. The user was not found in the JWT token, nor in the current virtual context URL.

The CMS and MVC site all build and load. But I get the above error when accessing the Page tab. If I load the iFrame URL in a new window, I get the same error. (iFrame URL is https://mysite.domain.comcmsctx/pv/administrator/culture/en-GB/......)

I am accessing the site with an SSL certificate (self-signed) for both CMS and MVC and I have resigned all Macros.

Is there anything else I can try..

Recent Answers


David te Kloese answered on November 26, 2021 16:25

Could be a dozen things, but last time I've had this error just after an upgrade... it was either Cache that only got reset after to a system restart.

OR check if the upgrade went correctly in the EventLog!

You should see a Upgrade to 13.0 START and END without any errors. Else you might need to redo it...

This should have been done before applying the hotfix...

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 26, 2021 16:35

I'm pretty sure it upgraded correctly, but unfortunately I don't see those entries in my backed up database. (although I can't say for certain if I cleared the logs or not).

I'd really rather not start this process again. Everything else is running so I am hoping there is something else I can do here?

I have cleared cache completely in Edge and I still get the error there. And I have also tried multiple IIS Resets.. I've not yet get restarted my laptop - Do you think that would help?

Cheers,

Danny

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 26, 2021 16:37

I could revert to the Upgrade only state as I did check-in and backup the database at each step during the upgrade process. But I'd like to try other things before I do this.

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on November 26, 2021 16:40

Yeah wouldn't be the first time a reboot did more then flushing every cache known to mankind...

You could restore you DB next to you current one and use the code you already as the process in the Eventlog is import to process DB changes after the upgrade.

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 26, 2021 17:01

So: Reboot did not work on the 13.0.52 version of my site. I still get the same error.

But, I actually copied my entire project directory before I applied the hotfix, and backed up the database, so I was able to spin up the 13.0.0 only version of the site. On this one, the Page tab loads without error.

SO - it was something after applying the hotfix that caused this to break.

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on November 26, 2021 20:49

did you make sure to update the nuget packages of the Site instance to the correct hotfix version too?

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 27, 2021 09:30

I was very careful to upgrade the packages in each project in both solutions so I’m pretty sure they are all correct.

My process was to remove the old package first before adding the new one.

I did have to manually edit each file as it had a reference at the very end of the .csproj file that referred to 13.0.0 packages (not related to the usual packages/assembly references - I’m not on laptop so can’t be more specific right now). I just removed this reference, as it didn’t look needed, and the project built fine without. I am going to put this reference back and update to the hot fix path to see if it helps, but I’m not holding out any hope..

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 27, 2021 10:31 (last edited on November 27, 2021 10:31)

So - Amazingly syncing those .csproj files actually worked (I did have to clear cookies for both admin and MVC sites first). But now the page tab loads without error.

Below is the part of the .csproj file that I had previously removed (when it referred to version 13.0.0) - I guess this is needed, even though all the .dlls are copied to a single folder during the build process.

As a FYI, the main MVC solution has 30 different projects, as it's based on the Helix architecture principles from Sitecore.

  <Import Project="..\..\packages\Kentico.Xperience.AspNet.Mvc5.13.0.52\build\Kentico.Xperience.AspNet.Mvc5.targets" Condition="Exists('..\..\packages\Kentico.Xperience.AspNet.Mvc5.13.0.52\build\Kentico.Xperience.AspNet.Mvc5.targets')" />
  <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild">
    <PropertyGroup>
      <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText>
    </PropertyGroup>
    <Error Condition="!Exists('..\..\packages\Kentico.Xperience.AspNet.Mvc5.13.0.52\build\Kentico.Xperience.AspNet.Mvc5.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\..\packages\Kentico.Xperience.AspNet.Mvc5.13.0.52\build\Kentico.Xperience.AspNet.Mvc5.targets'))" />
  </Target>

Thanks for your advice so far though David - It's appreciated.

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 29, 2021 17:28

Update: Thie error has come back, and all I did was close all Chrome windows and reload..

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.