Export (0) Print
Expand All
Expand Minimize

Services Value is Missing or Inaccessible

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2010-05-25

In Microsoft Exchange Server 2007 or earlier versions, the Microsoft Exchange Analyzer Tool reads the following registry entry to verify the existence of the Services string type value:

HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup

In Microsoft Exchange Server 2010, the Microsoft Exchange Analyzer Tool reads the following registry entry to verify the existence of the Services string type value on servers that are running the Mailbox Server role or the Client Access Server role:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup

Note   Exchange Server 2010 servers that are running the Hub Transport server role, the Unified Messaging (UM) server role, or the Edge Transport server role do not have this registry key.

The Services string type value holds the path to the Exchange installation root. The Exchange Analyzer displays an error if it finds that the Services string type value is missing or is inaccessible. The absence of the path to the Exchange installation root may cause a failure of initialize critical drivers and protocols. If this failure occurs, it causes the Exchange information store and dependent services to fail upon startup.

To address this problem, follow the steps in Microsoft Knowledge Base article 285116, Exchange Store Does Not Start: Errors 7024, 1026, 9542, and 5000.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft