Microsoft Exchange: Stores fail to start with 0x8004010f error

I was recently involved in a migration from a legacy Exchange 2000 Organization to a new Exchange 2007 deployment. All was going well until the Information Store service on the Exchange 2000 Server was restarted, but failed to start due to the following error:

Unable to initialize the Microsoft Exchange Information Store service. Error 0x8004010fEvent ID: 5000 Source: MSExchangeIS

On attemping to start the Information Store manually, I was greeted with a not-particularly-verbose error stating the process failed with service-specific error code ’0′.

The issue was caused in this case by the X400 address, required by Exchange 2000/2003 for internal communications, being removed from the Default Recipient policy. Although legacy Exchange organizations require this address, Exchange 2007 deployments without any legacy Exchange Servers will function without the address , and it is possible some aspect of the new server configuration removed the entry.

Resolution

To restore the address, open Exchange System Manager on a legacy Exchange Server and edit the Default Recipient Policy. If no X400 address is present, add a new X400 address into the Recipient Policy using the appropriate information. Since removing an entry from a Recipient Policy does not remove the entry from existing mailboxes, I retrieved the required settings from an existing mailbox using the management tools on the new Exchange 2007 Server.

Once the address is added, or if it was present already but unchecked, you need to enable the entry. Attempting to check or uncheck the entry in ESM will more than likely result in an error:

X400 address cannot be disabled using Exchange System Manager

This error is to be expected, since Exchange 2000/2003 requires the X400 address and will therefore prevent any attempt to remove it as a safety precaution. To enable the address, you need to perform a low-level edit using ADSIEdit on a Domain Controller.

Usual warnings apply – ADSIEdit can make permanent and potentially destructive changes to Active Directory. Use the tool at your own risk and with proper backups in place.

In ADSIEdit at a Domain Controller, expand the Configuration Naming Context and drill down through CN=Services > CN=Microsoft Exchange > CN= > CN=Recipient Policies. Right click the Default Policy and choose Properties. You will notice the X400 address is listed within the ‘disabledGatewayProxy’ attribute. To enable:

1. Edit the disabledGatewayProxy attribute and remove the X400 address.
2. After pressing the ‘Remove’ button, the X400 configuration contents generated by Exchange are placed into the textarea. Copy this data.
3. Close the attribute so it is now stored blank. Edit the ‘gatewayProxy’ attribute, which is the location for enabled entries in the policy, and add the X400 contents from your clipboard.
4. Store your changes, then wait for or manually force Active Directory replication prior to restarting the Exchange Services.

Viola! Your IS service should now start and you can mount the stores. If the X400 issue was not the culprit, it is more than likely permissions within Active Directory. Verify the Exchange 2000/2003 computer is a member of the legacy Exchange Domain Servers group, and that group is in turn a Member Of the Exchange Enterprise Servers security group. You should then use ADSIEdit to check and reset certain permissions; the changes required are detailed over at Technet.

This post is a copy of http://tigermatt.wordpress.com/2009/05/21/exchange-0x8004010f-x400-error/

Exchange services do not start, and event IDs 2114 and 2112 are logged in the Application log in Exchange Server 2003 or in Exchange 2000 Server

Após instalar no domínio com DCs 2003 R2 com Exchange 2010 RTM e Exchange 2003 SP2 dois DCs 2008 R2 e remover os DCs 2003 R2 (o nível funcional continuou 2003) o Exchange 2010 não conseguia mais contactar os DCs e o serviço System Attendant do Exchange 2003 não conseguia iniciar, apresentando os seguintes erros no event viewer:

Event ID : 2114
Event Category : Topology
Event Source : MSExchangeDSAccess

Event ID : 2112
Event Category : Topology
Event Source : MSExchangeDSAccess

Solução para o Exchange 2010:

If you receive the error “An error caused a change in the current set of domain controllers” in Exchange 2010 the simple fix is to run the “Collect Organizational Health Data” option from the actions plane.

http://www.itgeek.co.nz/post/An-error-caused-a-change-in-the-current-set-of-domain-controllerse280a6.aspx

Solução para o Exchange 2003:

a. Start the Active Directory Users and Computers snap-in.

b. Right-click the Domain Controllers container, and then click Properties.

c. Click the Group Policy tab, click Default Domain Controllers Policy in the Group Policy Object Links box, and then click Edit.

d. Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click User Rights Assignment.

e. In the right pane, double-click Manage auditing and security log, click Add, click Browse, and then add the Exchange Enterprise Servers group.

f. In the Add user or group dialog box, click OK, and then click OK again.

g. Exit the Group Policy snap-in, and then click OK in the Domain Controllers Properties dialog box.

h. Restart the Exchange server.

http://support.microsoft.com/?scid=kb;en-us;919089&x=2&y=12