If you are running a Windows Server 2008 virtual machine with “AD DS” Services (Domain Controller) and you installed Exchange 2007 SP1 on the same machine than three services may fail to start. During the boot process of the virtual machine Active Directory Services are not ready and some Exchange 2007 services will fail to start.

Screenshot of the Services console during my troubleshooting actions.

phpLMRJYI

Microsoft Exchange Information Store, Microsoft Exchange Service Host and Microsoft Exchange System Attendant services are not started. The Startup Type of has been set to Automatic.

The System EventViewer will show the following error events:

  • EventID 7024: The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).
  • EventID 7009: A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Service Host service to connect.
  • EventID 7000: The Microsoft Exchange Service Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
  • EventID 7022: The Microsoft Exchange Transport service hung on starting.

Exchange Management Console message:

  • ERROR: Could not connect to the Microsoft Exchange Information Store service on server Networknet.nl. One of the following problems may be occurring: 1- The Microsoft Exchange Information Store service is not running. 2- There is no network connectivity to server Networknet.nl. 3- You do not have sufficient permissions to perform this command. The following permissions are required to perform this command: Exchange View-Only Administrator and local administrators group for the target server. 4- Credentials have been cached for an unpriviledged user. Try removing the entry for this server from Stored User Names and Passwords.

To fix this problem change the Startup Type of Microsoft Exchange Information Store, Microsoft Exchange Service Host and Microsoft Exchange System Attendant to “Automatic (Delayed Start)”

phpzDcsBJ

 

Reboot the virtual machine again and everything should be started as smooth as you would have two separate virtual machines.

Related links: