Microsoft Knowledge Base Email Alertz

(892088) - Fixes a problem where no ASPNET_WP.EXE worker process appears in Task Manager, but your ASP.NET requests run when you use the .NET Framework 1.0 Service Pack 3.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 892088 - Last Review: December 3, 2007 - Revision: 1.3

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

On This Page

SYMPTOMS

If 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>

CAUSE

This 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  (http://kbalertz.com/Feedback.aspx?kbNumber=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.

RESOLUTION

Software update information

A 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:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)
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.

Prerequisites

The Microsoft .NET Framework 1.0 SP3

Restart requirement

After you apply this software update, restart your computer if you are prompted to do this.

Software update replacement information

This 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

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Additionally, if you try to apply the software update that is described in KB article 840870 on your computer that is running the .NET Framework 1.0 SP3, you receive the following error message. Also, the software update is not applied.
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct patch upgrade.
Note You also receive this error message if you try to apply the software update that is described in KB article 840870 on your computer that is running a version of the .NET Framework 1.0 that is earlier than the .NET Framework 1.0 SP2.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft .NET Framework 1.0 Service Pack 3
Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbnetframe100presp3fix KB892088
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate