HTTP Error 500.19 when publish .net core project into iis











up vote
7
down vote

favorite












error



I want to publish a sample .net core web application on my pc's IIS manager but I failed. I am using Microsoft guidance but it doesn't work for me, if you have reasonable experience to fix this problem I would be grateful to see your suggestions.










share|improve this question




























    up vote
    7
    down vote

    favorite












    error



    I want to publish a sample .net core web application on my pc's IIS manager but I failed. I am using Microsoft guidance but it doesn't work for me, if you have reasonable experience to fix this problem I would be grateful to see your suggestions.










    share|improve this question


























      up vote
      7
      down vote

      favorite









      up vote
      7
      down vote

      favorite











      error



      I want to publish a sample .net core web application on my pc's IIS manager but I failed. I am using Microsoft guidance but it doesn't work for me, if you have reasonable experience to fix this problem I would be grateful to see your suggestions.










      share|improve this question















      error



      I want to publish a sample .net core web application on my pc's IIS manager but I failed. I am using Microsoft guidance but it doesn't work for me, if you have reasonable experience to fix this problem I would be grateful to see your suggestions.







      c# .net-core iis-8 publishing






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 17 at 18:55









      ekad

      11.9k123641




      11.9k123641










      asked Nov 25 '16 at 12:45









      Ali Jahanbin

      4814




      4814
























          4 Answers
          4






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found.
          Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.






          share|improve this answer





















          • Dear Andy I like to thank u for your immediate response! It worked. Thank you man
            – Ali Jahanbin
            Nov 25 '16 at 13:21






          • 1




            Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
            – Andy Lamb
            Nov 25 '16 at 13:29










          • Of course, actually I forgot to accept, excuse me. thanks again.
            – Ali Jahanbin
            Nov 27 '16 at 13:54


















          up vote
          11
          down vote













          I was missing the AspNetCoreModule from IIS->Modules. One that was installed I no longer had the 500.19 error.



          To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS



          Here is the page from Microsoft to find the download: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x






          share|improve this answer























          • In your case "Config Error" field would be a different message.
            – Lex Li
            Apr 20 at 12:09






          • 1




            Thanks for the blog. Really helped me understand how .net core apps were hosted.
            – Ash
            Oct 8 at 12:48


















          up vote
          2
          down vote













          You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.



          Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":



          enter image description here



          Before installing this you have to install the right version of runtime:
          https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1
          Than install the right version of "Hosting Bundle Installer".



          "Hosting Bundle Installer" is:
          .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library,
          and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.






          share|improve this answer





















          • I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
            – Trevor Yokum
            Jun 15 at 20:23










          • I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
            – Sadjad Khazaie
            Jun 17 at 16:58


















          up vote
          1
          down vote













          Sure, you have to follow this tutorial to deploy to IIS:



          https://docs.microsoft.com/en-us/aspnet/core/publishing/iis



          I would suggest you to do this:




          1. Publish your web application to desktop.


          2. Copy the folder to the server.



          3. Open cmd and run cd





          4. In cmd run
            dotnet webapplication.dll


          5. You should see that application is run and waiting for responses on localhost:port.


          6. Open browser and navigate there. It should work.



          Otherwise, you will be able to see all the errors in the cmd window.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40805402%2fhttp-error-500-19-when-publish-net-core-project-into-iis%23new-answer', 'question_page');
            }
            );

            Post as a guest
































            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote



            accepted










            The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found.
            Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.






            share|improve this answer





















            • Dear Andy I like to thank u for your immediate response! It worked. Thank you man
              – Ali Jahanbin
              Nov 25 '16 at 13:21






            • 1




              Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
              – Andy Lamb
              Nov 25 '16 at 13:29










            • Of course, actually I forgot to accept, excuse me. thanks again.
              – Ali Jahanbin
              Nov 27 '16 at 13:54















            up vote
            1
            down vote



            accepted










            The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found.
            Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.






            share|improve this answer





















            • Dear Andy I like to thank u for your immediate response! It worked. Thank you man
              – Ali Jahanbin
              Nov 25 '16 at 13:21






            • 1




              Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
              – Andy Lamb
              Nov 25 '16 at 13:29










            • Of course, actually I forgot to accept, excuse me. thanks again.
              – Ali Jahanbin
              Nov 27 '16 at 13:54













            up vote
            1
            down vote



            accepted







            up vote
            1
            down vote



            accepted






            The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found.
            Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.






            share|improve this answer












            The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found.
            Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 25 '16 at 12:54









            Andy Lamb

            1,1971017




            1,1971017












            • Dear Andy I like to thank u for your immediate response! It worked. Thank you man
              – Ali Jahanbin
              Nov 25 '16 at 13:21






            • 1




              Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
              – Andy Lamb
              Nov 25 '16 at 13:29










            • Of course, actually I forgot to accept, excuse me. thanks again.
              – Ali Jahanbin
              Nov 27 '16 at 13:54


















            • Dear Andy I like to thank u for your immediate response! It worked. Thank you man
              – Ali Jahanbin
              Nov 25 '16 at 13:21






            • 1




              Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
              – Andy Lamb
              Nov 25 '16 at 13:29










            • Of course, actually I forgot to accept, excuse me. thanks again.
              – Ali Jahanbin
              Nov 27 '16 at 13:54
















            Dear Andy I like to thank u for your immediate response! It worked. Thank you man
            – Ali Jahanbin
            Nov 25 '16 at 13:21




            Dear Andy I like to thank u for your immediate response! It worked. Thank you man
            – Ali Jahanbin
            Nov 25 '16 at 13:21




            1




            1




            Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
            – Andy Lamb
            Nov 25 '16 at 13:29




            Glad to have helped. Could you accept the answer so others facing the same problem are directed to the correct solution?
            – Andy Lamb
            Nov 25 '16 at 13:29












            Of course, actually I forgot to accept, excuse me. thanks again.
            – Ali Jahanbin
            Nov 27 '16 at 13:54




            Of course, actually I forgot to accept, excuse me. thanks again.
            – Ali Jahanbin
            Nov 27 '16 at 13:54












            up vote
            11
            down vote













            I was missing the AspNetCoreModule from IIS->Modules. One that was installed I no longer had the 500.19 error.



            To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS



            Here is the page from Microsoft to find the download: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x






            share|improve this answer























            • In your case "Config Error" field would be a different message.
              – Lex Li
              Apr 20 at 12:09






            • 1




              Thanks for the blog. Really helped me understand how .net core apps were hosted.
              – Ash
              Oct 8 at 12:48















            up vote
            11
            down vote













            I was missing the AspNetCoreModule from IIS->Modules. One that was installed I no longer had the 500.19 error.



            To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS



            Here is the page from Microsoft to find the download: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x






            share|improve this answer























            • In your case "Config Error" field would be a different message.
              – Lex Li
              Apr 20 at 12:09






            • 1




              Thanks for the blog. Really helped me understand how .net core apps were hosted.
              – Ash
              Oct 8 at 12:48













            up vote
            11
            down vote










            up vote
            11
            down vote









            I was missing the AspNetCoreModule from IIS->Modules. One that was installed I no longer had the 500.19 error.



            To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS



            Here is the page from Microsoft to find the download: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x






            share|improve this answer














            I was missing the AspNetCoreModule from IIS->Modules. One that was installed I no longer had the 500.19 error.



            To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS



            Here is the page from Microsoft to find the download: https://docs.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jul 13 at 16:31

























            answered Sep 27 '17 at 7:46









            Enkode

            2,47422136




            2,47422136












            • In your case "Config Error" field would be a different message.
              – Lex Li
              Apr 20 at 12:09






            • 1




              Thanks for the blog. Really helped me understand how .net core apps were hosted.
              – Ash
              Oct 8 at 12:48


















            • In your case "Config Error" field would be a different message.
              – Lex Li
              Apr 20 at 12:09






            • 1




              Thanks for the blog. Really helped me understand how .net core apps were hosted.
              – Ash
              Oct 8 at 12:48
















            In your case "Config Error" field would be a different message.
            – Lex Li
            Apr 20 at 12:09




            In your case "Config Error" field would be a different message.
            – Lex Li
            Apr 20 at 12:09




            1




            1




            Thanks for the blog. Really helped me understand how .net core apps were hosted.
            – Ash
            Oct 8 at 12:48




            Thanks for the blog. Really helped me understand how .net core apps were hosted.
            – Ash
            Oct 8 at 12:48










            up vote
            2
            down vote













            You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.



            Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":



            enter image description here



            Before installing this you have to install the right version of runtime:
            https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1
            Than install the right version of "Hosting Bundle Installer".



            "Hosting Bundle Installer" is:
            .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library,
            and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.






            share|improve this answer





















            • I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
              – Trevor Yokum
              Jun 15 at 20:23










            • I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
              – Sadjad Khazaie
              Jun 17 at 16:58















            up vote
            2
            down vote













            You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.



            Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":



            enter image description here



            Before installing this you have to install the right version of runtime:
            https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1
            Than install the right version of "Hosting Bundle Installer".



            "Hosting Bundle Installer" is:
            .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library,
            and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.






            share|improve this answer





















            • I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
              – Trevor Yokum
              Jun 15 at 20:23










            • I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
              – Sadjad Khazaie
              Jun 17 at 16:58













            up vote
            2
            down vote










            up vote
            2
            down vote









            You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.



            Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":



            enter image description here



            Before installing this you have to install the right version of runtime:
            https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1
            Than install the right version of "Hosting Bundle Installer".



            "Hosting Bundle Installer" is:
            .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library,
            and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.






            share|improve this answer












            You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.



            Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":



            enter image description here



            Before installing this you have to install the right version of runtime:
            https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1
            Than install the right version of "Hosting Bundle Installer".



            "Hosting Bundle Installer" is:
            .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library,
            and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered May 29 at 11:46









            Sadjad Khazaie

            1,0231016




            1,0231016












            • I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
              – Trevor Yokum
              Jun 15 at 20:23










            • I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
              – Sadjad Khazaie
              Jun 17 at 16:58


















            • I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
              – Trevor Yokum
              Jun 15 at 20:23










            • I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
              – Sadjad Khazaie
              Jun 17 at 16:58
















            I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
            – Trevor Yokum
            Jun 15 at 20:23




            I'm not entirely sure why this was downvoted, Sadjad. Your solution pointed me to the correct spot almost instantly. I had downloaded and initiated the x64 Installer instead of using the Hosting Bundle Installer. As soon as I did so, everything worked flawlessly. Thank you!
            – Trevor Yokum
            Jun 15 at 20:23












            I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
            – Sadjad Khazaie
            Jun 17 at 16:58




            I am happy to read this. The reason that it was down-voted, was because I created the same answer to similar question somewhere else.I didn't like it and I don't think its fair. Thank you and success.
            – Sadjad Khazaie
            Jun 17 at 16:58










            up vote
            1
            down vote













            Sure, you have to follow this tutorial to deploy to IIS:



            https://docs.microsoft.com/en-us/aspnet/core/publishing/iis



            I would suggest you to do this:




            1. Publish your web application to desktop.


            2. Copy the folder to the server.



            3. Open cmd and run cd





            4. In cmd run
              dotnet webapplication.dll


            5. You should see that application is run and waiting for responses on localhost:port.


            6. Open browser and navigate there. It should work.



            Otherwise, you will be able to see all the errors in the cmd window.






            share|improve this answer

























              up vote
              1
              down vote













              Sure, you have to follow this tutorial to deploy to IIS:



              https://docs.microsoft.com/en-us/aspnet/core/publishing/iis



              I would suggest you to do this:




              1. Publish your web application to desktop.


              2. Copy the folder to the server.



              3. Open cmd and run cd





              4. In cmd run
                dotnet webapplication.dll


              5. You should see that application is run and waiting for responses on localhost:port.


              6. Open browser and navigate there. It should work.



              Otherwise, you will be able to see all the errors in the cmd window.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                Sure, you have to follow this tutorial to deploy to IIS:



                https://docs.microsoft.com/en-us/aspnet/core/publishing/iis



                I would suggest you to do this:




                1. Publish your web application to desktop.


                2. Copy the folder to the server.



                3. Open cmd and run cd





                4. In cmd run
                  dotnet webapplication.dll


                5. You should see that application is run and waiting for responses on localhost:port.


                6. Open browser and navigate there. It should work.



                Otherwise, you will be able to see all the errors in the cmd window.






                share|improve this answer












                Sure, you have to follow this tutorial to deploy to IIS:



                https://docs.microsoft.com/en-us/aspnet/core/publishing/iis



                I would suggest you to do this:




                1. Publish your web application to desktop.


                2. Copy the folder to the server.



                3. Open cmd and run cd





                4. In cmd run
                  dotnet webapplication.dll


                5. You should see that application is run and waiting for responses on localhost:port.


                6. Open browser and navigate there. It should work.



                Otherwise, you will be able to see all the errors in the cmd window.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 10 at 20:11









                tayfun Kılıç

                112




                112






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40805402%2fhttp-error-500-19-when-publish-net-core-project-into-iis%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest




















































































                    Popular posts from this blog

                    The Sandy Post

                    Danny Elfman

                    Pages that link to "Head v. Amoskeag Manufacturing Co."