Script Mappings Are Not Removed from the Registry after Migration

This article was previously published under Q193169
This article has been archived. It is offered "as is" and will no longer be updated.
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:
Script mappings are not removed from the registry after they have beenmigrated to the Internet Information Server (IIS) 4.0 metabase.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Microsoft has confirmed this to be a problem in Internet InformationServer version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
More information
Previous versions of IIS use the Windows registry rather than themetabase. When the W3svc service is started in IIS 4.0, it checks theregistry for settings used by IIS 4.0, and then migrates them to themetabase, which causes duplicate entries in the script map list.
multiple long extra migrating import copy transfer akz

Article ID: 193169 - Last Review: 10/26/2013 12:05:00 - Revision: 5.0

  • kbnosurvey kbarchive kbbug kbfix KB193169