Script Mappings Are Not Removed from the Registry after Migration
Article ID: 193169
Article Last Modified on 6/23/2005
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Internet Information Server 4.0
This article was previously published under Q193169
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
Script mappings are not removed from the registry after they have been
migrated to the Internet Information Server (IIS) 4.0 metabase.
RESOLUTION
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 the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in Internet Information
Server 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 the
metabase. When the W3svc service is started in IIS 4.0, it checks the
registry for settings used by IIS 4.0, and then migrates them to the
metabase, which causes duplicate entries in the script map list.
Additional query words: multiple long extra migrating import copy transfer akz
Keywords: kbbug kbfix KB193169