locked
An error occurred while starting the application. .NET Core X86 v4.1.1.0 | Microsoft.AspNetCore.Hosting version 1.1.1 | Microsoft Windows 6.2.9200 RRS feed

  • Question

  • User1164381444 posted

    I've been building an ASP.NET Core app (1.1) and deploying it to an Azure instance I've had for a while.

    Everything was working fine, then suddenly I deploy and get this error when I navigate to the site:

    An error occurred while starting the application.
    
    .NET Core X86 v4.1.1.0    |   Microsoft.AspNetCore.Hosting version 1.1.1    |    Microsoft Windows 6.2.9200    |   Need help? 

    The publish succeeds (as it has) in the past.

    I had read via this post on StackOverflow that it's helpful to connect via FTP and delete everything in "Site/wwwroot" but when I attempted to FTP to the instance I was unable to connect.

    Any ideas on how to troubleshoot this instance?

    I'd be fine with a way to "reset" it because it's not in production yet and I can just deploy my code to it and be back where I want to be. :)

    Monday, March 13, 2017 4:56 PM

All replies

  • User527778624 posted

    Hi,

    You can check error logs and even edit your files using Azure SCM (kudu):

    https://blogs.msdn.microsoft.com/benjaminperkins/2014/03/24/using-kudu-with-windows-azure-web-sites/

    //and google for Azure SCM to find more links

    Tuesday, March 14, 2017 6:06 AM
  • User1328880122 posted

    I also have the same problem ... any real leads on how to fix this ? 

    Trying to deploy a solution that work just fine on my dev computer but when i deploy doesn't work at all and no error message whatsoever ...

    Friday, March 24, 2017 7:08 PM
  • User-1849651236 posted

    Hello,

    I have this same exact problem today.  I am using Visual Studio 2017 Community.  The publish procedure says: "========== Publish: 1 succeeded, 0 failed, 0 skipped =========="

    Did you ever find a soltion for this problem?

    Thanks,
    Tony

    Tuesday, April 11, 2017 8:38 PM
  • User1852039331 posted

    Is happening for me too.

    Saturday, April 15, 2017 2:13 PM
  • User1289604957 posted

    Hello,

    Before doing a publish, please make sure you choose Release, build for Release mode then do your publish.

    Best regards,

    Maher

    Saturday, April 29, 2017 2:02 PM
  • User-1759322447 posted

    In my case, I am using swagger and in my release build I was not creating the XML documentation file.

    Tuesday, October 3, 2017 10:39 PM
  • User-1254954967 posted

    This was exactly my problem as well. Thank you for posting your response. That could have been tough to figure out.

    Sunday, December 10, 2017 4:56 PM
  • User-973886032 posted

    Hello,

    Before doing a publish, please make sure you choose Release, build for Release mode then do your publish.

    Best regards,

    Maher

    How do you choose your release and build for release ? I cant seem to find that ?

    Saturday, January 20, 2018 7:50 AM
  • User-1268825352 posted

    In my case, I am using swagger and in my release build I was not creating the XML documentation file.

    Thank you, i still had no clue what was wrong after half a day of frustration.

    This was also the solution for me...

    Wednesday, February 21, 2018 2:45 PM