System Attendand fail to start on a restored node (demoted DC)

[Alberto Rigatti - SED Srl]

Hi all, we have a problem:
We rebuilt a cluster node with new Win server 2k3 SP1 installation.
The node was a DC, but during restore we did not run DCPROMO, cause we don't
want to restore his DC functionality. The other node is the only DC, now.

Followed procedures on "Replacing Damaged Exchange Cluster Nodes" on
technet, reinstalling Exchange server. trying to start the VS System
Attendant resource on the restored node, we have these errors logged:

MSExchangeMU - 1042 ERROR
Metabase Update failed to read the Configuration namespace property from the
domain controller. Error code is 80040a01.

MSExchangeDSAccess - 2090 Warning
Process MAD.EXE (PID=XXXX). The Configuration Domain Controller specified in
the registry (XXX.sed.it) is unreachable. DSAccess will choose the
Configuration Domain Controller from the list of available Domain
Controllers.

MSExchangeDSAccess - 2102 ERROR
Process MAD.EXE (PID=XXXX). All Domain Controller Servers in use are not
responding:
XXX.sed.it - - (the name of the other node, the right DC)

MSExchangeDSAccess - 2114 ERROR
Process MAD.EXE (PID=XXXX). Topology Discovery failed, error 0x80040a02.

netdiag and dcdiag doesn't seems to report anything relevant.

Suggestions?

Thanks in advance.

[Nuevo]

The problem is almost certainly the fact that you did not run DCPromo on the
second node. Did you ever failover successfully before the rebuild?

Nue
"Alberto Rigatti - SED Srl" <AlbertoRig...@discussions.microsoft.com>
wrote in message news:0D3AB0B8-F2E6-4827...@microsoft.com...