.net framework 1.1 sp1 crash
in [ASP .NET]
|
From: STech on 21 Feb 2005 19:11 When installing the .net framework 1.1 service pack 1 on my webserver, the installer crashes with the following error message: --------------------------- SLA.tmp - Common Language Runtime Debugging Services --------------------------- Application has generated an exception that could not be handled. Process id=0x1090 (4240), Thread id=0xecc (3788). Click OK to terminate the application. Click CANCEL to debug the application. --------------------------- OK Cancel --------------------------- The log files contains this: move C:\WINNT\Microsoft.NET\Framework\v1.1.4322\SHADOW1224\_aspnet_isapi.dll C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll Process returned: -532459699 Please advise. Thanks.
From: Steven Cheng[MSFT] on 22 Feb 2005 02:48 Hi Stech, Thanks for your posting. Regarding on the problem you described, are you installing the sp through windows update ? What's your server's enviorment, .net runtime version, is there VS.NET installed on it? Also, before you istalling the .net framework sp, is the IIS or asp.net workprocess completely turned off? I suggest that you try restart the server and turn off all the exsiting running asp.net processes (or other asp.net process) and try installing the sp again. Thanks, Steven Cheng Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.)
From: STech on 22 Feb 2005 15:15 I am trying to re-run SP1 because asp_wp.exe might have a memory leak. It takes up more and more memory and eventually the web server has to be restarted. We have the *same* applications running on a windows 2003 server without any problems. > What's your server's enviorment, .net runtime version, is there VS.NET > installed on it? Windows 2003, (version 1.1.4322.573), No VS.NET This server used to be running NT 4.0 -> Upgraded to Win 2000 -> Upgraded to Win 2003 I am trying to run SP1 through the exe - NDP1.1sp1-KB867460-X86.exe Thanks. "Steven Cheng[MSFT]" wrote:> What's your server's enviorment, .net runtime version, is there VS.NET > installed on it? > Hi Stech, > > Thanks for your posting. Regarding on the problem you described, are you > installing the sp through windows update ? > > > Also, before you istalling the .net framework sp, is the IIS or asp.net > workprocess completely turned off? > I suggest that you try restart the server and turn off all the exsiting > running asp.net processes (or other asp.net process) and try installing the > sp again. > > Thanks, > > Steven Cheng > Microsoft Online Support > > Get Secure! www.microsoft.com/security > (This posting is provided "AS IS", with no warranties, and confers no > rights.) > >
From: Steven Cheng[MSFT] on 23 Feb 2005 01:01
Hi Stech, Thanks for your followup. Seems something incorrect with the install package. I think we can try the following steps to manually install it (unpack the sp install file): ======================================== 1. Close all unnecessary application. If we have protection programs (e.g. firewall or antivirus) running, please disable them temporarily. 2. Clean the ýýTempýý folder: Open the menu ýýStartýý | ýýRunýý and run ýý%temp%ýý (without quotation marks). This will bring us to the Temp folder. Letýýs delete as many files as possible in the Temp folder. Since some of the files may be in use, it is normal that we cannot remove some of them. 3. Turn on Windows Installer verbose log option for diagnostic purpose. You can extract the file attached and import the .REG file into the registry by double-clicking it. 4. Download the ýýNDP1.1sp1-KB867460-X86.exeýý again. Letýýs save it as ý ýC:\NDP1.1sp1-KB886903-X86.exeýý: 5. Open the menu ýýStartýý | ýýRunýý and run the following command to extract the file manually: C:\NDP1.1sp1-KB867460-X86.exe /xp A file named ýýM867460.mspýý will be extracted to the folder we specify. The speed can be quite slow. Please be patient. If we get the ýýUnhandled Exceptionýý error at this point, it is most likely that your .Net Framework has been corrupted. I suggest that you try reinstalling the .net frameowork and the sp. ======================================= HTH. Thanks, Steven Cheng Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.) |