Article ID: 324292 - View products that this article applies to.
This article was previously published under Q324292
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft has learned that when you install Security Bulletin MS02-026, if Microsoft Visual Studio .NET is open, the installation may not be successful if the files that are to be replaced are locked. This problem can occur under the following circumstances:
(https://support.microsoft.com/kb/322289/ )MS02-026: Unchecked buffer in ASP.NET worker process (English)
(https://support.microsoft.com/kb/322299/ )MS02-026: Unchecked buffer in ASP.NET worker process (Simplified Chinese)
(https://support.microsoft.com/kb/322300/ )MS02-026: Unchecked buffer in ASP.NET worker process (Traditional Chinese)
(https://support.microsoft.com/kb/322301/ )MS02-026: Unchecked buffer in ASP.NET worker process (Korean)
The following files are copied to the %WINDIR%\Microsoft.NET\Framework\v1.0.3705\ASP.NETClientFiles\ folder:
Version File Name ------------------------------- 1.0.3705.272 Aspnet_isapi.dll 1.0.3705.272 Aspnet_wp.exe 1.0.3705.272 Aspnet_regiis.exe -- Aspnet_perf.ini -- Aspnet_perf2.ini 1.0.3705.272 System.Web.dll
Additionally, System.Web.dll is installed to the global assembly cache (GAC). If files are locked during installation, the updated version of System.Web.dll does not install to the global assembly cache.
Version File Name ----------------------- -- SmartNavIE5.js -- SmartNav.js
To check the version of the assembly in the global assembly cache, follow these steps:
How to recover from a failed installationIf Setup was unsuccessful, ASP.NET pages will not run, and an error page will be returned. The error page may indicate that the server cannot be found and that a DNS error may have occurred. When you try to debug a project in Visual Studio .NET, you may receive the following error message:
To recover from a failed installation, follow these steps:
Error while trying to run project: Unable to start debugging on the web server. Would you like to disable future attempts to debug ASP.NET pages for this project?