Last post Jul 20, 2016 02:24 PM by ygoe
Jul 15, 2016 08:46 AM|ygoe|LINK
I've started an ASP.NET Core web application with the RC2 version and published it to a Windows server with IIS. Everything worked fine.
When RTM came out, I upgraded VS and the hosting tools, restarted the server, republished the app to the server, and the web application fails to start.
The error message in the browser says "HTTP Error 502.5 - Process Failure". The Windows event log (Application log) says "Failed to start process with commandline '"dotnet" .\EssBot.dll', ErrorCode = '0x80004005'." I followed the Common Errors section of
the ASP.NET Core documentation, publishing to IIS. Everything looks correct. C:\Program Files\dotnet is in the %PATH%, the file names and paths are correct and files exist.
What's wrong with this? Do I need to restart with a new VS project from scratch every time a new ASP.NET Core version comes out?
Jul 16, 2016 08:44 AM|damienBod|LINK
I had this problem as well. What I did to fix it was uninstall all existing dotnet versions from the computer, restart, and install the new version, restart and it worked.
Not certain if all the steps are required and what fixed the issue, but it worked after. Maybe you could try this.
Hope this helps
Jul 16, 2016 11:52 AM|maherjendoubi|LINK
Would you please share the crash report? You will find it here %AppData%\Local\Microsoft\Windows\WER\ReportArchive
You can open them easily with nodepad++
Jul 18, 2016 07:28 AM|ygoe|LINK
There is only a single version of "Microsoft .NET Core 1.0.0" installed, the runtime and Windows Server Hosting. Should I uninstall this and re-install it again?
The path "%AppData%\Local\Microsoft\Windows\WER\ReportArchive" does not exist on that server so there's nothing to share here.
Jul 18, 2016 03:50 PM|maherjendoubi|LINK
I really apologize! Here is the right path %LocalAppData%\Microsoft\Windows\WER\ReportArchive
Before reinstalling, let's checl the crash report please.
Jul 20, 2016 09:30 AM|ygoe|LINK
That resolves to the same path and it still doesn't exist.
Jul 20, 2016 09:44 AM|maherjendoubi|LINK
Try to analyse using fiddler http://www.telerik.com/fiddler
Jul 20, 2016 11:46 AM|ygoe|LINK
IIRC Fiddler is an HTTP proxy that I use on my local computer between my browser and the network. What am I supposed to do there? My problem lies on the server side. I just don't get enough details about the issue to analyse it.
I'm going to uninstall and re-install the ASP.NET Core hosting software and see if that helps.
Jul 20, 2016 12:26 PM|Radomir|LINK
Do you get any more detailed error message if you try running "dotnet EssBot.dll" from command prompt manually? Does a test new project created w/ RTM tooling work?
Jul 20, 2016 12:33 PM|anurajp|LINK
Please look into the common errors sections in publishing to IIS - https://docs.asp.net/en/latest/publishing/iis.html#common-errors
Jul 20, 2016 02:24 PM|ygoe|LINK
Running "dotnet essbot.dll" on the command prompt gave me a good message. It said "The specified framework 'Microsoft.NETCore.App', version '1.0.0-rc2-3002702' was not found." That led me into checking my project.json and it was all over rc2. That's probably
the problem why my app wasn't working anymore.
Now I've changed that and upgraded all NuGet packages but the build fails with an error message from Microsoft.DotNet.Common.Targets which sounds like the dark side of MSBuild. The message suggests running "dotnet restore". That fails with the message "error:
Tools must specify a version range.", a message only found a single time on the internet. (Now it's two times.) I guess rc2 to RTM upgrades aren't working properly and I need to create a new project in Visual Studio.