Very Computer

Just spent the day installing SQL 2000 SP2 on a W2K AS (sp2) 2-node
cluster. Various attempts to install using a terminal services client
failed. Finally went down to the server-dungeons and installed from
the console: success!

Does this make any sense? I can't find any docs indicating that this
should be a problem. The setup log (sqlsp.log) indicates that there
*may* be a problem involved with 'seeing' the shared cluster disks
from the active node where setup is run. (setup on the secondary node
completes successfully according to the log - it is the primary node
that fails).

Below are excerpts from the failing and successful log: (F: IS THE
CLUSTER DISK)

SQLSP.LOG (FAIL):
13:40:04 Processing: SQLAdHlp\Res1033
13:40:04 Processing: SQLAdHlp\ResOther
13:40:04 SQL program folder: D:\Program Files\Microsoft SQL
Server\MSSQL
13:40:04 SQL data folder: F:\SqlSystem\MSSQL
13:40:04 Windows system folder: C:\WINNT\System32\
13:40:04 Prog req: 32715, Data req: 3072, Sys req: 39110
13:40:04 Prog avail: 28155405, Data avail: 0, Sys avail: 2751309
13:40:04 Prog req vs. avail, 32715, 28155405
13:40:04 Data req vs. avail, 3072, 0
13:40:04 Sys req vs. avail, 39110, 2751309
13:40:04 Setup requires an additional 3072Kb free space on F:.
13:40:04 Action CleanUpInstall:
13:40:05 Installation Failed.

SQLSP.LOG (SUCCESS):
14:30:10 Processing: SQLAdHlp\Res1033
14:30:10 Processing: SQLAdHlp\ResOther
14:30:10 SQL program folder: D:\Program Files\Microsoft SQL
Server\MSSQL
14:30:10 SQL data folder: F:\SqlSystem\MSSQL
14:30:10 Windows system folder: C:\WINNT\System32\
14:30:10 Prog req: 32715, Data req: 3072, Sys req: 39110
14:30:10 Prog avail: 28155755, Data avail: 17206432, Sys avail:
2750941
14:30:10 Prog req vs. avail, 32715, 28155755
14:30:10 Data req vs. avail, 3072, 17206432
14:30:10 Sys req vs. avail, 39110, 2750941
14:30:10 SQLManagerApplicationClass found
14:30:10 Begin:  InstallPkgs()
14:30:10 Begin Action: Locked Connectivity Files Check
14:30:10 ConnectivityLocked returned: 3010
14:30:10 The requested operation is successful. Changes will not be
effective until the system is rebooted.

14:30:10 End Action: Locked Connectivity Files Check
14:30:10 Setup is installing Microsoft Data Access Components (MDAC)
...
14:30:10 D:\SQL2ksp2\x86\Other\sqlredis.exe /q:a
14:31:02 ExitCode: 0
14:31:02 RebootRequired: 1
14:31:02 Cleared Reboot Required value
14:31:02 InstallMSSearch instance: MSSQLSERVER

---
Erik Oxaal

Microsoft published an article "SQL 2k SP 2 readmi.txt
additions" (ID Q306909) indicate the SP2 setup may fail
when start from terminal server clinet.

Quote:>-----Original Message-----
>Just spent the day installing SQL 2000 SP2 on a W2K AS
(sp2) 2-node
>cluster. Various attempts to install using a terminal
services client
>failed. Finally went down to the server-dungeons and
installed from
>the console: success!

>Does this make any sense? I can't find any docs

indicating that this

Quote:>should be a problem. The setup log (sqlsp.log) indicates
that there
>*may* be a problem involved with 'seeing' the shared
cluster disks
>from the active node where setup is run. (setup on the
secondary node
>completes successfully according to the log - it is the
primary node
>that fails).

>Below are excerpts from the failing and successful log:
(F: IS THE
>CLUSTER DISK)

>SQLSP.LOG (FAIL):
>13:40:04 Processing: SQLAdHlp\Res1033
>13:40:04 Processing: SQLAdHlp\ResOther
>13:40:04 SQL program folder: D:\Program Files\Microsoft
SQL
>Server\MSSQL
>13:40:04 SQL data folder: F:\SqlSystem\MSSQL
>13:40:04 Windows system folder: C:\WINNT\System32\
>13:40:04 Prog req: 32715, Data req: 3072, Sys req: 39110
>13:40:04 Prog avail: 28155405, Data avail: 0, Sys avail:
2751309
>13:40:04 Prog req vs. avail, 32715, 28155405
>13:40:04 Data req vs. avail, 3072, 0
>13:40:04 Sys req vs. avail, 39110, 2751309
>13:40:04 Setup requires an additional 3072Kb free space
on F:.
>13:40:04 Action CleanUpInstall:
>13:40:05 Installation Failed.

>SQLSP.LOG (SUCCESS):
>14:30:10 Processing: SQLAdHlp\Res1033
>14:30:10 Processing: SQLAdHlp\ResOther
>14:30:10 SQL program folder: D:\Program Files\Microsoft
SQL
>Server\MSSQL
>14:30:10 SQL data folder: F:\SqlSystem\MSSQL
>14:30:10 Windows system folder: C:\WINNT\System32\
>14:30:10 Prog req: 32715, Data req: 3072, Sys req: 39110
>14:30:10 Prog avail: 28155755, Data avail: 17206432, Sys
avail:
>2750941
>14:30:10 Prog req vs. avail, 32715, 28155755
>14:30:10 Data req vs. avail, 3072, 17206432
>14:30:10 Sys req vs. avail, 39110, 2750941
>14:30:10 SQLManagerApplicationClass found
>14:30:10 Begin:  InstallPkgs()
>14:30:10 Begin Action: Locked Connectivity Files Check
>14:30:10 ConnectivityLocked returned: 3010
>14:30:10 The requested operation is successful. Changes
will not be
>effective until the system is rebooted.

>14:30:10 End Action: Locked Connectivity Files Check
>14:30:10 Setup is installing Microsoft Data Access
Components (MDAC)
>....
>14:30:10 D:\SQL2ksp2\x86\Other\sqlredis.exe /q:a
>14:31:02 ExitCode: 0
>14:31:02 RebootRequired: 1
>14:31:02 Cleared Reboot Required value
>14:31:02 InstallMSSearch instance: MSSQLSERVER

>---
>Erik Oxaal
>.

Thanks, got it!

The article says:
"Setup fails when started from Terminal Server Client on localized
versions of SQL Server SP2.
When you attempt to install a localized version of SQL Server SP2
through Terminal Server, the setup process fails. Microsoft is
currently researching this issue and will post additional information
when available."

Only thing is: this is not a localized version. The only local thing
about the server are the regional settings (Norwegian) - apart from
this all software from the OS and up are plain US-English versions.
Hmmmm....

/Erik

There are no known issues performing the installation using the Terminal
Services Client, in your case the installation did for some unknown reason
think that the F drive did not have sufficient space as noted in your
failure log. Should you encounter this issue again I would advise opening a
case with SQL support.

Dave Whitney
Microsoft SQL Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.

--------------------

microsoft.public.sqlserver.clustering,microsoft.public.sqlserver.setup
cpmsftngxa09!tkmsftngxs01!tkmsftngp01!newsfeed00.sul.t-online.de!t-online.de
!fr.usenet-edu.net!usenet-edu.net!proxad.net!isdnet!sn-xit-02!supernews.com!
postnews1.google.com!not-for-mail

Quote:>Xref: cpmsftngxa09 microsoft.public.sqlserver.setup:36434

microsoft.public.sqlserver.clustering:5168

Quote:>X-Tomcat-NG: microsoft.public.sqlserver.clustering

>Just spent the day installing SQL 2000 SP2 on a W2K AS (sp2) 2-node
>cluster. Various attempts to install using a terminal services client
>failed. Finally went down to the server-dungeons and installed from
>the console: success!

>Does this make any sense? I can't find any docs indicating that this
>should be a problem. The setup log (sqlsp.log) indicates that there
>*may* be a problem involved with 'seeing' the shared cluster disks
>from the active node where setup is run. (setup on the secondary node
>completes successfully according to the log - it is the primary node
>that fails).

>Below are excerpts from the failing and successful log: (F: IS THE
>CLUSTER DISK)

>SQLSP.LOG (FAIL):
>13:40:04 Processing: SQLAdHlp\Res1033
>13:40:04 Processing: SQLAdHlp\ResOther
>13:40:04 SQL program folder: D:\Program Files\Microsoft SQL
>Server\MSSQL
>13:40:04 SQL data folder: F:\SqlSystem\MSSQL
>13:40:04 Windows system folder: C:\WINNT\System32\
>13:40:04 Prog req: 32715, Data req: 3072, Sys req: 39110
>13:40:04 Prog avail: 28155405, Data avail: 0, Sys avail: 2751309
>13:40:04 Prog req vs. avail, 32715, 28155405
>13:40:04 Data req vs. avail, 3072, 0
>13:40:04 Sys req vs. avail, 39110, 2751309
>13:40:04 Setup requires an additional 3072Kb free space on F:.
>13:40:04 Action CleanUpInstall:
>13:40:05 Installation Failed.

>SQLSP.LOG (SUCCESS):
>14:30:10 Processing: SQLAdHlp\Res1033
>14:30:10 Processing: SQLAdHlp\ResOther
>14:30:10 SQL program folder: D:\Program Files\Microsoft SQL
>Server\MSSQL
>14:30:10 SQL data folder: F:\SqlSystem\MSSQL
>14:30:10 Windows system folder: C:\WINNT\System32\
>14:30:10 Prog req: 32715, Data req: 3072, Sys req: 39110
>14:30:10 Prog avail: 28155755, Data avail: 17206432, Sys avail:
>2750941
>14:30:10 Prog req vs. avail, 32715, 28155755
>14:30:10 Data req vs. avail, 3072, 17206432
>14:30:10 Sys req vs. avail, 39110, 2750941
>14:30:10 SQLManagerApplicationClass found
>14:30:10 Begin:  InstallPkgs()
>14:30:10 Begin Action: Locked Connectivity Files Check
>14:30:10 ConnectivityLocked returned: 3010
>14:30:10 The requested operation is successful. Changes will not be
>effective until the system is rebooted.

>14:30:10 End Action: Locked Connectivity Files Check
>14:30:10 Setup is installing Microsoft Data Access Components (MDAC)
>...
>14:30:10 D:\SQL2ksp2\x86\Other\sqlredis.exe /q:a
>14:31:02 ExitCode: 0
>14:31:02 RebootRequired: 1
>14:31:02 Cleared Reboot Required value
>14:31:02 InstallMSSearch instance: MSSQLSERVER

>---
>Erik Oxaal