 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Setup / January 2005.net 1.1 sp1 install may have broken vsnet debugging
I installed .net framework sp 1 update from the microsoft update site. There seems to be no way to roll back to the previous version. After installing this my vs.net debugging is broken for web apps. I can't use the .net repair tool included with the vs.net cd since it can't repair sp 1. None of the suggested debugging fixes are working. Any suggestions? what have you tried, I just upgraded yesterday and now I cannot debug either. I get the tooltip = "the breakpoint will not currently be hit. No symbols have been loaded for this document." Brian > I installed .net framework sp 1 update from the microsoft update site. > There seems to be no way to roll back to the previous version. After [quoted text clipped - 3 lines] > > Any suggestions? The help page is ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/vsdebug/html/vxtbsHTTPServerErrors.htm Nothing on that page is either relevant or effective. Debugging was working, my project was set up perfectly. Then after sp1 I couldn't debug. It's still not fixed, I have no idea what's wrong, or how to fix. I've tried looking at the user accounts for the web site and application pooling, but am flying blind. The vs.net debugger has been a problem from day one -- it's very twitchy and it's broken before, but not this badly. The main problem with this product is that you have to run in administrator mode to use the debugger -- that plus no support from MS. > what have you tried, I just upgraded yesterday and now I cannot debug > either. [quoted text clipped - 11 lines] >> >>Any suggestions? Hello Paul. Which operating system are you running .NET Framework 1.1 on? If this is Windows Server 2003 then this response will not apply to you. If you are running on any 32-bit platform other than Windows Server 2003 however, then try the following suggestions. First, you can repair .NET Framework 1.1 (including SP1) from the command line using the following command. Do this from somewhere with dotnetfx.exe (the .NET Framework 1.1 installer, not the SP1 installer) in your path. c:\> dotnetfx.exe /t:%tmp% /c:"msiexec.exe /fvecms %tmp%\netfx.msi" You also asked how to rollback to the previous version. You cannot explicitly uninstall .NET Framework 1.1 SP1, however you can uninstall and re-install .NET Framework 1.1 which will effectively remove .NET Framework 1.1 SP1. This will also remove any .NET Framework 1.1 hotfixes which you have installed, so you will need to re-install these after re-installing .NET Framework 1.1 (see below). You can find the .NET Framework 1.1 installer (dotnetfx.exe) here: http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842- 8157-034d1e7cf3a3&displaylang=en You can determine which .NET Framework 1.1 hotfixes you have installed (if any) by checking Add/Remove Programs prior to uninstalling .NET Framework 1.1. Any Framework 1.1 hotfixes should look like this: "Microsoft .NET Framework 1.1 Hotfix (KBxxxxxx)". I hope these suggestions help! Best wishes. -Blair. -------------------- > Date: Wed, 29 Sep 2004 13:00:25 -0600 > Subject: .net 1.1 sp1 install may have broken vsnet debugging [quoted text clipped - 6 lines] > > Any suggestions?  SignatureThis 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. I still have not been able to fix this and it may not be related to the .net sp 1 software. No projects can be debugged using the debug run, but I can debug by attaching to a process. This is a pain and I want my debugger back. I reinstalled asp.net 1.1, and did a visual studio repair install. No help. I have checked all the default web site permissions and users, and the account for application pooling. Nothing I try seems to work, including the original settings that were working. The debugger was working fine until sometime after the sp1 install and a few MS security updates. My next tests will be to start removing the security updates one by one. I don't have an account on the local machine, but am an admin on active directory. My account is in the local debugger users group, none of this was changed. One day the debugger was working, the next it wasn't. There is no information provided by the error message, and all the usual fixes have been tried. I am going to ask the owner of the system to consume a MS support incident pretty soon, otherwise it's reformat the hard drive time. > Hello Paul. > > Which operating system are you running .NET Framework 1.1 on? w2k3 If this is > Windows Server 2003 then this response will not apply to you. If you are > running on any 32-bit platform other than Windows Server 2003 however, then [quoted text clipped - 11 lines] > have installed, so you will need to re-install these after re-installing > NET Framework 1.1 (see below). This is what I did. I uninstalled asp.net from the control panel add remove windows components. Then reinstalled asp.net. This did not fix the debugger. > You can find the .NET Framework 1.1 installer (dotnetfx.exe) here: > http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842- [quoted text clipped - 22 lines] >> >>Any suggestions? Hi Paul. Sorry to hear about your continued troubles debugging applications under Visual Studio .NET. Unfortunately, I do not think that I am in any position to help you troubleshoot your debugger, but you did also preface this thread with concerns that the problem may have been introduced by .NET Framework 1.1 Service Pack 1 and that you were unable to rollback to the non-SP1 version. This is the area where I may be able to help. My previous post assumed that you were not running on Windows Server 2003. Now that I know that you are, in fact, running on Windows Server 2003, I may be able to offer a bit more appropriate suggestions. First off, you can uninstall .NET Framework 1.1 SP1 from Add/Remove Programs on Windows Server 2003. If I were a support engineer and you told me that your problems started after installing SP1, that would be the first thing I would try. Unfortunately, the name for SP1 in Add/Remove Programs is not intuitive, but it should be present. .NET Framework 1.1 SP1 is listed as "Windows Server 2003 Hotfix - KB 867460" in Add/Remove Programs on Windows Server 2003. If uninstalling SP1 does not fix your problem then I would strongly recommend re-installing it. A number of important fixes are contained in SP1 and we definitely recommend you having it. You can download .NET Framework 1.1 Service Pack 1 for Windows Server 2003 from the following download site. It should also be offered to your system on Windows Update if you have uninstalled and not yet re-installed it. http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7edef7-2cb7-4864- 8623-a1038563df23&DisplayLang=en Also, here is the list of bugs that are fixed in .NET Framework 1.1 SP1: http://support.microsoft.com/?kbid=867460 Again, hope this helps! I always hate it when machines get flattened to fix applications; with any luck, we'll find a way to get you back in shape! Take care. -Blair. -------------------- > Date: Tue, 12 Oct 2004 23:48:02 -0600 > Subject: Re: .net 1.1 sp1 install may have broken vsnet debugging [quoted text clipped - 49 lines] > > > You can find the .NET Framework 1.1 installer (dotnetfx.exe) here: http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842- > > 8157-034d1e7cf3a3&displaylang=en > > [quoted text clipped - 20 lines] > >> > >>Any suggestions? SignatureThis 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. Unfortunately, the name for SP1 in Add/Remove Programs > is not intuitive, but it should be present. .NET Framework 1.1 SP1 is > listed as "Windows Server 2003 Hotfix - KB 867460" in Add/Remove Programs > on Windows Server 2003. @#*$*#&^@! -- The first thing I did was look for sp 1 in the add/remove, not there -- which I thought was a little unfriendly. I never thought to examine each hotfix. I uninstalled 1.1 original then reinstalled, not the same thing. Thanks for answering, no one in the vsnet.debugging group has. I'm not the only one having a problem. Paul Wilson has a blog entry on this. http://weblogs.asp.net/pwilson/archive/2004/09/22/232894.aspx > Unfortunately, the name for SP1 in Add/Remove Programs > is not intuitive, but it should be present. .NET Framework 1.1 SP1 is > listed as "Windows Server 2003 Hotfix - KB 867460" in Add/Remove > Programs on Windows Server 2003. @#*$*#&^@! -- The first thing I did was look for sp 1 in the add/remove, not there -- which I thought was a little unfriendly. I never thought to examine each hotfix. I uninstalled 1.1 original then reinstalled, not the same thing. Thanks for answering, no one in the vsnet.debugging group has. I'm not the only one having a problem. Paul Wilson has a blog entry on this. http://weblogs.asp.net/pwilson/archive/2004/09/22/232894.aspx He also has another earlier entry that probably explains WHY MY WEB APP BROKE! > First, you can repair .NET Framework 1.1 (including SP1) from the command > line using the following command. Do this from somewhere with dotnetfx.exe > (the .NET Framework 1.1 installer, not the SP1 installer) in your path. > c:\> dotnetfx.exe /t:%tmp% /c:"msiexec.exe /fvecms %tmp%\netfx.msi" This is not my result! Using dotnetfx.exe in the 1.1 install, I get an error popup that says this version of the .net framework is part of the operating system and cannot be installed or uninstalled ... use windows update... etc. I recently had a similar thing happen to me. See if any of this applies.... I had built a class library with .NET 1.1. I installed that class library into the GAC. Life is great. I upgraded to .NET 1.1 SP1. I found a need to make modifications to the class library that was already installed in the GAC. However, after making modifications, I couldn't get the debug symbols to load for the project. Turns out that it was because my AssemblyInfo file was specifying a version #. Fusion was picking up the GAC version, not the project version - and there were no debug files to load with the GAC version. I changed my AssemblyInfo to a different version than what was already installed in the GAC and I was back in business. Sound like it might apply to you? If not, try taking advantage of the Debug window called "modules" (Debug -> Windows -> Modules). With it, you can view what assemblies are currently loaded and explicity load (or reload) debug symbols for assemblies that don't already have them loaded. Ron. > I installed .net framework sp 1 update from the microsoft update site. > There seems to be no way to roll back to the previous version. After [quoted text clipped - 3 lines] > > Any suggestions? I don't think this applies. In my case even a new default web project with a blank form can't be run directly with the debugger. Thanks. > I recently had a similar thing happen to me. See if any of this applies.... > [quoted text clipped - 24 lines] >> >>Any suggestions? Is this the same problem as the topic ".NET 1.1 service pack 1 debug symbols", i.e. you need to download the latest symbols? > I don't think this applies. In my case even a new default web project > with a blank form can't be run directly with the debugger. Thanks. [quoted text clipped - 27 lines] > >> > >>Any suggestions? Something that worked for me. 1. iisreset 2. Consider clearing out the temporary files found in C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files 3. Delete C:\Documents and Settings\<your login>\VSWebCache\<your project> 4. Open VS .NET again Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.