Re: Exchange 2007 CCR on Windows 2008 x64 RTM

Fortunately for you I have stumbled on this problem several times and got
this guidance from a very helpful guy in Microsoft CSS.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"RobAbate" <RobAbate@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:76AF9140-8089-47CF-A51D-78175F4353CC@xxxxxxxxxxxxxxxx
EXCELLENT! I got your response and luckily I had left the install in the
"failed" state, so I ran setup.com with the parameters you mentioned, and
it
worked. I had tried the command line after the failure, as mentioned in
the
install guide, but I always did it too quickly after the failure.

Just to give you some more info on the configuration -- I have a 2008
Domain
Controller that has all FSMO roles except a GC and two other 2003 Domain
Controllers which are GCs. They are all in the same AD site and we are
running at the 2003 Forest Functional Level.

Thanks again for the help on this! I'm an MCITP on Server 2008 & Exchange
2007, and I was getting frustrated that I couldn't get this to work! I
guess
I'm just a little too impatient. Next I'll try to implement SCR (once I
move
some mailboxes over). Good thing I read the release notes for SP1 -- I'll
have to make sure that my SCR target is another 2008 Server:

"SCR cannot be deployed across multiple operating systems. In Exchange
2007
SP1, the operating system of the SCR source must match the operating
system
of all SCR targets. Therefore, an SCR source that is running on Windows
Server 2003 cannot deploy SCR targets that are running on Windows Server
2008, and an SCR source that is running on Windows Server 2008 cannot
deploy
SCR targets running on Windows Server 2003."

I was also curious about the Updates folder that you had mentioned in the
install path. I was wondering if there was an update that we could
slipstream into the install that might help with this issue, but it sounds
like the root cause is on the AD side? Are you also saying that I can
simply
download the exe of the update from microsoft.com and copy that exe into
the
Updates folder without extracting it, and it will be slipstreamed into the
install?

"Ed Crowley [MVP]" wrote:

After it errors out the first time, wait maybe 15 minutes and rerun Setup
without the /Roles:MB switch, just the /newcms /cmsname and /CMSIPAddress
switches. You might need to repeat twice. That process has worked for
us.
I'm told that this is caused by the way the cluster service creates the
computer account and password. You might find it works better if the PDC
Emulator FSMO role holder is in the same AD site as the Exchange server
you're building, but that didn't fix the problem for me. You might also
try
including the /DC switch to specify the domain controller Setup uses, but
that didn't help mine either since the cluster service ignores it. Don't
proceed with anything until you get the message that setup of the CMS has
completed successfully or you'll just have trouble later.

Note that you can drag the rollup patch file into the /Updates directory
of
your SP1 setup files share and it'll get applied automatically.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"RobAbate" <RobAbate@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:87F23CED-ED5A-418F-B205-AC71BFBA3F3B@xxxxxxxxxxxxxxxx
I am trying to set up an Exchange 2007 SP1 CCR Cluster on Windows Server
2008
x64 RTM. I have been following the instructions on
(http://technet.microsoft.com/en-us/library/bb676458(EXCHG.80).aspx),
and
I
am certain that I have all of the prerequisite roles/features
installed.
However, whenever I attempt to install the Active Clustered Mailbox
Role,
it
errors out towards the end of the setup when trying to configure the
cluster.
I am using the Exchange 2007 SP1 installation media on an RTM version
of
Windows Server 2008 x64 Enterprise Edition.

I have tried to create the Cluster Group (or Services & Applications)
with
the IP & Network Name resources online manually, and I have also
attempted
without creating the group first. If I watch during the install in
Failover
Cluster Management, I can see that Exchange 2007 Setup deletes this
group
and
then recreates it if I had it created already, and shortly after setup
errors
out. I only see the Network Name & IP resources get created. I have
the
Quorum Model set to Node & File Share Majority, and all of my Cluster
Core
Resources are Online. I also made sure that my Current Host Server is
set
to
the node that I am attempting to install the Active CCR Node to. Here
is
the
error that I get at the end of the installation: "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."
I
can see this in the Exchange Setup Log files, but I cannot determine
what
service it is attempting to start, and I do not see any Services
installed
into the Cluster Group that is created, which is what I am guessing it
is
trying to start.

Here is the bottom of the ExchangeSetup log file:

[7/21/2008 7:09:16 PM] [2] Entering ScBindToEVS
[7/21/2008 7:09:16 PM] [2] Binding to cluster'ADV70V-2K8CLN2'
[7/21/2008 7:09:16 PM] [2] Binding to EVS 'ADV70v-2K8CCR'
[7/21/2008 7:09:16 PM] [2] Leaving ScBindToEVS
[7/21/2008 7:09:16 PM] [2] Leaving ScCheckStateOfDependentResources
[7/21/2008 7:09:16 PM] [2] Querying state for service 'MSExchangeSA' on
server 'ADV70V-2K8CLN2'
[7/21/2008 7:09:16 PM] [2] Starting service 'MSExchangeSA' on server
'ADV70V-2K8CLN2'
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 PM] [2] Failed to start service
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 PM] [2] Leaving ScSetupExchangeVirtualServer
[7/21/2008 7:10:22 PM] [2] [ERROR] Unexpected Error
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 PM] [2] Ending processing.
[7/21/2008 7:10:22 PM] [1] The following 1 error(s) occurred during
task
execution:
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 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.
[7/21/2008 7:10:22 PM] [1] Setup is halting task execution because of
one
or
more errors in a critical task.
[7/21/2008 7:10:22 PM] [1] Finished executing component tasks.
[7/21/2008 7:10:22 PM] [1] Ending processing.
[7/21/2008 7:10:22 PM] [0] The Exchange Server Setup operation did not
complete. For more information, visit http://support.microsoft.com and
enter
the Error ID.
[7/21/2008 7:10:22 PM] [0] End of Setup
[7/21/2008 7:10:22 PM] [0]
**********************************************

I have uninstalled and reinstalled several times, and I have attempted
the
install from each node on several different occasions. My standalone
Mailbox/Hub/CAS Server is accessible, and run fine, and I don't see any
issues with AD. I suspect that something is happening when trying to
create
the cluster resources, but I can't see any error to troubleshoot. I
also
looked into the Windows Failover Clustering Application & Service Logs
from
Event Viewer, and I don't see any errors starting services. Any help
with
where to look to troubleshoot this would be much appreciated, as I've
been
messing around with this for a few days now and can't get past this.





.