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



Please post the entire SQLStop log files from both nodes.

By NetBIOS disabled, do you mean you removed File and Print sharing and/or
Windows Client network tools. If so, then you cannot build a SQL cluster.
SQL Installer relies on this functionality to copy installation files to
remote nodes.

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

"KMcDermott" <KMcDermott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:09FAE2F0-01CC-4CC0-852D-D31C3A0C6810@xxxxxxxxxxxxxxxx
> SQL 2000 Ent. on 2003 sp1 Cluster.
>
> -Installation & Service accounts are both domain admins
> -NetBIOS disabled on NICs
> -CLuster service & failover running properly
> -Cluster resource names contain no spaces
> -User PATH for TEMP and TMP set to c:\temp
> -AVScanner Services stopped
> -Licensing Mode = Per Processor (4)
>
> Cluster Machines reside in own OU
>
> SQLstp.log files on Node1 and on Node2 both indicate "Installation
> Successful"
>
> 14:28:04 End Action LogSelectedComponents
> 14:28:05 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL
> 14:28:05 SQL data folder: R:\Program Files\Microsoft SQL Server\MSSQL
> 14:28:05 Windows system folder: C:\WINDOWS\system32\
> 14:28:05 Prog req: 38205, Data req: 34432, Sys req: 96876
> 14:28:05 Prog avail: 30955000, Data avail: 716796800, Sys avail: 30955000
> 14:28:05 Prog req vs. avail, 135081, 30955000
> 14:28:05 Data req vs. avail, 34432, 716796800
> 14:28:05 Sys req vs. avail, 96876, 30955000
> 14:28:05 DisplaySystemPreReq
> 14:28:05 Begin Action InstallPkgs:
> 14:28:05 Begin Action: Locked Connectivity Files Check
> 14:28:06 ConnectivityLocked returned: 0
> 14:28:06 The operation completed successfully.
>
> But then hang for approx 20 mins on
>
>
> 14:28:06 End Action: Locked Connectivity Files Check
> 14:28:06 Setup is installing Microsoft Data Access Components (MDAC) ...
> 14:28:06 D:\ENGLISH\ENT\x86\Other\sqlredis.exe /q:a
> 14:28:49 ExitCode: 0
> 14:28:49 InstallMSSearch instance: MSSQLSERVER
> 14:28:49 Software\Microsoft\Search\Install:Version not present
> 14:28:49 MSSearch 2.0 or greater version check returned -1
> 14:28:49 Setup is installing the Microsoft Full-Text Search Engine ...
> 14:28:49 "D:\ENGLISH\ENT\x86\FullText\MSSearch\Search\SearchStp.exe" /s
> /a:SQLServer
>
>
> End abruptly end with
>
> "Setup Failed to Perform Required Operations on the Cluster Nodes"
>
> 2 Nodes.
>
> Have tried installing only to the local node -- Same Result
>
> No indication of "Installation Failed" or "exit code was (2)" as in MSKB
> 321063
>
> After above error popup, cannot re-run cd:\ENGLISH\ENT\AUTORUN.EXE until
> server is restarted, and will only do so from "shutdown /i"
>
> Please Advise.
>
>


.



Relevant Pages

  • Re: Adding 3 nodes to a cluster
    ... First you use the cluster admin tool to add the machines as nodes to the cluster. ... Then you run the SQL installer to install binaries on the newly added nodes and allow the new nodes to host the existing instances. ... >>>I need to add these new servers as seperate instances in the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: applying SQL patch
    ... SQL hotfixes are cluster-aware, just like a SQL service pack. ... You must start the hotfix installer from the node that currently ... You may have to reboot the cluster host nodes ...
    (microsoft.public.sqlserver.clustering)
  • Re: Damaged Cluster Node
    ... The SQL 2000 SP4 installer is a cluster-wide installer and will re-apply the SP to all nodes. ... from both SQLand the cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: applying SQL patch
    ... SQL hotfixes are cluster-aware, just like a SQL service pack. ... You must start the hotfix installer from the node that currently owns ... You may have to reboot the cluster host nodes after ...
    (microsoft.public.sqlserver.clustering)
  • Re: Please help with Missing Management Studio in second node.
    ... The SQL installer only pushes cluster-aware components to all cluster nodes. ... Make sure and apply any Service Packs and Hotfixes to the second node. ...
    (microsoft.public.sqlserver.clustering)