Admin site issues after migration to K13 from K12

Geo Neeliyara asked on November 14, 2024 12:41

after migrating from Kentico 12 to Kentico 13, I encountered a couple of errors when attempting to make changes to the Sites section, as well as when trying to save the page type objects. Please see the error details below. Any suggestions or insights would be greatly appreciated.

Server Error in '/' Application. Object type 'cms.cssstylesheet' not found. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Object type 'cms.cssstylesheet' not found.

An error occurred when saving data. Please see event log for more details. Message:

UPDATE CMS_Tree SET [NodeCacheMinutes] = @NodeCacheMinutes, [NodeDocType] = @NodeDocType, [NodeHeadTags] = @NodeHeadTags, [NodeBodyElementAttributes] = @NodeBodyElementAttributes, [NodeInheritPageLevels] = @NodeInheritPageLevels, [RequiresSSL] = @RequiresSSL, [NodeGroupID] = @NodeGroupID, [NodeTemplateID] = @NodeTemplateID, [NodeTemplateForAllCultures] = @NodeTemplateForAllCultures, [NodeInheritPageTemplate] = @NodeInheritPageTemplate, [NodeAllowCacheInFileSystem] = @NodeAllowCacheInFileSystem, [NodeIsContentOnly] = @NodeIsContentOnly, [NodeBodyScripts] = @NodeBodyScripts WHERE [NodeID] = @NodeID

Caused exception: Invalid column name 'NodeCacheMinutes'. Invalid column name 'NodeDocType'. Invalid column name 'NodeHeadTags'. Invalid column name 'NodeBodyElementAttributes'. Invalid column name 'NodeInheritPageLevels'. Invalid column name 'RequiresSSL'. Invalid column name 'NodeGroupID'. Invalid column name 'NodeTemplateID'. Invalid column name 'NodeTemplateForAllCultures'. Invalid column name 'NodeInheritPageTemplate'. Invalid column name 'NodeAllowCacheInFileSystem'. Invalid column name 'NodeIsContentOnly'.

Recent Answers


Juraj Ondrus answered on November 14, 2024 15:23

The cms.cssstylesheet object type was related to portal engine development model. Also, the invalid columns in the DB should have been removed. How was the upgrade done? Was the site originating in the MVC5 development model? This sounds like the upgrade was not done correctly and I would recommend repeating it again (or, you can try manually removing the object type and columns from the DB - with no guarantees)

0 votesVote for this answer Mark as a Correct answer

Geo Neeliyara answered on November 14, 2024 15:29 (last edited on November 14, 2024 15:32)

Hi Juraj,

Thank you for your prompt response and for assisting me with this matter.

To provide more context, I used the Upgrade Tool (Upgrade_12_0_13_0.exe) for the migration from Kentico 12 to Kentico 13. After the upgrade I also applied hotfix 13.0.163. Additionally, the site was originally built using the MVC5 model.

I appreciate any further insights or suggestions you may have regarding these issues.

Thank you again for your support.

Best regards, Geo

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on November 15, 2024 05:40

I would still recommend rolling back the backups and upgrade again. Isn't it possible you were using some third party integrations like dynamic routing or anything else? If yes, I would try removing them prior the upgrade.
Something prevented the SQL upgrade script from removing the old columns and class definitions. Maybe I would try running the SQL part of the upgrade manually in the SQL Server management studio.

0 votesVote for this answer Mark as a Correct answer

Geo Neeliyara answered on November 20, 2024 11:31

Hi Juraj,

I have rolled back to Kentico version 12 and executed the Kentico Upgrade Tool without the SQL scripts. I then manually ran the SQL scripts successfully through SQL Management Studio and applied the hotfix for version 13.0.163. However, I am still encountering the same issue as outlined in the original post

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on November 20, 2024 11:51

When did you applied the hotfix? Right after you upgraded? Was the admin app launched before the hotfix? If not, this is wrong. The upgrade instructions say to run the admin app before applying any hotfixes and making sure that the Upgrade START and FINISH events are logged in the Event log without any errors between. Please see this KB article to learn what happens during upgrade. Especially no.3

0 votesVote for this answer Mark as a Correct answer

Geo Neeliyara answered on November 20, 2024 12:01

Thank you, Juraj. I applied the hotfix immediately after the upgrade. Prior to applying the hotfix, I encountered a DLL reference issue when attempting to launch the admin app. However, after the hotfix was applied, the DLL reference error no longer occurs.

I will follow the instructions you provided and keep you updated on the progress.

0 votesVote for this answer Mark as a Correct answer

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