RE: Cluster diagnostics tool test fails
- From: "Petri" <Petri@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Nov 2005 07:57:03 -0800
Mike,
Thanks for your comments.
At first I didn't had private NIC only for private traffic, but I got advice
from otherwhere how it should be. Also from the same place I got a message
that it might be because of VMWare. As I told I'm running this on my test
system in WMVware ESX server.
After this message I wonder that it is not so important, because failover is
working fine. So now I have installed the E2003 to that and still it works :)
Have a nice Wednesday !
--
..-Petri-.
"Mike Rosado [MSFT]" wrote:
> Hi Petri,
>
> Here's how the code is interpreted.
>
> # for hex 0x80070005 / decimal -2147024891
> # Access is denied.
> E_ACCESSDENIED
> # General access denied error
>
> Are the Private Heartbeat NICs connected to a switch, dumb hub or
> cross-over cable? If they are connected to a switch, then I would
> suggested using a dumb hub or cross-over cable to see if you experience the
> same behavior.
>
> Is the Public NIC configured for All Communications and Private Heartbeat
> NIC for Internal Communication Only?
>
> --------------------
> Hope this helps,
> Mike Rosado
> Windows 2000 MCSE + MCDBA
> Microsoft Enterprise Platform Support
> Windows NT/2000/2003 Cluster Technologies
>
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> <http://www.microsoft.com/info/cpyright.htm>
>
> -----Original Message-----
> > From: <Petri@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > Subject: Cluster diagnostics tool test fails
> > Date: Tue, 29 Nov 2005 08:06:10 -0800
> >
> > Hi,
> > I have two node cluster on W2003 platform. Right after installation I ran
> > the Cluster Diagnostic tool to check that I can install E2003 to that
> system.
> > This is my test system before the production, but still.
> >
> > When the node 1 is active and I'm running the tool against cluster it
> > reports for me:
> >
> > Adding info for connection #0 of node server1. Physical
> > address=00-11-22-33-44-55
> > Adding info for connection #0 of node server1. Physical
> > address=00-11-22-33-44-66
> > Status=-2147024891("80070005H) In Loop. Error value=-2147024891 returned
> > from MiscEnumerateConnection(autosniff.cpp@262)
> > Status=-2147024891("80070005H) Failed to get Mac Addresses for cluster :
> > mycluster, Ret: -2147024891. (autosniff.cpp@739)
> >
> > When the another node is active then I get the same error on there as
> well.
> > Only difference is that server1 is server2 at then and the MAC addresses
> are
> > different.
> >
> > Should I worry of this ?
> >
> > .-Petri-.
> >
>
>
.
- References:
- RE: Cluster diagnostics tool test fails
- From: Mike Rosado [MSFT]
- RE: Cluster diagnostics tool test fails
- Prev by Date: RE: Microsoft NLB
- Next by Date: with NLB.... a master host
- Previous by thread: RE: Cluster diagnostics tool test fails
- Next by thread: Re: Exchange 2003 Cluster Problem
- Index(es):
Relevant Pages
|