Microsoft KB Archive/249516

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:14, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


XFOR: Service Restart Fails on IMAP4 and POP3

Article ID: 249516

Article Last Modified on 2/22/2007



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition



This article was previously published under Q249516


SYMPTOMS

When you restart the Microsoft Exchange 2000 Server IMAP4 or POP3 services, you may occasionally see the following error message:

Could not start the Microsoft Exchange IMAP4\POP3 Service on Local Computer
Error 1056: An instance of the service is already running.

You may also see the following errors in the Event Viewer application log:

Event Type: Information
Event Source: MSExchange IMAP4\POP3 Interface
Event Category: General
Event ID: 11600
Description:
Attempting to start the Microsoft Exchange IMAP4\POP3 Service


Event Type: Error
Event Source: MSExchange IMAP4\POP3 Interface
Event Category: General
Event ID: 11604
Description:
Microsoft Exchange IMAP4\POP3 Service is already running.


Event Type: Error
Event Source: MSExchange IMAP4\POP3 Interface
Event Category: General
Event ID: 13000
Description:
An error occurred while starting the Microsoft Exchange IMAP4 Service: the call to DwInitializeService() failed with error 0x420.


Event Type: Information
Event Source: MSExchange IMAP4\POP3 Interface
Event Category: General
Event ID: 11602
Description:
Attempting to stop the Microsoft Exchange IMAP4\POP3 Service


Event Type: Error
Event Source: MSExchange IMAP4\POP3 Interface
Event Category: General
Event ID: 13000
Description:
An error occurred while starting the Microsoft Exchange IMAP4\POP3 Service: the call to IIS_SERVICE::StartServiceOperation() failed with error 0x420.


WORKAROUND

Instead of using the Restart command, click the Stop command to stop the service. Then click Start to start the service.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.


Additional query words: exch2kp2w

Keywords: kbbug kberrmsg kbpending KB249516