Process with an ID #### is not running in visual studio professional 2013 update 3

Question

I am trying to run any program on visual studio 2013 update 3 and I get the following alert box :

Process with an ID #### is not running . // every time there is different ID number showing

and in the error windows I get this error msg:

The program '[3148] iisexpress.exe' has exited with code -1073741816 (0xc0000008) 'An invalid handle was specified'.

Sometimes it runs and in the browser i get the following message : The webpage is not available.

I have looked around and try almost everything and I stil cannot fix the problem.

Please help anyone

Answer 1

First Error

For the first error:

Process with an ID #### is not running.

The following steps worked for me:

1. Close all instances of Visual Studio.
2. Rename the IISExpress folder (in my PC is in C:\Users\jmelosegui\Documents).
3. Add the _CSRUN_DISABLE_WORKAROUNDS Environment System variable with the value of 1.
   

4. Start Visual Studio in administrator mode. (In Windows, right click the executable file and select Run as administrator).

Second Error

The second error:

The webpage is not available

What caused this error:

I deleted IIS Express Development Certificate while playing with the SSL.

The following steps worked for me:

1. Go to Control Panel.
2. Select Add/Remove Programs.
3. Locate IIS 8.0 Express.
4. Right click on it then click Repair.
5. Your certificate should be back!

Hope this helps!

Answer 2

The following steps fix the problem for Visual Studio 2015 and Visual Studio 2017:

• Close VS.
• Navigate to the folder of the solution and delete the hidden .vs folder.
• Restart VS.
• Hit F5 and IIS Express should load as normal, allowing you to debug.

Note: Based on my experience and others in the comments, this problem seems to be caused by moving a project between workstations, environments, or versions of Visual Studio. There must be some environment specific information contained in the .vs folder.

Answer 3

Easily solved:

1. Open Visual Studio as an administrator
2. Right-click your project and click on 'Unload Project'
3. Again, right-click your project and click on 'Edit PROJECT_NAME.csproj'

4. Find the code below and delete it:

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

5. Save and close the file .csproj

6. Right-click your project and reload it
7. See its working

Answer 4

With respect to the first error:

Process with an ID #### is not running

This situation will sometimes occur when IIS Express fails to bind to a port. A likely reason for that is that some other process has already bound to that port. Visual Studio will launch the IISExpress.exe process (which will fail to bind to the port and exit again) and then attach to the now-terminated process, resulting in the above error.

To check, note the port number in your project settings (e.g. 12116) and then try:

netstat -ano | find "12116"

If another process has the port open, this will give its PID. You can then choose to kill the offending process or reallocate your own port number.

Answer 5

If you are using a 64-bit machine

Then the problem maybe due to Visual Studio use of 32-bit IIS-Express.

Solution: In Visual Studio, go to Tools menu > Options > Projects and Solutions > Web Projects > Enable the option "Use the 64 bit version of IIS Express" and click ok

Answer 6

I had the same problem. Just restarting Visual Studio worked for me.

Answer 7

@Kilanny your answer is correct. Most machines in 2015 are 64bit, so there's a lot of chances that you just need to enable the 64bit option under the Tools main navigation link menu. No need to configure other files or hard code ports. Besides, port assignment should be dynamic. This fix applies to 2013 With Update 3 and Visual Studio 2015 Community Edition.

Check the images below for a mini tutorial: (I'm just improving Kilanny's answer)

Answer 8

I tried the first error and that didn't help me. However What did work for me was to delete the hidden ".vs" folder which is at the solution root.

Answer 9

I had a similar problem with Chrome.

It appears that VS can't attach to the Chrome process for some reason.

Solution: 1. Close Chrome 2. With Chrome closed, start the web project and allow VS to open Chrome.

Hope that helps.

Answer 10

For me, none of the other solutions worked. The things I tried:

• Updating and patching everything associated with Visual Studio
• Reinstalling Visual Studio
• Reinstalling IIS Express
• Several reboots
• Adding the _WORKAROUND thing to the PATH
• Renaming the IIS folder under documents to regenerate the IIS config
• Manually editing the csproj file and removing the whole IIS settings section
• Changing the IIS executable usage to 64bit in VS settings
• Changing the port of IIS in the projects settings

After checking if the problem was persistent over different projects, it turned out that the problem only occurred in one specific projects. I figured that I had to delete all the user specific files in the solutions folder (such as bin, obj, *.suo, ...) I just deleted the whole solution folder and reverted the files in git.

TLDR: Try deleting user specific files/folders like bin, obj, *.suo, ...

Answer 11

go to Properties of the start up project, increment port number of the Project Url is probably the quickest way to get around this problem which I didn't read anyone mentioned yet.

And you don't need to restart VS as it can be a pain sometimes if you needed a few other instances needed to be running.

Answer 12

I found the solution here:

https://www.codeproject.com/Tips/1029540/Solved-Process-With-An-Id-Of-Is-Not-Running

Edited the project file and deleted the lines:

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

Answer 13

It looks like there are many solutions that work and some that don't...

My issue kept surfacing after a few test iterations. Yes restarting the PC and/or VS would resolve the issue...but temporarily.

My solution was to undo a security change I had enabled a couple days earlier to Controlled folder access under Ransomware protection.

I undid this change by:
(right click Start) Setting->Update & Security->Windows Security->Virus & threat protection-> Virus & threat protection settings

Under Controlled folder access Click->Manage Controlled folder access (this is also the Ransomware protection screen)

Turn Controlled folder access off.

