FIX: Your ASP.NET request runs, but no ASPNET_WP.EXE worker process appears in Task Manager when you use Microsoft .NET Framework 1.0 SP3 (892088)
The information in this article applies to:
- Microsoft .NET Framework 1.0 SP3
SYMPTOMSIf your Machine.config file contains syntax errors in the proxy bypass list, the wrong process model may be used to run ASP.NET requests when you use the Microsoft .NET Framework 1.0 Service Pack 3 (SP3). For example, if you add the following code in the <system.net> section of your Machine.config file, ASP.NET requests run, but no ASPNET_WP.EXE worker process appears in Task Manager.
<defaultProxy>
<proxy usesystemdefault="false" proxyaddress="intranetproxy" bypassonlocal="true" />
<bypasslist>
<add address=".*\.corp\.microsoft\.com\:.*" />
</bypasslist>
</defaultProxy> CAUSEThis problem occurs when you use the Microsoft .NET Framework 1.0 SP3. This problem occurs because the .NET Framework 1.0 SP3 does not include an update for this problem. Note This problem was fixed in the Microsoft .NET Framework 1.0 Service Pack 2 (SP2). For example, you may experience the symptoms that are described in the "Symptoms" section when the following conditions are true: - You apply the software update that is described in Microsoft Knowledge Base (KB) article 840870 on your computer that is running the .NET Framework 1.0 SP2.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
840870
FIX: ASP.NET requests run, but no ASPNET_WP.EXE worker process appears in Task Manager
- Then, you update your computer by installing Microsoft .NET Framework 1.0 SP3.
RESOLUTIONSoftware update informationA supported software update is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This software update may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.0 service pack that contains this software update. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the software update. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesThe Microsoft .NET Framework 1.0 SP3 Restart requirementAfter you apply this software update, restart your computer if you are prompted to do this. Software update replacement informationThis software update does not replace any other software updates. File information
The English version of this software update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
------------------------------------------------------------
30-Dec-2004 19:21 1.0.3705.6030 200,704 Aspnet_isapi.dll
30-Dec-2004 19:21 1.0.3705.6030 32,768 Aspnet_wp.exe STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 6/5/2006 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbfix kbNetFrame100preSP3fix KB892088 kbAudITPRO kbAudDeveloper |
---|
|