In Kentico Admin - Settings page displays "500 - Internal server error"

Woodley Westbrook asked on August 28, 2020 21:15

Very recently our Kentico Admin in production environment displays "500 - Internal server error". In our Stage and Dev environments this does not occur, only Prod. When we view it in console we see this error - Failed to load resource: the server responded with a status of 500 () /CMSModules/Settings/Pages/Keys.aspx?displaytitle=False. We also see that the Categories are being displayed properly at this location - /CMSModules/Settings/Pages/Categories.aspx In other words the left-hand nav for that page displays without issue but the iframe in the content portion does generate the 500 error.

We searched and could not find any other instance of this so we were hoping that someone on the DevNet Team could point us in the right direction regarding a solution.

We are currently using Kentico v10.0.52

Please let me know if I omitted and any information.



Correct Answer

Woodley Westbrook answered on September 4, 2020 20:33

Hello David,

We did find the solution to this issue. We updated this line in webconfig file by adding a tilde and forward slash and it solved the issue.

location path="CMSModules/Settings/Pages/Keys.aspx"


0 votesVote for this answer Unmark Correct answer

Recent Answers

David te Kloese answered on August 29, 2020 00:21


Can you get any more information from the Event Log module?

A server error can be mean a lot of things, missing file, missing data, database error...

First thing that does come to mind is does this file actually exist on your file system:


Might have been removed by mistake.

1 votesVote for this answer Mark as a Correct answer

Woodley Westbrook answered on August 31, 2020 16:50

Hello David,

When we access the Admin and go to that page no errors are generated in the Event log. We can see us accessing the logon page but after that no errors are generated.

Yes, these files do exist on the server. We are thinking that we would go to the page and start commenting out segments to see if we can narrow down where the error is being generated.


0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on August 31, 2020 17:10

Any recent hotfix, upgrades or deployments? Perhaps a custom module with custom (non-default-Kentico) settings not properly deployed?

0 votesVote for this answer Mark as a Correct answer

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