Hi There,

Trying via NNTP as I have posted 3 messages via the web interface and they
vanish ?
I am trying to cluster SQL2K on W2K.
Have done this many times before.
W2K is SP3. Cluster working fine.
When I install SQL it takes approx 30 mins to install the second node and fails.
I have checked Technet and via an article relevent (and loads others with SQL
cluster issues, so I have
installed SQL on one node, which has created the virtual cluster fine.
Same problem adding the second node.

I have also tried installing SP3 on the fist node and adding the second node
(again suggested on Technet) but same problem.

Example of error log below. Any offers before I pay Microsoft Support :>(

18:37:01 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=1
Server.1=NODE2
[Server.1]
NumRemoteServices=1
1.app=\\NODE1\D$\x86\setup\setupsql.exe
1.server=NODE2
1.script=\\NODE1\admin$\NODE2_MSSQLSERVER.iss
1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
"\\NODE1\D$\x86\setup\setup.ins" -f1 %s -f2 "\\NODE2\admin$\setup.log" -e
"stpsilnt._ex" -x "C:\"
1.user=SUNSET\xxxxx
1.password=xxxxxxx
1.name=SQLSetup1
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
18:37:01 Setup is performing required operations on cluster nodes. This may
take a few minutes...
18:37:01 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
19:10:06 Process Exit Code: (1460) This operation returned because the timeout
period expired.

19:10:06 Begin Action : GetRemsetupRetCode
19:10:06 Installation return status on NODE2 : -1
19:10:06 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 11/04/03 18:37:02 ####

CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x90] created for execution.
CThread::Process [0x90]
CThreadPool::RunUntilCompleteHlpr start thread [0x90],index=0
Script file copied to '\\NODE2\ADMIN$\NODE2_MSSQLSERVER.iss' successfully.

Installing remote service (NODE2)...

Running '\\NODE1\D$\x86\setup\setupsql.exe k=ClSec k=Rm k=Cl -SMS -s -f
"\\NODE1\D$\x86\setup\setup.ins" -f1 \\NODE2\ADMIN$\NODE2_MSSQLSERVER.iss -f2
"\\NODE2\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"' (NODE2) ...

CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr the operation timed out.
CThreadPool::RunUntilComplete returned 1460
CThreadPool::RunUntilComplete execution level=1, need execution: 0
One or more errors occurred while running the remote/unattended setups.

Disconnecting from remote machine (NODE2)...

Service removed successfully.

Remote files could not be removed.

#### SQL Server Remote Setup - Stop Time 11/04/03 19:10:06 ####















19:10:06 End Action : Run setup on cluster nodes
19:10:06 One or more errors occurred while running remote setup on the
clustered machines.
19:12:48 Setup failed to perform required operations on the cluster nodes.
19:12:48 Begin Action : ClusterErrorCleanup
19:12:48 End Action : ClusterErrorCleanup

Cheers
Tim

Check the installation log on the second node. Usually there is a
permissions or temporary folder location problem causing a second node
installation to fail.

Make sure and log into the second node with the same account you are using
to launch the SQL installation before you start the install. Use a domain
account that is a local administrator on both nodes. this will create the
temporary folder paths needed by the installer. I make the cluster service
account and the SQL service account local administrators on all cluster
nodes to simplify things.

You will probably need to reboot the second node before retrying to clear
any pending file replacement operations.

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




"Tim Bicknelle" <no (AT) nospam (DOT) com> wrote

This error can be caused by a number of reasons.

Check the sqlsp.log file for any indication that MDAC did not install
successfully on the second node. You can also look at the dasetup.log as
well. If MDAC did not istall successfully, you can try to install MDAC 2.7
SP1 on node 2 before running the service pack setup.

If this does not help you can fail the SQL Server resource group to the
second node and run the setup from there as well.

Another option is to set SQL Server Agent, Full-Text and any other resource
in the SQL Server resource group to not affect the group. There could be a
situation where one of the resources is not coming on line and this is
causing SQL Server to not come online during setup.

Rand
This posting is provided "as is" with no warranties and confers no rights.

Tim,

Sounds like you didn't run Comclust.exe on both nodes before the install ?
Give it a try

Cheers
LM

On 05/11/2003 Tim Bicknelle <no (AT) nospam (DOT) com> wrote:

LM,

Thanks for that, missed that one.

Cheers
Tim

Check that the follow key is set to "0" on both nodes

HKLM\Software\Microsoft\Non-Driver Signing\Policy

The silent install will not display the message, therefore the install
times-out.

Hope this helps



--
deadwood
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message31722.html