Clever Geek Handbook

Process ID "xxxx" is not running in Visual Studio (2013 to 2017 ~)

I can't start any application from Visual Studio 2013, it gives Process with id "xxxx" not running message. I have used Telerik as well. I have tried all solutions from internet (except reinstalling visual studio), nothing helped me, please help, thanks.

Ps: WebForm base.

+4


source to share


10 replies


  • Open Visual Studio as Administrator
  • Right click your project and click Unload Project

  • Right click your project again and click Edit PROJECT_NAME.csproj

  • Find the code below and delete it

    <DevelopmentServerPort>63366</DevelopmentServerPort>
<DevelopmentServerVPath>/</DevelopmentServerVPath>
<IISUrl>http://localhost:63366/</IISUrl>

  • Save and close the file

  • Right click your project and reload it.
  • See if it works


+12


source


I faced the same problem and found a great way to deal with this problem as follows

1. Open your project file:
* .csproj
2. Try to find the lines shown below (by finding "DevelopmentServerPort" in your project file).

 <DevelopmentServerPort>62140</DevelopmentServerPort>    
 <DevelopmentServerVPath></DevelopmentServerVPath>    
 <IISUrl>http://localhost:62116/</IISUrl>

3. Once found, remove the following tags from your project file:

4. Save and close the file. If your project is open, you may be prompted to reload the project.



full link url

+2


source


I had this problem and the solutions found on the internet did not help. Here's what worked for me:

When the problem occurs ...

  • Change the startup project to a different project in your solution.
  • Run this project once.
  • Change the startup project to the original project.

In my case, an error occurred because the selected port was already in use. This means that you need to select a new port. For some reason, the chosen port is sometimes taken and sometimes free.

To select a new port, right click on your project, then Properties

. On the tab, Web

change the port in the file Project URL

.

You should avoid using port 0 to 1024. Choose a funky number such as 12321 or 23432, which is high enough to be easily remembered.

+1


source


I had the same problem and the solution was pretty simple.

  • close your solution.
  • rerun the solution as administrator.
  • rebuild it.
  • try now.

You may need to restart your computer. Do not remove any of the csproj parameters.

0


source


Only unloading and reloading the startup project fixed, I didn't really need any other steps.

0


source


The only thing that worked for me was restarting Visual Studio completely.

I tried in vain to kill all the suspended processes vstest.executionengine.exe and vstest.discoiveryengine.exe using Process Explorer.

0


source


I tried the first error and it didn't work for me. However, what worked for me was to delete the hidden ".vs" folder that is at the root of the solution. You will have to close visual studio, delete the folder, reopen the solution, and Visual Studio will create a new "correct" folder instance.

0


source


I have the same problem and examine the project directory and delete this hidden .vs folder. If you don't see this folder, go to your folder, show all files and then delete that folder.
Close the project, then clean and build, then type F5. enter image description here

0


source


For me, using Visual Studio 2017, the tags mentioned in ali abid's answer were located in the csproj.user file.

However, removing these tags did not solve my problem. For me, I set the virtual directory in the project properties with a low (9500) port number. I think some other process decided to use this port and was blocking IIS Express from starting.

The solution was to edit the project properties, update the Web -> Project Url to use the new port, and create a virtual directory.

0


source


I have the same problem and none of these solutions worked for me. When I open the project and press F5, I get the error "process with id not running", but if I leave Visual Studio open and wait for about 30 minutes and then press F5 it works fine!

Does anyone know why?

-2


source






More articles: