Publishing aspnet core project to IIS

Question

0.00/5 (No votes)

See more:

I have successfully generated a publish folder via following command;

dotnet publish -c Release -r win10-x64 --self-contained

Here is the generated exe file in publish folder. If I run the exe file, the website runs with no problem on localhost:5000.

However; when I try to put this website on iis, I have the following error;

HTTP Error 500.19 - Internal Server Error<pre>

Error Code     0x8007000d<pre>

Here is my web config file;

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <handlers>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
    </handlers>
    <aspNetCore processPath=".\AURORA.MvcWebUI.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
  </system.webServer>
</configuration> 
<!--ProjectGuid: 1E855145-26EA-4E34-8527-9A44CCB14290-->

Could you help me please?

What I have tried:

I have tried to delete each part of the web config file but could not make it work

Posted 10-Oct-17 23:04pm

tasinsahin

Updated 11-Oct-17 7:54am

Add a Solution

Comments

Wessel Beulink 11-Oct-17 5:10am

Your web configuration doesn't matter. Just clear the map, redeploy and edit the web configuration by IIS. Even without web configuration IIS will create a new one.

tasinsahin 11-Oct-17 5:37am

Map? What map? Could you please tell it step by step? I am really new to iis :)

2 solutions

Solution 1

Create folder [

logs

] folder inside your deploy folder.

Posted 10-Oct-17 23:57pm

kulile

Comments

tasinsahin 11-Oct-17 5:59am

sorry didnt solve the problem

kulile 11-Oct-17 6:01am

What does if say on the log file that is produced on that folder?

kulile 11-Oct-17 6:08am

You might want to have a look at this

https://stackoverflow.com/questions/16836473/asp-net-http-error-500-19-internal-server-error-0x8007000d

tasinsahin 11-Oct-17 13:54pm

thanks for the reply :)

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

tasinsahin · Accepted Answer · 2017-10-11T07:53:00

Solution 2

Reinstalling aspnet core module solved my problem.

Posted 11-Oct-17 7:53am

tasinsahin

Updated 11-Oct-17 7:54am

v2