Article ID: 165335
Article Last Modified on 6/23/2005
APPLIES TO
- Microsoft Internet Information Server 3.0
- Microsoft Active Server Pages 4.0
This article was previously published under Q165335
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
SYMPTOMS
If you are running Active Server Pages version 1.0b on Microsoft Internet Information Server (IIS) version 3.0, and you are storing objects in the Application scope, you may experience performance problems and increased memory usage by IIS.
CAUSE
These performance problems are caused by a memory leak in the Asp.dll file when you give objects an application scope. You can confirm this resource leak with Performance Monitor.
RESOLUTION
A hotfix has been posted to the following Internet location. You can
download the self-extracting files from the following service:
- Internet (anonymous FTP)
ftp ftp.microsoft.com
Change to the bussys/winnt/winnt-public/fixes/usa/
nt40/hotfixes-postsp3/asp-fix/ folder.
Get Readme.1st (for instructions on downloading and installing the hotfix)
-or-
- Use the following full URL on your client browser:
FTP://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/
nt40/hotfixes-postSP3/asp-fix/readme.1st
NOTE: This fix is only for Active Server Pages (ASP) version 1.0b. ASP 1.0b is the double-byte
character enabled version of ASP that is now available via web download or in the Microsoft
Windows NT Service Pack 3. (The version number on the Asp.dll file in 1.0b is: 1.15.14.0)
REFERENCES
For additional information, please see the following article in the
Microsoft Knowledge Base:
150934
: How to Create a Performance Monitor Log for NT Troubleshooting
STATUS
Microsoft has confirmed this to be a problem in Microsoft Active Server
Pages version 1.0b.
A supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this fix.
Contact Microsoft Technical Support for more information.
Keywords: kberrmsg kbusage KB165335