Exchange 2003 cluster setup error

I'm running a "pure" Windows 2003 environment, and I will install
Exchange 2003 on an active/passive cluster. (/Forestprep & /Domainprep
has been implemented OK)

When I run Exchange 2003 setup on the cluster nodes, the initial
installation seems OK, but when I try to create the System Attendant
resource, I get the c0070035 error message (The network path was not
found).

The Remote Registry service is running on both nodes, and they have
registered their names in DNS (cluster node names, cluster name and
the Network Name for the virtual Exchange server).

Any suggestions??

Thanx..

EvitaN -

Two potential workarounds for a common cause of this error:
1) Check the binding order of your public NIC (in
Network->Advanced->Advanced Settings). Make sure that the public NIC is your
highest priority bound NIC.
2) Alternately, try to create the SA from another node in the cluster.

You can find more specifics on the proper config for the private and public
NICs in your cluster in chapter 7 of the Exchange 2003 Deployment Guide
available at: http://www.microsoft.com/exchange/library. This specific
setting is covered under the heading "Confirming Order of Network
Connections" or in KB.258750 (http://support.microsoft.com/?kbid=258750)

--
Evan Dodds
Microsoft Exchange Support

****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.

"EvitaN" <evi...@hotmail.com> wrote in message
news:2ac8bd8d.03110...@posting.google.com...

Hi Evan.

Thanks for your response.

However, I've checked the bindings, and the Public LAN is at the top
of the list.
I also tried to create the SA from the other node, but the same error
occurs.

Here are some line from the "Exchange Server Setup ProgresS.LOG"

[15:55:42] CTrustee::ScMakeSidFromWellKnownRid
(f:\titanium\admin\src\libs\logic\security2.cxx:664)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CTrustee::ScMakeSid
(f:\titanium\admin\src\libs\logic\security2.cxx:483)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CTrustee::ScMakeSidFromWellKnownRid
(f:\titanium\admin\src\libs\logic\security2.cxx:664)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CTrustee::ScMakeSid
(f:\titanium\admin\src\libs\logic\security2.cxx:483)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CTrustee::ScInit
(f:\titanium\admin\src\libs\logic\security2.cxx:819)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CTrustee::ScInitArray
(f:\titanium\admin\src\libs\logic\security2.cxx:1384)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CAtomServer::ScSetExtendedRightsOn
(f:\titanium\admin\src\udog\exsetdata\components\server\a_server.cxx:1833)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] Leaving CAtomServer::ScSetExtendedRightsOn
[15:55:42] CAtomServer::ScSetOrgLevelPermissions
(f:\titanium\admin\src\udog\exsetdata\components\server\a_server.cxx:1896)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] Leaving CAtomServer::ScSetOrgLevelPermissions
[15:55:42] CAtomServer::ScSetDSPermissions
(f:\titanium\admin\src\udog\exsetdata\components\server\a_server.cxx:632)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] Leaving CAtomServer::ScSetDSPermissions
[15:55:42] CAtomServer::ScAddOrRefreshDSObjects
(f:\titanium\admin\src\udog\exsetdata\components\server\a_server.cxx:366)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] CAtomServer::ScAddDSObjects
(f:\titanium\admin\src\udog\exsetdata\components\server\a_server.cxx:409)
Error code 0XC0070035 (53): The network path was not found.
[15:55:42] Rolling back creation of objects in AD
[15:55:42] Entering CAtomOMASync::ScRemoveDSObjects
[15:55:42] Removing Active Directory objects for Exchange ActiveSync
[15:55:42] Clearing HAS_WIRELESS_SYNC bit for HTTP server object
[15:55:42] Entering ScSetFlagOnServerHeuristics
[15:55:42] Leaving ScSetFlagOnServerHeuristics
[15:55:42] Creating Ldob from
"/dc=local/dc=deltaroot/cn=Configuration/cn=Services/cn=Microsoft
Exchange/cn=COMMONMAIL/cn=Administrative Groups/cn=First
Administrative Group/cn=Servers/cn=301-MSG01/cn=Protocols/cn=HTTP"
[15:55:42] CAtomOMASync::ScRemoveDSObjects
(f:\titanium\admin\src\udog\exsetdata\components\server\a_omasync.cxx:376)
Error code 0X80072030 (8240): There is no such object on
the server.

Any other things I should check??

Thanx......

"Evan Dodds [MSFT]" <ev...@online.microsoft.com> wrote in message news:<OyY6pHno...@TK2MSFTNGP11.phx.gbl>...

EvitaN -

This sort of failure is due to a failure to communicate with other servers
as required during the SA creation and is commonly related to either
networking issues or DNS configuration. Can you confirm that you have no
firewalls or other filtering between this Exchange cluster and your other
Exchange servers and DC/GCs? Also, if you have multiple DNS namespaces, can
you confirm that your suffix list is complete and that DNS is functional
from this Exchange cluster to all other Exchange servers and DC/GCs?

Hi Evan.

The problem was caused by missing entries in the suffix list on each
node in the cluster. After I added a search suffix for both the child
domain (where the Exchange server is installed) and the root domain, I
was able to add the System Attendant resource.

Does this mean that Exchange must be able to find all domain
controllers by "only" their server name instead of relying on the
FQDN??

Thanks for your help..

"Evan Dodds [MSFT]" <ev...@online.microsoft.com> wrote in message news:<uzaFbG9o...@TK2MSFTNGP11.phx.gbl>...

EvitaN -

Glad to hear that resolved it! Exchange uses both Netbios (short) names and
FQDN DNS names for various things, so they each need to be properly
resolvable in a functional install.

"EvitaN" <evi...@hotmail.com> wrote in message
news:2ac8bd8d.03110...@posting.google.com...