This was 100% the issue for me as I was able to run my test without restarting VS.

Answer 14

I had the same problem, and what needed to be done was setup IIS Express properly.

I right clicked on my project Properties => Web (tab) and on Servers: Project URL was already pre-populated and I clicked the button "Create Virtual Directory".

I had just reinstalled (refreshed) windows and the IIS was not setup b/c it was new.

Hope this helps.

Answer 15

I also had the same problem, doing the above didn't work for me. What my error turned out to be was twofold.

1. I had Opera as my default browser and it couldn't attach to that.
2. I had multiple startup projects so it wouldn't let me switch to IE until I change the default startup project back to just the MVC shell.

I set that project specifically as the startup, then I switched it back to launching IE and it started debugging again.

Hope that helps

Answer 16

I came across the same problem and found that somehow the file 'applicationhost.config' (in ..\Documents\IISExpress\config) had a different localhost port number (in the 'sites' section) to the one specified in project\properties\web. Changed them to the same number and the problem went away

Answer 17

What I did to make this go away:

Open C:\Users\gr_mext1\Documents\IISExpress\config\applicationhost.config and remove all <site> entries in <sites> do not remove <siteDefaults>!

In your project, go to Properties, Web and click "Create Virtual Directory".

Close and re-open visual studio, load your project and run

Fixed!

Answer 18

None of the listed solutions worked for me. Problem was some sort of conflicting state in local applicationhost.config file. Fix is easy, just delete one in your solution. For VS2015 it should be located in <path_to_your_solution>\Solution\.vs\config\. When you launch Debug, VS will recreate that file based on settings in your project file.

Answer 19

Resolution I found;

Head to the following directory

%userprofile%\documents\IISExpress\Config directory

Delete all files within that folder. Restart visual studio and works like a charm.

Answer 20

Deleting the hidden .vs folder didn't work for me since the port specified in my app was being used by another app. Doing the following worked for me:

1. Went to properties and then click the web tab.
2. Changed the port number in the Start Url and the Project URL.
3. Clicked Create Virtual Directory.
4. Save and Press F5.

Answer 21

I recently had the same issue with VS 2013 and IIS Express:

"Process with an ID #### is not running ." // every time there is different ID number showing.

Here was the solution I found that worked for me:

1) Go into the Documents -> IIS Express -> config -> applicationhost.config

2) I opened applicationhost.config in Notepad++

3) Under the tag , there are lines of code that looks like this:

    <add name="Clr4IntegratedAppPool" managedRuntimeVersion="v4.0" managedPipelineMode="Integrated" CLRConfigFile="%IIS_USER_HOME%\config\aspnet.config" autoStart="true">
                 <processModel loadUserProfile="true" />
        </add>

4) Remove these two lines

                <processModel loadUserProfile="true" /> 
        </add>

5) Change the END of the first line to

            <add name="Clr4IntegratedAppPool" managedRuntimeVersion="v4.0" managedPipelineMode="Integrated" CLRConfigFile="%IIS_USER_HOME%\config\aspnet.config" autoStart="true" />

Notice that all I did was close the tag by adding ' /' after "true".

I am now able to run my projects in a web browser AND debug my code.

Also, I had updated to Update 4, but was having the same issue. I believe appending the applicationhost.config file was what fixed the problem.

I hope this helps!

Answer 22

Same error Process with an ID #### is not running using visual studio 2015 RC.

Only go rid of the message after repair IIS 10 in Control Panel - Programs and Features

Renato

Answer 23

This can happen for various reasons, helpfully - if you run IISExpress.exe (\Program Files (x86)\IISExpress\iisexpress.exe for 32-bit, \Program Files\IISExpress\iisexpress.exe for 64-bit) in the command line, you'll get some more details. In my case:

C:\Program Files\IIS Express>iisexpress.exe

Filename: \\?\C:\Users\My.Username\Documents\IISExpress\config\applicationhost.config
Line number: 15
Error: Configuration file is not well-formed XML

Nice and easy to fix, that one my was my fault though!

Answer 24

For me, VS uses Firefox for the default browser. Restarting VS and closing all Firefox windows seems to resolve this issue.

Answer 25

If you're using git as source control, you should also make sure that any user specific files are ignored.

[Dd]ebug/
[Dd]ebugPublic/
[Rr]elease/
[Rr]eleases/
x64/
x86/
bld/
[Bb]in/
[Oo]bj/
[Ll]og/

If they're already tracked, then use git -r rm --cached

This resolved the error for me.

Answer 26

startMode="alwaysRunning" in $SOLUTION_DIR/bis/.vs/config/applicationhost.config caused it for me. Try to remove that string and everything will work again (even without restart of VS)

Answer 27

Close your instance of Visual studio. Start it again in Administration mode. "Run as Admin"

Answer 28

Running as administrator didn't seem to make a difference when I got this.

• Make sure all iisexpress.exe processes had been closed
• Edit <path_to_your_solution>\Solution\.vs\config\applicationhost.config

• Change the site name.

  <site name="MySite" id="1" serverAutoStart="true">

  to :

  <site name="MySite2" id="1" serverAutoStart="true">

• That fixed it for me

Answer 29

cmd - regedit-HKEY_LOCAL_MACHINE-SYSTEM-CurrentControlSet-Services-HTTP-START=3

Computer restarted.

worked for me!

Answer 30

What fixed it for me was running the project from a different file in my solution. Specifically, 2 of my files are named web.config, so I just ran from the other one.