XFOR: SMTP Services Do Not Start Automatically After One Is Stopped

This article was previously published under Q193686
This article has been archived. It is offered "as is" and will no longer be updated.
When you start multiple instances of the Simple Mail Transfer Protocol(SMTP) service, use the Microsoft Management Console (MMC) to stop oneinstance, and then stop Smtpsvc.dll from a command prompt, all otherinstances of the SMTP service are stopped. If you then start Smtpsvc.dllfrom a command prompt, the instance that you stopped using the MMC and anyother instances that were initially started after that instance, do notstart automatically. The instance that you stopped using the MMC does notnormally start automatically, but all other instances normally do.
When you stop an instance of the SMTP service, the service isautomatically configured so that it does not start automatically when youstart Smtpsvc.dll. The problem described in this article occurs becauseSmtpsvc.dll does not automatically start any instances of the SMTP serviceafter it encounters one instance that is configured in this manner.
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 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.
XFOR mcis

Article ID: 193686 - Last Review: 10/10/2013 22:25:02 - Revision: 4.1

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

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