FIX: Error message when you try to run an ASP.NET 2.0 Web application that includes Web services: "The file <FilePath> does not exist"

When you try to run a Microsoft ASP.NET 2.0 Web application that includes Web services, you continuously receive the following error message:Note In this error message, <FilePath> is placeholder for the path of the .aspx file.

You continuously receive this error message until the Microsoft Internet Information Services (IIS) application pool that hosts the ASP.NET 2.0 Web application is recycled.

This problem may occur when you run the ASP.NET 2.0 Web application in a high-load environment.

This problem occurs because the code that generates the Web Services Description Language (WSDL) file may unregister any VirtualPathProviders class that is used by the ASP.NET 2.0 Web application. This problem may occur if more than one WSDL help request is in process. If the VirtualPathProviders classes are unregistered, any content that resides on the virtual path may be inaccessible.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have ASP.NET 2.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the hotfixes that are described in the following Microsoft Knowledge Base articles:

File information

The English version of this hotfix 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 item in Control Panel.

The Microsoft .NET Framework 2.0, x86-based versions

The Microsoft .NET Framework 2.0, x64-based versions

The Microsoft .NET Framework 2.0, Itanium-based versions

To work around this problem, recycle the IIS application pool that hosts the ASP.NET 2.0 Web application to register the VirtualPathProviders classes again. To do this, follow these steps:

1. Click Start, click Run, type inetmgr, and then click OK.
2. Expand <Server Name>, and then expand Application Pools.
   
   Note <Server Name> is a placeholder for the name of the computer on which you want to recycle the IIS application pool.
3. Right-click the IIS application pool that you want to recycle, and then click Recycle.
4. Right-click <Server Name>.
5. Click All Tasks, and then click Restart IIS.
6. Click OK.

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

This hotfix becomes effective the next time that the IIS application pool is recycled.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: