Failed to start dotnet.exe process

Question

I am trying to set up a new workspace and transfer all my projects from the old computer to the new one. However, I get this error when trying to start IIS Express:

Cannot start the process C: \ Program Files \ dotnet \ dotnet.exe. Web server request failed with status code 500.

I work in Visual Studio 2015 Update 3 and I am using .NET Core RC2. Does anyone know how to fix this and run my old projects on this new machine?

Answer 1

I had the same problem. I am looking for dotnet.exe in this directory, but it exists, but the debugger cannot execute it, so I will restart Visual Studio 2015 as an administrator and it works!

Answer 2

Just close VS, delete the project.lock.json file, open VS, the file will be restored, and you will have no more problems.

Answer 3

In my case, the problem was

1- I am updating (porting) my project (console / website) from .net 4.5 framework to donetcoreapp 2.0

2. The .NET Framework 4.5 project had Web.Config

3 dotnetcore 2.0 has no concept of web.config support.

4- So, whenever I started the project, I got the same error

Decision:

Just uninstalled 'Web.Config' and it started working for me.

Answer 4

in my case. I select "ProjectName" instead of "IIS Express" during runtime / debugging. and it works / opens with the console window and the selected browser, during debugging the console output window opens. Hope this works.

Answer 5

1. Close VS 2015 (it seems that the problem is resolved in VS 2017).
2. Delete all files in \ bin and \ obj. Remove project.lock.json.
3. Launch VS.
4. Rebuild.

If the above solution does not work in VS2017.Net Core, start from VS2017 as ADMIN. If you do not have ADMIN access to your computer, you can modify the launchSettings.json file so that it works on port 8080, as shown below, and then follow the 4 above steps.

"applicationUrl": " http: // localhost: 8080 / ",

Answer 6

Visual Studio 2017 -> The fix for me is to select the project name instead of IISExpress when debugging / starting.

Answer 7

Here is what worked for me:

I had the same problem, and it turned out that I just did not have the correct version of the runtime (1.1.0); instead, I tried to use builds 1.1.0 with runtime 1.0.1.

The solution is simple - download and install the SDK from here , but select the correct version! It turned out that if you want version 1.1.0, you need to select the "Current" option (button).

Basically, the problem is caused by the stupid interface on the specified page - if you do not pay attention, you will download v1.0.1, since this is the version of “LTS”, and the “LTS” option is there by default. What can I say ... Another disappointment from the .NET team at this time of crazy versions, crazy names, crazy platforms ...

Quotes from Sand: https://github.com/aspnet/Home/issues/1719

Answer 8

this is an answer to a question slightly different from what the OP posted. If the error message has only "dotnet.exe" and not the full path to dotnet.exe ("C: \ ProgramFiles \ DotNet \ dotnet.exe"), then check if dotnet.exe is in the System.Environment path if do not add it and run VS as administrator

Answer 9

The solution for me was to close the visual studio 2017 and reopen the solution. :)

Answer 10

This is caused by the wrong Way in the applicationhost.config file, you can find this file in the project folder. Go to the project folder. There you will find a folder named .vs if you cannot find it, and then in the folder is open. You must uncheck the "Remove hidden folder." After you find it in the config folder, you will find applicationhost.config . Open this file in notepad and indicate the location of the project as follows: -

<virtualDirectory path="/" physicalPath="c:\users\*****\documents\visual studio 2015\Projects\<ProjectFolderName>\<Projectname>" />

Hope this helps you.

Answer 11

In your startup project, make sure you select the Enable anonymous authentication option.

Answer 12

The solution in my case was removed by web.config from the project root. I was working on an ASPnetcore project and after a week an error started. I am not sure how this web.config file was added, but as soon as I delete that their error has been resolved.

Answer 13

I have this problem right after updating Microsoft Visual Studio 2017 pro, so far I have found 3 potential solutions:

• Restarting Visual Studio works, sometimes

• Delete% USERPROFILE% .nuget may fix the problem,

• Uninstall, then reinstall the dotnet SDK,

Answer 14

The solution for me (without administrator rights) was:

• Close all instances of visual studio 2017
• Open project
• Clean
• Rebuild
• Run

Answer 15

I was able to fix the error by deleting $ (solutionDir) .vs \ config \ applicationhost.config . After restarting, VS 2017 recreated the file.
After I moved the solution from one place to another, the file became invalid.

Thanks https://elanderson.net/2016/09/unable-to-start-process-dotnet-exe/ for this idea.

Answer 16

VS2017 and the solution has .NET Core 1.1 web applications.

This did not help: Delete the .VS folder, delete all bin directories, restart VS.

This helped: Installed the latest SDK (.NET Core SDK 1.0.4), this problem was resolved.

I got this problem all of a sudden after rebooting my computer, after which I installed PHP for IIS, URL Rewrite for IIS. But try reinstalling the SDK - it can work fine with it itself, instead of following the latest SDK.

Answer 17

I found a solution by reinstalling the .NET CORE SDK

Answer 18

iisreset in cmd as administrator did the job for me.

Answer 19

In my case, I accidentally install dotnet for the x86 platform when x64 is installed on my VS 2017. I am reinstalling dotnet for the x64 platform and now it works fine.

Answer 20

If you are using IIS Express instead of IIS Express , simply restart the service or:

1. open IIS
2. open your project folder from the Sites tree
3. select site
4. in the Manage Website click the " Restart " button

Answer 21

If an error occurs in the Web.config file, this will result in an error.

Answer 22

In my case, I have several projects in one solution, and not one of them has been configured as a launch project.

So, just right-click on the project (and not on the solution!), Select "Set as StartUp Project".

Answer 23

Fix from the program and functions allowed in my case (Windows Server 2012)

Answer 24

In my case, there was a setting in web.config and the wait time was not defined properly, instead of the actual value there was requestTimeout="00:06:00" TFS requestTimeout="00:06:00"

Here is how it looks. I hope it will be useful

 <system.webServer> <handlers> <remove name="aspNetCore"/> <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/> </handlers> <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:06:00" /> <httpRedirect enabled="false" /> </system.webServer> 

Answer 25

I had this, and it turned out that I was in Release build. Changed to Debug build and it worked.

Answer 26

In my case, I just change modules="AspNetCoreModuleV2" to modules="AspNetCoreModule" and work fine. The final web.config looks like the one below.

 <?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer> <handlers> <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" /> </handlers> <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00"> <environmentVariables /> </aspNetCore> <httpProtocol> <customHeaders> <remove name="X-Powered-By" /> </customHeaders> </httpProtocol> </system.webServer> </configuration> 

Answer 27

For those who have a problem with Visual Studio 2019, since they used the previous version of Visual Studio, simply delete the .vs folder located in the root directory of the project and restart the application, the problem should be solved. It worked for me.

Answer 28

I had to do a repair installation of .net core 2.2 sdk to fix this problem. Using VS 2017

Answer 29

My problem is solved with

Go to: the .vs \ config \ applicationhost.config file and set the overrideModeDefault parameter to Allow instead of Deny

 <section name="windowsAuthentication" overrideModeDefault="Allow" />