I have a test domain which include 2-node SQL 2005 clusters. Default instance
is running on it well. As installing a named instance INS2 it gave error at
the last stage installing "SQL Database Services". After that when I try to
run the setup, setup terminates at the very beginning with the following
error log:

Microsoft SQL Server 2005 Setup beginning at Thu Mar 13 15:27:37 2008
Process ID : 2084
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe Version:
2005.90.3042.0
Running: LoadResourcesAction at: 2008/2/13 15:27:37
Complete: LoadResourcesAction at: 2008/2/13 15:27:37, returned true
Running: ParseBootstrapOptionsAction at: 2008/2/13 15:27:37
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2008/2/13 15:27:37, returned true
Running: ValidateWinNTAction at: 2008/2/13 15:27:37
Complete: ValidateWinNTAction at: 2008/2/13 15:27:37, returned true
Running: ValidateMinOSAction at: 2008/2/13 15:27:37
Complete: ValidateMinOSAction at: 2008/2/13 15:27:37, returned true
Running: PerformSCCAction at: 2008/2/13 15:27:37
Complete: PerformSCCAction at: 2008/2/13 15:27:37, returned true
Running: ActivateLoggingAction at: 2008/2/13 15:27:37
Complete: ActivateLoggingAction at: 2008/2/13 15:27:37, returned true
Running: DetectPatchedBootstrapAction at: 2008/2/13 15:27:37
Complete: DetectPatchedBootstrapAction at: 2008/2/13 15:27:37, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following
restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2084" returned false.
Running: PerformSCCAction2 at: 2008/2/13 15:27:37
Complete: PerformSCCAction2 at: 2008/2/13 15:27:37, returned true
Running: PerformDotNetCheck at: 2008/2/13 15:27:37
Complete: PerformDotNetCheck at: 2008/2/13 15:27:37, returned true
Running: ComponentUpdateAction at: 2008/2/13 15:27:37
Complete: ComponentUpdateAction at: 2008/2/13 15:27:50, returned true
Running: DetectLocalBootstrapAction at: 2008/2/13 15:27:50
Complete: DetectLocalBootstrapAction at: 2008/2/13 15:27:50, returned true
Action "LaunchLocalBootstrapAction" will be skipped due to the following
restrictions:
Condition "EventCondition: __STP_LaunchLocalBootstrap__2084" returned false.
Running: PerformDotNetCheck2 at: 2008/2/13 15:27:50
Complete: PerformDotNetCheck2 at: 2008/2/13 15:27:50, returned true
Running: InvokeSqlSetupDllAction at: 2008/2/13 15:27:50
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\sqlspars.dll Version:2005.90.3042.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [CLSNODE1]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = CLSNODE1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = CLSNODE1, Article = WMIServiceWin32CompSystemWorking, Result = 0
(0x0)
Machine = CLSNODE1, Article = WMIServiceWin32ProcessorWorking, Result = 0
(0x0)
Machine = CLSNODE1, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = CLSNODE1, Article = WMIServiceWin32DirectoryWorking, Result = 0
(0x0)
Machine = CLSNODE1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = CLSNODE1, Article = XMLDomDocument, Result = 0 (0x0)
Machine = CLSNODE1, Article = Processor, Result = 0 (0x0)
Machine = CLSNODE1, Article = PhysicalMemory, Result = 70009 (0x11179)
Machine = CLSNODE1, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = CLSNODE1, Article = OSVersion, Result = 0 (0x0)
Machine = CLSNODE1, Article = OSServicePack, Result = 0 (0x0)
Machine = CLSNODE1, Article = OSType, Result = 0 (0x0)
Machine = CLSNODE1, Article = iisDep, Result = 70348 (0x112cc)
Machine = CLSNODE1, Article = AdminShare, Result = 0 (0x0)
Machine = CLSNODE1, Article = PendingReboot, Result = 0 (0x0)
Machine = CLSNODE1, Article = PerfMon, Result = 0 (0x0)
Machine = CLSNODE1, Article = IEVersion, Result = 0 (0x0)
Machine = CLSNODE1, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = CLSNODE1, Article = COMPlus, Result = 0 (0x0)
Machine = CLSNODE1, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = CLSNODE1, Article = MDAC25Version, Result = 0 (0x0)
Machine = CLSNODE1, Article = SKUUpgrade, Result = 70391 (0x112f7)
*******************************************
Setup Consistency Check Report for Machine: CLSNODE1
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: Warning
Description: Minimum hardware requirements are not met, therefore, some
components may not perform as expected. Action: Make sure minimum hardware
requirements are met. Please refer to the readme for minimum requirements.
Article: IIS Feature Requirement, Result: Warning
Description: IIS is not installed, therefore Report Server feature will be
disabled Action: Install IIS in order for Report Server feature to be enabled
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
Article: Edition Upgrade Check, Result: Warning
Description: There can be a product on higher SP level. Action: If you are
attempting to upgrade an existing instance of Microsoft SQL Server to another
Edition by installing the RTM version of the new Edition, you need to pass
"SKUUPGRADE=1" to setup.exe on the command line.
<Func Name='PerformDetections'>
1
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\sqlsval.dll Version:2005.90.3042.0
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Thu Oct 5 12:22:42 2006
Function Name: ClusterInfoCollector::collectClusterVSInfo
Source Line Number: 888
----------------------------------------------------------
Failed to detect VS info due to datastore exception.
Source File Name: datastore\machineconfigscopeproperties.cpp
Compiler Timestamp: Wed Jun 14 16:28:00 2006
Function Name: SqlInstallConfigScope.InstanceName
Source Line Number: 95
----------------------------------------------------------
Error: Could not find an install of type 3 for instance INS2

WinException : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\machineconfigscopeproperties.cpp
Compiler Timestamp: Wed Jun 14 16:28:00 2006
Function Name: SqlInstallConfigScope.InstanceName
Source Line Number: 95

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework 2.0.log" to cab file
: "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework 2.0 LangPack.log" to
cab file : "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework Upgrade Advisor.log"
to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework Upgrade Advisor
LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework Windows
Installer.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_.NET Framework Windows Installer
LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\SqlSetup0009.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0009_CLSNODE1_SCC.log" to cab file : "C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0009.cab" Error
Code : 32
Running: UploadDrWatsonLogAction at: 2008/2/13 15:29:47
Message pump returning: 2

I cannot contiue to installation. As I said above INS2 was an unsuccessful
prior instance installation attempt.
Thanks,
Murat.

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote

SQL has issues with cluster installs when you have a login open on any of
the remote nodes.

Another problem might be the Windows Task Scheduler is not running on the
remote node.

And yet another is that teh remote node may not be able to "see" the
installation source. Locked-down or removed admin shares will cause that.

Check these things and see if any help.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"murat" <murat (AT) discussions (DOT) microsoft.com> wrote