none
"unable to start debugging on the web server" MSVSMON.EXE failed to start. VS2010 error

    Question

  • hi there,

    having a real problem getting VS2010 to debug IIS.

    I've searched on the internet for a few days now and tried every single solution I can.  VS2008 works perfectly but I've installed VS2010 and when trying to debug an IIS site (by pressing F5 on a project that uses IIS) I get the error message

    "unable to start debugging on the web server.  Microsoft Visual Studio Debugging Monitor (MSVSMON.EXE) failed to start.  If this problem persists, please repair your Visual installation via "add or remove programs" in the control panel."

    when i try attaching the process manually, i get the same message.
    I've tried repairing the software.  I tried it, it failed, so I uninstalled using the Microsoft Visual Studio 2010 Uninstall Utility (http://archive.msdn.microsoft.com/vs2010uninstall/Release/ProjectReleases.aspx?ReleaseId=4321), then reinstalled and it still has the same problem.  With the SP1 update this still happens.  I can run the website fine when running "start without debugging" and it runs fine.

    I've gone through all the guides I can and all tried all the settings on IIS I can and still no luck.  I'm using Windows 7 64bit if that means anything.  I can detail much more about all the things i've tried.

    also have a laptop and have done the same, installing VS2010 and TFS (also on win7 64bit), and this works perfectly for debugging.  Didn't have to mess around at all.  I can't see any difference between this and my PC with the problem.   I'm scratching my head here and thinking I might have to format my PC and try again from a fresh install (which would be seriously annoying!)

    Thanks to anyone that reads this,
    Dan Gent
    Thursday, September 29, 2011 11:16 AM

Answers

  • Hello Buswell,

    Glad to see that you have found the reason which generate this issue. If everything is work well in you laptop, we just make sure the another PC has something wrong. It should be not related to VS. So maybe you could reinstall system to have a check or others. Thanks for your understanding.

    Thanks, 


    Jack Zhai[MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    • Unmarked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    • Marked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    Saturday, October 01, 2011 2:44 AM
    Moderator

All replies

  • Hello,

    See this  article VS2010 : MSVSMON.exe failed to start.

    This is MSDN link, see Error: Unable to Start Debugging on the Web Server. Hope it helps.

    Thanks,


    Jack Zhai[MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, September 30, 2011 3:23 AM
    Moderator
  • Hi Jack,

    Much thanks for your help, but they were the first things that i tried.  the registry edit doesn't help, and the MSDN guide was the first thing I followed as VS linked to it.  the problem I have I can't do "attach to process", where as with the above problem (as i've read on other threads) they can attach to a process.  The above MSDN guide has nothing on what happens if you can't attach to a process. it just tells you to do it.

    Thats why my problem is so odd and I think something has gone seriously wrong with VS2010 (is it known for being buggy?)

    Thanks for the replies,

    Buswell

    Friday, September 30, 2011 8:33 AM
  • Hello Buswell,

    Thanks for your reply.

    You could provide your steps or links to create a similar project that use IIS, so I could try to reproduce it with my PC.

    In addtion, you can submit this feedback to Microsoft Connect feedback Center in formal format. Microsoft engineers will evaluate them seriously and report to Product Group.
     
    http://connect.microsoft.com/VisualStudio/ ,

    Thanks,


    Jack Zhai[MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, September 30, 2011 9:24 AM
    Moderator
  • Hi Jack,


    You won't be able to reproduce it on your PC.  it happens when I create a new empty project and use IIS.  the same projects work fine on my laptop it is just something seriously wrong on this PC.  If i'm going to have to submit bug reports to Microsoft then I think I'll just have to format my PC first.

    what a nightmare, I wish I could stick with VS2008.   ;^)
    is VS2010 known for being horrendously buggy or is it just my luck? 

     

    Thanks for your help anyway. 

    Friday, September 30, 2011 10:53 AM
  • Hello Buswell,

    Glad to see that you have found the reason which generate this issue. If everything is work well in you laptop, we just make sure the another PC has something wrong. It should be not related to VS. So maybe you could reinstall system to have a check or others. Thanks for your understanding.

    Thanks, 


    Jack Zhai[MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    • Unmarked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    • Marked as answer by Buswell Wednesday, October 05, 2011 4:04 PM
    Saturday, October 01, 2011 2:44 AM
    Moderator
  • i've fixed it now. ended up formatting machine, reinstalling windows 7, and then taking backups everytime i installed a new program so i could roll back. installed VS2010 first, F5 worked. then installed VS2008 & everything else and debugging still works on VS2010. not sure what happened as the above problem happened on a fresh install. something must have corrupted something somewhere

    thanks for all your help and narrowing this problem down to something that was worth formatting my PC to fix.

    cheers,
    Buswell
    Wednesday, October 05, 2011 4:04 PM