Server Error in 'Kentico13' Application - IIS 10

Tim Bush asked on February 21, 2025 19:24

Hi,

I'm running into some issues when deploying our Kentico 13 admin site to IIS 10 running on Windows Server 2019. Everything works fine on my local machine; both the live site and the CMS bootup fine. Locally I connect to our dev SQL Server DB, these sites are also configured to connect to the same DB when hosted on our dev server.

Here is how I have IIS currently configured: - Under "Sites" I've added a website called dev.oursite.com. This site uses the DefaultAppPool. - Under this website I've created 2 virtual directory applications;

1. Kentico13 - App Pool is configured for .NET CLR Version V4.0.30319 - Integrated. Location:                    
    D:\inetpub\wwwroot\dev.ourwebsite.com-Admin_Site

2. Live - App Pool is configured for .NET CLR Version "No Managed Code" - Integrated. Location: 
    D:\inetpub\wwwroot\dev.ourwebsite.com-Live_Site

I've published both of these projects via Visual Studio using the Release Profile, I have the publish profile dump the Release publish files on my local machine and then I move them to our IIS server manually. For the live site I open OURWEBSITE.Web.sln and publish just the ASP.NET Core app and then move the files to the server. For the CMS side, I open WebApp.sln and publish the CMSApp.proj and move the files to the server. I don't have any precompiling enabled.

The live site will run when I browse it locally, but I cannot seem to get the CMS site to run, I'm getting the typical:

Server Error in '/Kentico13' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

I've set the customErrors mode to "Off", but I'm still not getting any detailed errors about what's going on. The logs in "D:\inetpub\logs\LogFiles" show the 500 error, but that's it. The HTTPERR logs (C:\Windows\System32\drivers\etc\hosts) are not showing anything related to what's going on.

I've also configured the PresentationURL and Adminstration domain name in the CMS, per your docs; https://dev.oursite.com/Live and dev.oursite.com/Kentico13 respectively. I have aliases setup for localhost as well.

Any insight into what I'm doing wrong here or things I should try would be tremendously helpful. Please let me know if you need additional info.

Recent Answers


Juraj Ondrus answered on February 25, 2025 08:39

How are you publishing the admin app? Did you enabled the deployment mode for publishing/pre-compilation? The virtual object must be stored on disk in this case.

0 votesVote for this answer Mark as a Correct answer

Tim Bush answered on February 25, 2025 14:01

Hi Juraj,

I just enabled deployment mode, got the CMSVirtualFiles directory included in the CMSApp.proj and rebuilt the project. After that, I hit "Publish" on the CMSApp.proj and created a new publish profile with "Precompile during publishing" enabled. "Allow precompiled site to be updatable" is un-checked and "Do not merge" is selected.

After that I published the files to my local machine, I then copied them over to our dev server into the /Kentico13 virtual directory. I'm still getting the same error as above though. Is there any additional things I should try? Do you need anymore information from me?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on February 25, 2025 14:04

To check whether the issue is in Kentico - does the published project run on your local machine or not? This sounds like some environment related issue. Could you please try publishing in debug mode? Maybe it will display more details in the error.

0 votesVote for this answer Mark as a Correct answer

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