XFOR: Virtual Server Is No Longer Viewable Through MMC

This article was previously published under Q193921
This article has been archived. It is offered "as is" and will no longer be updated.
After you upgrade to Windows NT 4.0 Service Pack 4 (SP4) and view theOperators tab on an SMTP, IMAP, or POP3 virtual server, the virtual serveris no longer viewable through Microsoft Management Console (MMC), even bythe administrator.
A change in the Internet Information Server (IIS) ADSI provider for themetabase causes this problem. When the SMTP, IMAP, or POP3 snap-ins savethe metabase ACL for the Operators tab, a bad ACL (that does not includethe administrator on the local computer) is written to the metabase. Noerror is returned by the ADSI provider, therefore the snap-ins commit thechange to the 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

NOTE: The fix that is needed to resolve this problem if you are runningMicrosoft Commercial Internet System 2.0 on a DEC Alpha computer is missingfrom the Windows NT 4.0 Service Pack 4 CD-ROM. For information about how toobtain the fix, please see the following article in the Microsoft KnowledgeBase:
197514Msmtpsnp.dll File Is Missing From Windows NT 4.0 SP4 CD-ROM
To work around this problem, restore the metabase.
Microsoft has confirmed this to be a problem in Microsoft CommercialInternet System version 2.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.
mcis hotfix hot fix qfe quick engineering patch

Article ID: 193921 - Last Review: 10/10/2013 22:27:00 - Revision: 3.1

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Commercial Internet System 2.0

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB193921
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)