Microsoft KB Archive/285116

= Exchange Store Does Not Start: Errors 7024, 1026, 9542, and 5000 =

Article ID: 285116

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q285116



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When you start Windows with Exchange installed, you may be notified by Service Control Manager with an error message similar to the following error message:

At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

The Exchange Microsoft Exchange Information Store will not start. As a result, all services that depend on Information Store service will not be able to start.

You may find the following error events in Event Viewer:

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

Description:

The Microsoft Exchange Information Store service terminated with service specific error 0.

Event Type: Error

Event Source: POP3SVC

Event Category: General

Event ID: 1026

Description:

Initialization of the POP3 external interface failed with error 0x0.

Data: 0000: ec 00 11 00

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9542

Description:

Initialization of external interface NNTP failed; Error ecNotInitialized-MAPI_E_NOT_INITIALIZED.

Event Type: Error

Event Source: IMAP4SVC

Event Category: General

Event ID: 1026

Description:

Initialization of the IMAP4 external interface failed with error 0x0.

Data:

0000: f7 00 09 00

Event Type: Information

Event Source: EXOLEDB

Event Category: General

Event ID: 118

Description:

Microsoft Exchange OLEDB was unable to initialize IFS Wrapper.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9542

Description:

Initialization of external interface WIN32 failed; Error ecServerOOM.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 5000

Description:

Unable to initialize the Microsoft Exchange Information Store service. Error 0x80040605.



CAUSE
The Services string type value located in the following registry key is missing or inaccessible:



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If the value is missing, you need to restore the following original values to the registry:

Value name: Services

Value type: String

Value:

For example, if Exchange was installed in the C:\Exchsrvr folder, the path is:

C:\Exchsrvr

If the value is present in the correct key, check the permission setting on the registry key. Use Registry Editor to check the permission setting of the key.  Get the service account of the information store. To do so:  In Control Panel, double-click Administrative Tools, and then double-click Services. Locate the Microsoft Exchange Information Store service. Double-click the service to open its properties. Note the account name in the Log on tab. By default it should be Local System account.</ol> </li> Start Registry Editor, and locate the following registry key:

</li> Use the Permission option under the Security tab to check the permission setting on this key. Make sure System is in the list with Full Control permissions if the service account is Local System. If you are not using Local System as the service account, check the existence of the corresponding account in the list and ensure that it has Full Control permissions.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The  registry key is read for the initialization of the IFSwrapper. It is used to get the path to the Ifsproxy.dll file. If this initialization fails, none of the protocols are able to register.

Additional query words: reviewdocid exch2kp2w XADM

Keywords: kberrmsg kbprb KB285116

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.