When installing the first node in a CCR cluster using the following command, the installation process may fail approximately 18% of the way through the new-clusteredmailboxserver command.
setup /roles:Mailbox /newcms /CMSName:CMSNAME
Looking through the ExchangeSetup.log file, you may notice errors similar to the following:
[6/25/2009 11:51:12 AM] [2] Previous operation run on domain controller 'dc.domain.com'.
[6/25/2009 11:51:12 AM] [2] Previous operation run on domain controller 'dc.domain.com'.
[6/25/2009 11:51:12 AM] [2] Preparing to output objects. Maximum result set size "unlimited".
[6/25/2009 11:51:12 AM] [2] [ERROR] Unexpected Error
[6/25/2009 11:51:12 AM] [2] [ERROR] The operation could not be performed because object 'NODE1' could not be found on domain controller 'dc.domain.com'.
At the very end of the failed setup process, you may notice similar events to the following:
[6/25/2009 12:03:24 PM] [2] Entering ScBindToEVS
[6/25/2009 12:03:24 PM] [2] Binding to cluster'NODE1'
[6/25/2009 12:03:24 PM] [2] Binding to EVS 'CMSNAME'
[6/25/2009 12:03:25 PM] [2] Leaving ScBindToEVS
[6/25/2009 12:03:25 PM] [2] Leaving ScCheckStateOfDependentResources
[6/25/2009 12:03:25 PM] [2] Querying state for service 'MSExchangeSA' on server 'NODE1'
[6/25/2009 12:03:25 PM] [2] Starting service 'MSExchangeSA' on server 'NODE1'
[6/25/2009 12:04:31 PM] [2] CService::ScWaitForCompletion (f:\08.01.0240\sources\dev\admin\src\libs\exsetup\service.cxx:674)
Error code 0XC007041D (1053): The service did not respond to the start or control request in a timely fashion.
[6/25/2009 12:04:31 PM] [2] CService::ScControl (f:\08.01.0240\sources\dev\admin\src\libs\exsetup\service.cxx:612)
Error code 0XC007041D (1053): The service did not respond to the start or control request in a timely fashion.
[6/25/2009 12:04:31 PM] [2] Failed to start service
[6/25/2009 12:04:31 PM] [2] ScSetupExchangeVirtualServer (f:\08.01.0240\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:2013)
Error code 0XC007041D (1053): The service did not respond to the start or control request in a timely fashion.
[6/25/2009 12:04:31 PM] [2] Leaving ScSetupExchangeVirtualServer
[6/25/2009 12:04:31 PM] [2] [ERROR] Unexpected Error
[6/25/2009 12:04:31 PM] [2] [ERROR] Error The service did not respond to the start or control request in a timely fashion occured while performing exsetdata operation; the original error code was 0xc007041d.
[6/25/2009 12:04:31 PM] [2] Ending processing.
[6/25/2009 12:04:31 PM] [1] The following 1 error(s) occurred during task execution:
[6/25/2009 12:04:31 PM] [1] 0. ErrorRecord: Error The service did not respond to the start or control request in a timely fashion occured while performing exsetdata operation; the original error code was 0xc007041d.
[6/25/2009 12:04:31 PM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Tasks.ExsetdataKnownException: Error The service did not respond to the start or control request in a timely fashion occured while performing exsetdata operation; the original error code was 0xc007041d.
[6/25/2009 12:04:31 PM] [1] [ERROR] Error The service did not respond to the start or control request in a timely fashion occured while performing exsetdata operation; the original error code was 0xc007041d.
[6/25/2009 12:04:31 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[6/25/2009 12:04:31 PM] [1] Finished executing component tasks.
[6/25/2009 12:04:31 PM] [1] Ending processing.
[6/25/2009 12:04:31 PM] [0] The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.
[6/25/2009 12:04:31 PM] [0] End of Setup
[6/25/2009 12:04:31 PM] [0] **********************************************
This is showing that the services are failing to start with timeout errors.
Viewing the application log, an event similar to the following may be seen:
Event ID : 1005
Category : None
Source : MSExchangeSA
Type : Error
Message : Unexpected error The local machine must be a Kerberos KDC (domain controller) and it is not. ID no: 80090339 Microsoft Exchange System Attendant occurred.