Re: Setup Failed to Perform Req'd operations on CLuster Nodes

Sounds like a blown node due to a COM+ security mixup. I would follow BOL
instructions for replacing a failed node (scenario 1). Once the failed node
is out of the mix, you should be able to apply SP3a + whatever hotfix you
need to the remaining node. You can likely reformat and reload the OS on
the failed node faster than you can undo a COM+ snafu . Alternatively, you
could call PSS and see if they have any advice. At this point $250 may be
the cheapest way out.

BTW, Step 2 should say remove the failed node, not remove the entire
instance. I believe the docs are being updated to reflect the correct
procedure. Look under Maintaining a Failover Cluster, Removing a node from
an existing Failover cluster for how to remive a node from an instance.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

"KMcDermott" <KMcDermott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D00E424-F866-46D0-8856-A829121A6634@xxxxxxxxxxxxxxxx
> Geoff...
>
> rebooted node 1
> checked version as per
> http://support.microsoft.com/default.aspx?scid=/support/servicepacks/sql/2000/sp3readme.asp#_identifying_the_current_version_of_sql_server_or_analysis_services
>
> confirmed version to be 8.00.766 -- looking good
>
> rebooted node 2
> Source: EventSystem
> Category (50)
> EventID 4609
>
> COM+EventSystem detected a bad return code during its internal processing.
> HRESULT was 80070005 from line 44 of
> d:\srvtm\com\complus\src\eventsystemobj.cpp
> Please Contact Microsoft Product Support Services.
>
>
> So now I have no network connections in Control Panel, Network Service
> won't
> start (hangs) and subsequently cannot see the network, AD, or cluster.
>
>
> HELP!!!


.