| Groups | Blog | Home |
visual studio .net debugging : Problem - Debugger in VS.NET 03 has stopped working!!!!
fix for. I can no longer debug an application I have developed through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the task manager I see the executable that I am trying to debug, it has only consumed some small number of bytes and nothing else id happening. Anyone have any idea what is going on and how to fix it?? The only clue I had was that I installed MS Office Developer after which I started to run into problems. I have however uninstalled Office Developer and reinstalled VS.NET but I have hit this problem time and time again. Anyone from the VS group at Microsoft??? Frustrated!!
I posted this a little while back and didn't get a response. I
thought I had fixed it by reinstalling the .NET framework, but I ran into the problem again. So with the help of MSConfig and ump-teen reboots I found the problem!! The problem has to do with the ZoneAlarm firewall as detailed in Microsoft Knowledge Base Article - 321434. This article refers to installation of Visual Studio but it appears the same fix works to solve this problem. Details in the article. Cheers [quoted text, click to view] cam_banks@hotmail.com (Cameron) wrote in message news:<2cc8a69e.0401171435.2d5db906@posting.google.com>...
> I have run into a problem that I can find explanation to nor find a > fix for. I can no longer debug an application I have developed > through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the > task manager I see the executable that I am trying to debug, it has > only consumed some small number of bytes and nothing else id > happening. > > Anyone have any idea what is going on and how to fix it?? The only > clue I had was that I installed MS Office Developer after which I > started to run into problems. I have however uninstalled Office > Developer and reinstalled VS.NET but I have hit this problem time and > time again. Anyone from the VS group at Microsoft??? > > Frustrated!! >
Try this:
Find the mdm.exe on your machine (somewhere under Common Files). In that same directory you should see a zero-length file whose name starts with mdm (but whose exact name I have forgotten). Move that file somewhere else (eg to Temp) Reboot the machine. Assuming this fixed it, delete the file you moved to Temp. Sometimes an Office Developer install can hork a VS2003 in this way. -------------------- [quoted text, click to view] >From: cam_banks@hotmail.com (Cameron) microsoft.public.vsnet.debugging,microsoft.public.vsnet.general,microsoft.pu>Newsgroups: blic.vsnet.ide [quoted text, click to view] >Subject: Re: Problem - Debugger in VS.NET 03 has stopped working!!!! cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix>Date: 28 Jan 2004 20:18:50 -0800 >Organization: http://groups.google.com >Lines: 31 >Message-ID: <2cc8a69e.0401282018.3deae1f2@posting.google.com> >References: <2cc8a69e.0401171435.2d5db906@posting.google.com> >NNTP-Posting-Host: 66.31.54.233 >Content-Type: text/plain; charset=ISO-8859-1 >Content-Transfer-Encoding: 8bit >X-Trace: posting.google.com 1075349930 28923 127.0.0.1 (29 Jan 2004 04:18:50 GMT) >X-Complaints-To: groups-abuse@google.com >NNTP-Posting-Date: Thu, 29 Jan 2004 04:18:50 +0000 (UTC) >Path: ..com!newsfeed.cwix.com!news.maxwell.syr.edu!postnews1.google.com!not-for-mai l [quoted text, click to view] >Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.general:16304 microsoft.public.vsnet.ide:10540 microsoft.public.vsnet.debugging:4821 >X-Tomcat-NG: microsoft.public.vsnet.debugging > >I posted this a little while back and didn't get a response. I >thought I had fixed it by reinstalling the .NET framework, but I ran >into the problem again. So with the help of MSConfig and ump-teen >reboots I found the problem!! > >The problem has to do with the ZoneAlarm firewall as detailed in >Microsoft Knowledge Base Article - 321434. This article refers to >installation of Visual Studio but it appears the same fix works to >solve this problem. > >Details in the article. > >Cheers > >cam_banks@hotmail.com (Cameron) wrote in message news:<2cc8a69e.0401171435.2d5db906@posting.google.com>... >> I have run into a problem that I can find explanation to nor find a >> fix for. I can no longer debug an application I have developed >> through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the >> task manager I see the executable that I am trying to debug, it has >> only consumed some small number of bytes and nothing else id >> happening. >> >> Anyone have any idea what is going on and how to fix it?? The only >> clue I had was that I installed MS Office Developer after which I >> started to run into problems. I have however uninstalled Office >> Developer and reinstalled VS.NET but I have hit this problem time and >> time again. Anyone from the VS group at Microsoft??? >> >> Frustrated!! >> >> Cameron > -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
Try restarting the World Wide Web publishing Service. That did it for me.
I just did a fresh install of WinXP PRo and the simplest project stopped running from the IDE, but would run from the EXE itself. It seems that Norton Personel Firewall has something to do with it, but I havent found a sure way to fix it. A Micsoft KB article (321434) talks about a registry hack when ZoneAlarm is the culprit, but doesn't have a similar one for Norton. Symantec's web site is useless as usual for anything but "Where is my power switch" questions. I suspect I installed NPW prior to NSNET this time, whereas VSNET was already installed the first time. If anyone can post a permanent fix, I'm sure many would appreciate it. [quoted text, click to view] "Cameron" <cam_banks@hotmail.com> wrote in message news:2cc8a69e.0401171435.2d5db906@posting.google.com... > I have run into a problem that I can find explanation to nor find a > fix for. I can no longer debug an application I have developed > through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the > task manager I see the executable that I am trying to debug, it has > only consumed some small number of bytes and nothing else id > happening. > > Anyone have any idea what is going on and how to fix it?? The only > clue I had was that I installed MS Office Developer after which I > started to run into problems. I have however uninstalled Office > Developer and reinstalled VS.NET but I have hit this problem time and > time again. Anyone from the VS group at Microsoft??? > > Frustrated!! > > Cameron
I've had the same problem. I have not installed the MS office developer, so
I'm not sure that's the cause. I've also been having problems using WindowsUpdate. None of the updates install correctly. The error messages aren't very helpful. All this started after installing Norton Internet Security. The worst part is, I have been unable to repair or uninstall VS.NET. The VS installer spends thirty minutes generating install scripts before finally failing with a message stating the Visual Studio Setup cannot continue while the Visual Studio Setup program is running. The only solutions I've seen on the newsgroups is to reinstall WinXP and VS.NET... Not a great choice. Equally Frustrated, Eric [quoted text, click to view] "Cameron" <cam_banks@hotmail.com> wrote in message news:2cc8a69e.0401171435.2d5db906@posting.google.com... > I have run into a problem that I can find explanation to nor find a > fix for. I can no longer debug an application I have developed > through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the > task manager I see the executable that I am trying to debug, it has > only consumed some small number of bytes and nothing else id > happening. > > Anyone have any idea what is going on and how to fix it?? The only > clue I had was that I installed MS Office Developer after which I > started to run into problems. I have however uninstalled Office > Developer and reinstalled VS.NET but I have hit this problem time and > time again. Anyone from the VS group at Microsoft??? > > Frustrated!! > > Cameron
OK, here's a possible solution for you. Script blockers don't like Visual
Studio (or is that the reverse?). Script blockers will cause problems with the installation and will prevent debugging. When you start a debug, the program will compile, but will only load to about 56 bytes before locking up the IDE. I had Norton Internet Security installed. Interestingly, the problem persisted when I disabled Script Blocking and restarted the PC with no portion of Norton running. I was only able to resolve the problem by uninstalling Norton. Good Luck, Eric [quoted text, click to view] "Cameron" <cam_banks@hotmail.com> wrote in message news:2cc8a69e.0401171435.2d5db906@posting.google.com... > I have run into a problem that I can find explanation to nor find a > fix for. I can no longer debug an application I have developed > through the VS.NET 03 IDE. I hit debug and the IDE locks up. In the > task manager I see the executable that I am trying to debug, it has > only consumed some small number of bytes and nothing else id > happening. > > Anyone have any idea what is going on and how to fix it?? The only > clue I had was that I installed MS Office Developer after which I > started to run into problems. I have however uninstalled Office > Developer and reinstalled VS.NET but I have hit this problem time and > time again. Anyone from the VS group at Microsoft??? > > Frustrated!! > > Cameron
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |