Re: sql2000 setup fails on w2003

From: RobE (anonymous_at_discussions.microsoft.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 00:44:57 -0700

Thanks for the reply,

I have created an msdtc resource in the cluster group.

The sql service, cluster service and the account used to
run setup are all domain admins with local admin rights.

I have logged on to the cluster using the accounts.

All devices are accessible.

Terminal services isn't installed

The sqlstp.log file ends with:

15:37:11 Setup is performing required operations on
cluster nodes. This may take a few minutes...
15:37:11 C:\WINDOWS\TEMP\SqlSetup\Bin\remsetup.exe
C:\WINDOWS\remsetup.ini
16:06:46 Process Exit Code: (1460) This operation
returned because the timeout period expired.
16:06:46 Begin Action : GetRemsetupRetCode
16:06:46 Installation return status on D-CL04B : -1
16:06:46 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 06/23/04
15:37:11 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x30] created for execution.
CThread::Process [0x30]
CThreadPool::RunUntilCompleteHlpr start thread
[0x30],index=0
Running '\\D-CL04B\D$\SQLENT\x86\setup\setupsql.exe k=Nb
k=Rm k=Cl -SMS -s -f "\\D-CL04B\D$\SQLENT\x86
\setup\setup.ins" -f1 \\D-CL04B\admin$\D-
CL04B_MSSQLSERVER.iss -f2 "\\D-CL04B\admin$\setup.log" -
e "stpsilnt._ex" -b -x "C:\WINDOWS\TEMP\"' (D-CL04B) ...
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 (D-CL04B)...
Service removed successfully.
Remote files could not be removed.
#### SQL Server Remote Setup - Stop Time 06/23/04
16:06:46 ####

The last line of the sqlstpx.log file is:

15:37:30 "D:\SQLENT\x86
\FullText\MSSearch\Search\SearchStp.exe" /s /a:SQLServer

                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                                          
                                             
16:06:46 End Action : Run setup on cluster nodes
16:06:46 One or more errors occurred while running remote
setup on the clustered machines.
>-----Original Message-----
>Have you created an MSDTC instance, either in the
cluster group or on its
>own?
>
>Are all accounts involved (SQL Service, Cluster, and
setup) all domain-level
>accounts that ate local admins on the host nodes?
>Are all the physical devices involved online and
accessable?
>Make sure you login to the console of each node using
each account. That
>will create all the structures for the profile locally
on each machine.
>Look in the C:\Windows folder for the SQL setup logs.
The last entry should
>give a better detailed error message.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>
>I support the Professional Association for SQL Server
>www.sqlpass.org
>
>"RobE" <anonymous@discussions.microsoft.com> wrote in
message
>news:20af801c45933$4d8c21d0$a001280a@phx.gbl...
>> Hi,
>>
>> My end goal is an active-passive sql2000 cluster
running
>> on 2 windows 2003 ee nodes.
>>
>> I have installed the os, got the san drives recognised
>> and setup the cluster.
>>
>> then i run sql2000 setup:
>> specify virtual,name,ip
>> specify default instance name
>> specify drives install options
>> setup then warns about unsigned infs, i choose yes to
>> continue
>>
>> setup then states "performing operations on the cluster
>> nodes, this may take a few minutes"
>> setup eventually fails after approx 30mins
>>
>> i have since removed node2 from the cluster to make it
a
>> single node install
>> specified the servername in client network config util
>> copied the cd locally to run setup
>> created an msdtc resource
>>
>> all with same result
>>
>> any help would be appreciated
>>
>> Rob
>>
>
>
>.
>

Relevant Pages

  • Re: Changing Windows Domain
    ... The SQL Setup program rewrites the account login ... Make sure the service accounts have the ... If the actual host names change, then a cluster rebuild may actually be ...
    (microsoft.public.sqlserver.clustering)
  • Re: sql2000 setup fails on w2003
    ... Have resorted to reloading the server and sql 2000 setup ... >I have created an msdtc resource in the cluster group. ... >run setup are all domain admins with local admin rights. ... >I have logged on to the cluster using the accounts. ...
    (microsoft.public.sqlserver.clustering)
  • Re: sql2000 setup fails on w2003
    ... Are all accounts involved (SQL Service, Cluster, and setup) all domain-level ...
    (microsoft.public.sqlserver.clustering)
  • Re: Time of failover of Microsoft SQL 2000
    ... > I have recently setup an active-active Microsoft SQL 2000 cluster on ... It usually takes under 10seconds for failover at the OS/MSCS level. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Designing a Clustering Solution
    ... you should setup the second DC as a GC as well...I meant ... File & Print can be made into cluster resources, and so can DFS if you would ... For SQL, you'll also need the Enterprise version of SQL, though you'll only ... > Server and SQL Server for the clustering. ...
    (microsoft.public.windows.server.clustering)