Exchange 2007 cluster install - interesting note on an SCC installation
- From: No One <noone@xxxxxxxxxxxxx>
- Date: Sun, 04 Mar 2007 17:54:02 -0800
I wanted to post some quick notes on my recent Ex2007 install...
I got my client/hub server setup just fine, and then when I went to my
hardware (shared storage) cluster to install the SCC mailbox role, I ran into
a really bizarre problem.
Basically, the install was going smoothly but then I noticed in the cluster
admin that whenever I'd attempt the active server installation, the IP address
I entered during the setup was "taking over" the existing cluster IP resource.
I wasn't sure why... I setup my cluster with an IP of 10.40.32.175 and the IP
I was using during the Exchange install was 10.40.32.170. But no matter what,
everytime I did the Exchange install, the existing .175 IP was *changed* to
..170.
That resulted in the cluster going offline/becoming degraded during the
Exchange install...
The cluster was named "Exchange2007" and the name I was using during the
Exchange install was "STAFFMAIL", and that new name was being added correctly
(not "taking over" the existing name)...
So, want to know what the problem was? It's really weird, and Microsoft
should *definitely* consider documenting this:
In cluster admin, I had *renamed* the original cluster group name... I knew my
Exchange would be called "STAFFMAIL" so I went ahead and renamed the default
group to "STAFFMAIL".
Well, guess what? When you install the active SCC role, it creates a *new*
cluster group with the same name as the cluster name you enter during setup.
But since I already had one by that name, it wasn't adding a new IP address,
it was replacing the existing IP address resource!!! Doh!
I actually stumbled on the solution by accident... during my hair pulling at 3
AM, I totally removed Exchange from the active node to try a new install (for
the 4th or 5th time) and for some reason I went ahead and renamed that cluster
group to something besides STAFFMAIL.
Lo and behold, I did the install one last time and I saw that it created a new
cluster group with that name, and that's when I realized what had been
happening each time I tried to install.
So I'm posting this for the common good so that future Googler's running into
this issue will have a chance to find out what happened.
And to help in the future google searches, here's what the symptoms were:
Exchange 2007 SCC install fails with:
--
The New-ClusteredMailboxServer operation failed for server STAFFMAIL
--
Exchange Server component Clustered Mailbox Server failed.
Error: Error:
Error The data is invalid occured while performing exsetdata operation; the
original error code was 0xc007000d.
--
Process MSEXCHANGEADTOPOLOGY (PID=4764). When updating security for a remote
procedure call (RPC) access for the Microsoft Exchange Active Directory
Topology service, Exchange could not retrieve the security descriptor for
Exchange server object - Error code=80070002.
The Microsoft Exchange Active Directory Topology service will continue
starting with limited permissions.
--
Process MSEXCHANGEADTOPOLOGY (PID=4764). The site monitor API was unable to
verify the site name for this Exchange computer -
Call=ExchangeGetComputerNameExW Error code=80070002. Make sure that Exchange
server is correctly registered on the DNS server.
----------
So, in short, it didn't pay in this case to think ahead and rename your
cluster group. :-P Who knew...
.
- Prev by Date: Creatring send connectors on an Hub server
- Next by Date: Re: Exchange 2007 and AD on same server
- Previous by thread: Creatring send connectors on an Hub server
- Next by thread: RE: [ERROR] Exception from HRESULT: 0x80005008
- Index(es):
Relevant Pages
|
