ASP Refresh Problems with IIS and a Network Appliance File Server
Article ID: 250925 - View products that this article applies to.
This article was previously published under Q250925
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
This article describes possible problems that are related to using a Network Appliance file server in a mixed environment with Windows NT Server. This article refers to Internet Information Server (IIS) 4.0 as the affected software that is running on Microsoft Windows NT, but this information can apply to any Win32-based program that connects to a NetApp file server.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
When a Windows NT-based client computer connects to a NetApp file server, the client may receive the following error message:
Note that this is what is returned from the client redirector to the Windows-based program. The error message that is displayed by the client may and probably will be different.
Error 1721: Not enough resources are available to complete this operation.
This is most likely to occur with Directory Change notifications when connecting to a UNC address. The problem is that the NetApp file server negotiates low LongTermEntries thresholds with the Windows NT-based client; when the client reaches this threshold, the Windows NT redirector returns an error to the Windows-based program, stating that it is unable to post change notifications to the server.
Although this may appear to be a Windows NT issue, the problem is with the file server. When this issue occurs, it looks as if the client software (IIS) is not updating content, but in reality the server negotiated the limit; the client only enforces this limit by returning an error to the Windows-based program.
A fix for this issue is available to Network Appliance customers. The fix is contained in patch releases 5.3.4R2P1 and 5.3.4R2P2. The fix will be in all subsequent patch releases for 5.3.4 and in subsequent maintenance releases as well. The patch releases are available from the Network Appliance Web site.
As a troubleshooting step and/or workaround, disable ASP and static file caching.
To disable ASP file caching, perform the following steps:
To obtain the Network Appliance patch that is referred to in this article, visit the Network Appliance Web site for more information:
http://www.netapp.comMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Article ID: 250925 - Last Review: November 1, 2006 - Revision: 3.2