Home Dashboard Directory Help
Search

VS 2010/2012/2013 Ultimate & IIS Express - "Process with Id of xxxx is not running." by GraGra_33


Status: 

Active


10
0
Sign in
to vote
Type: Bug
ID: 806692
Opened: 10/27/2013 3:45:56 AM
Access Restriction: Public
2
Workaround(s)
view
4
User(s) can reproduce this bug

Description

Dev environment: Fresh install of Windows 8.1 Pro, VS2010 Ultimate, VS2012 Ultimate, & VS2013 Ultimate.

Test done: On all 3 versions of VS - File > New Project > MVC (Default) with Properties > Web > Servers: IIS Express (8.0).

All 3 versions of VS are reporting:

* VS2010 & VS2012: "Unable to launch the IIS Express Web server.

* VS2013: "Process with an Id of xxx is not running." with debug trace reports "The program '[7720] iisexpress.exe: Program Trace' has exited with code 0 (0x0). The program '[xxxx] iisexpress.exe' has exited with code -1073741816 (0xc0000008) 'An invalid handle was specified'."

I have run VS in and out of Administrator mode and receive the same results. I have uninstalled IIS Express 8.0 and Reinstalled. I have checked that IIS Express is selected in Tools > Opetions > Projects and Solutions > Web Projects > Use IIS Express is checked.

I am out of ideas... Any thoughts???

NOTE: Original post here: http://social.msdn.microsoft.com/Forums/vstudio/en-US/7577bac7-95b8-46c3-9dd0-2fcf340872f7/mvc5iis-express-unable-to-debug-code-not-running
Details
Sign in to post a comment.
Posted by DarkGray Knight on 5/15/2014 at 9:03 AM
Still an issue for me
Posted by dpolanco on 3/13/2014 at 12:57 AM
Hi guys, for me worked closing VS and renaming the iisexpress folder in documents. It seems that somehow a process got attached and couldn't be released not allowing the debug. When I restarted VS and relaunched the debug a new brand iisexpress folder was created and i was back on the game!
Hope it helps
Posted by Matthew Petersen on 12/16/2013 at 1:36 PM
What worked for me was to got to the documents and iisexpress folder and rename the Config file to be config.poo

i then f5'd and problem solved.

didnt need to quit vs or reboot.
Posted by DarkGray Knight on 12/4/2013 at 7:19 PM
I am having a similar problem and the workaround doesn't work for me.
Posted by Microsoft on 10/28/2013 at 2:22 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by GraGra_33 on 10/27/2013 at 8:08 PM
The solution to the above problem was a simple one. Close down dev environments, go to Documents folder and rename IISExpress. Now set environment variable _CSRUN_DISABLE_WORKAROUNDS ( ref: http://gauravmantri.com/2013/02/05/workaround-for-iis-express-crashing-when-running-windows-azure-cloud-service-web-role-with-multiple-instances-in-windows-azure-sdk-1-8-compute-emulator/ ).

Now reboot PC, start VS, load website and run in debug. IIS automatically regenerated the IISExpress folder and the environment variable resolved conflicts.
Posted by Microsoft on 10/27/2013 at 3:53 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by Nik Ivancic on 3/25/2014 at 6:50 PM
The workaround for me is a lot simpler version of what was posted GraGra_33 - all I needed to do is to rename the IISExpress folder after closing the Visual Studio 2013. Starting the Visual Studio again resulted with recreation of the IISExpress folder and everything worked fine.

Note, that my Visual Studio is Premium model - not Ultimate
Posted by GraGra_33 on 10/27/2013 at 8:12 PM
The solution to the above problem was a simple one. Close down dev environments, go to Documents folder and rename IISExpress. Now set environment variable _CSRUN_DISABLE_WORKAROUNDS ( ref: http://gauravmantri.com/2013/02/05/workaround-for-iis-express-crashing-when-running-windows-azure-cloud-service-web-role-with-multiple-instances-in-windows-azure-sdk-1-8-compute-emulator/ ).

Now reboot PC, start VS, load website and run in debug. IIS automatically regenerated the IISExpress folder and the environment variable resolved conflicts.