Information Store Does Not Start with Service-Specific Error 0 (Zero) (283179)


The information in this article applies to:

  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Server
This article was previously published under Q283179

SYMPTOMS

The information store does not start, and the following system event ID is logged in the Application event log:

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.

There are informational event IDs preceding this error in the log. These are the interfaces starting up:

Event Type: Information
Event Source: POP3SVC
Event Category: General
Event ID: 1024

Event Type: Information
Event Source: EXOLEDB
Event Category: General
Event ID:100

Event Type: None
Event Source: EXCDO
Event Category: General
Event ID: 8195

Event Type: None
Event Source: EXCDO
Event Category: General
Event ID: 8195

NOTE: Following these events are shut down events.

The Store.log file (with Debug tracing enabled) lists the following errors:

TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcSearchDSValuesWithGUID
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcGetGuidAdnDN - Failed to search DS object
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcGetGuidAndDN
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in VSERVER::EcConfig - Failed to get IS guid or DN
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in VSERVER::EcConfig
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcStartServer - Failed to init VSERVER
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcStartServer
TID 9fc TAG 3: Error ecNotFound-MAPI_E_NOT_FOUND (0x8004010f) in EcMuckWithWindow

CAUSE

The machine account no longer has rights to read the information store, for the following possible reasons:
  • The server is no longer a part of the Exchange Domain Servers Group.
  • Inherited rights have been removed from the information store.
  • Explicit denies have been added to this object.
  • The object may no longer exist.

RESOLUTION

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk. Use ADSI Edit to check the permissions on the following object or verify that it exists:

CN=InformationStore,CN=ServerName,CN=Servers,CN=AdminGroupName,CN=Administrative Groups,CN=ExchangeOrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DomainName,DC=com

If the permissions are incorrect or Exchange accounts are missing, run setup.exe /domainprep. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

312407 Requirements for preparing Windows domains for Exchange Server 2003 or for Exchange 2000 Server

You can find the ADSI Edit by installing Windows 2000 Support Tools. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301423 HOW TO: Install the Windows 2000 Support Tools to a Windows 2000 Server-Based Computer

MORE INFORMATION

The same errors will also be listed if the system account does not have access to the storage group objects. (The Store.log file will be a little different.)
Modification Type:MajorLast Reviewed:8/17/2005
Keywords:kbprb KB283179
©2004 Microsoft Corporation. All rights reserved.