• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...
Common Tasks
  • Blog Home
  • Email Blog Author
  • RSS for comments
  • RSS for posts
Search
  • Advanced search options...
Tags
  • .NET Framewor
  • .NET Framework
  • Ajax/Javascript
  • ASP.NET
  • CLR
  • Cool stuff
  • DataAccess
  • Debugging/Windbg
  • Hotfix/Service Pack
  • IDEVDataCollector
  • IIS
  • Internet Explorer
  • Italian techs
  • LogParser
  • OT
  • Personal
  • Productivity
  • Random
  • Scripting/ASP
  • Security
  • Technology
  • Tools
  • Troubleshooting
  • Vista/Longhorn
  • Visual Studio
Archives
Archives
  • November 2010 (1)
  • October 2010 (1)
  • July 2010 (2)
  • April 2010 (1)
  • March 2010 (2)
  • February 2010 (2)
  • January 2010 (1)
  • October 2009 (2)
  • September 2009 (2)
  • August 2009 (1)
  • July 2009 (5)
  • June 2009 (1)
  • May 2009 (1)
  • April 2009 (3)
  • March 2009 (3)
  • February 2009 (5)
  • January 2009 (3)
  • December 2008 (5)
  • November 2008 (3)
  • October 2008 (2)
  • September 2008 (3)
  • August 2008 (3)
  • July 2008 (3)
  • June 2008 (5)
  • May 2008 (4)
  • April 2008 (8)
  • March 2008 (4)
  • February 2008 (5)
  • January 2008 (2)
  • December 2007 (4)
  • November 2007 (6)
  • October 2007 (6)
  • September 2007 (8)
  • August 2007 (6)
  • July 2007 (7)
  • June 2007 (10)
  • May 2007 (9)
  • April 2007 (12)
  • March 2007 (8)
  • February 2007 (5)
  • January 2007 (3)
  • December 2006 (1)
  • November 2006 (4)
  • October 2006 (2)
  • September 2006 (9)
  • August 2006 (2)
  • July 2006 (1)

Corrupt installation? Do not repair Visual Studio

MSDN Blogs > Never doubt thy debugger > Corrupt installation? Do not repair Visual Studio

Corrupt installation? Do not repair Visual Studio

Carlo Cardella
5 Dec 2007 11:44 AM
  • Comments 4

unable to start debugging on the web server

(Unable to start debugging on the web server. An error occurred that usually indicates a corrupt installation. If the problem persists, repair Visual Studio installation via 'Add or Remove Programs' in Control Panel)

 

I saw this happening on a Vista x64 while trying to debug an ASP.NET application and needless to say (smile_sad), repairing Visual Studio does not help.

This is a misleading error message which might appear when you try to debug an ASP.NET application on a 64 bit OS and you configured your application pool to run a 32 bit worker process; I know it will be changed to a more meaningful message, but I'm not sure about the timeframe (I can't repro so I'm not able to check how Visual Studio 2008 behaves).

What to do then? Check the advanced settings for your application pool and set "Enable 32-bit applications" to "False"

advanced settings 

By the way, I was this error in conjunction with this one so pay attention if you're hitting one of the two...

 

Carlo

Quote of the Day:
Sincerity is the highest compliment you can pay.
--Ralph Waldo Emerson

  • 4 Comments
ASP.NET, IIS, Visual Studio
Leave a Comment
  • Please add 4 and 1 and type the answer here:
  • Post
Comments
  • Chetan Garude
    15 Jul 2009 1:40 PM

    I'm getting a similar error for a Windows Application - any pointers what to look for? Thanks.

  • krzyszp
    22 Nov 2011 8:35 AM

    Similar problem in vs2008...

    No fix for this up to today???

  • Carlo Cardella
    15 Dec 2011 2:21 AM

    Well, debugging a 64 bit process from a 32 bit one simply cannot be done, there is not much to fix if not, maybe, a more clear error message

  • Santosh
    20 Dec 2011 2:47 AM

    For Windows application, inappropriate debugger type (for example debugger type set to script) might cause this problem when trying debug the application. The problem gets resolved by setting debugger type to Auto.

    Debugger type can be changed through Project properties -> Configuration properties -> Debugging

Page 1 of 1 (4 items)
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.402.223