Hi we have a two node windows 2003 x64 cluster, each running a SQL 2005 instance. I've added a new node to the cluster and am now trying to set up a new instance of SQL 2005 on the new node (node c). During the install i am getting a failure just after the stage where you choose the features to install. I'm selecting SQL database engine with Failover Cluster. When i click next i get a message which states:
"The drive specified cannot be used for program location. Program Files must be installed on a valid local disk available on all cluster nodes. The valid values are"
I've read a number of articles about possible causes for this and i've checked all the suggested causes but none of these have made a difference. The cluster disk resource is healthy and can be failed between all nodes in the cluster. No errors are generated. I am using an account which has domain admin rights and I can access all admin shares on all nodes. Some of the articles i have referenced are here:
http://support.microsoft.com/kb/907261
http://support.microsoft.com/?kbid=913815
http://blogs.technet.com/mbaher/archive/2007/03/23/clustering-sql-2005-and-administrative-shares.aspx
I've tried uninstalling all components etc but still i can't get it to work. The next step is rebuilding the server completely so does anyone have any suggestions?
When trying to install SQL 2005 as a failover cluster in a Windows 2003 64 bit SP 2 cluster, I receive the following error when trying to select the installation path after choosing to install as a failover cluster.
_________________________ TITLE: Microsoft SQL Server Setup ------------------------------ The drive specified cannot be used for program location. Program files must be installed on a valid local disk available on all cluster nodes. The valid values are __________________________
There is a knowledge base artical that says this can be from not installing the software with an account with admin permissions on all the servers in the cluster with the 64 bit install, but the account I used is an admin on both servers.
The only thing that I can think is causing the problem is that it is setup to boot from our SAN and it is using one fabric. By default Microsoft Clustering doesnt like this, but we use the newest storeport driver and applied the registry key supplied in KB article 886569 to resolve this. I could not find any documentation showing that this would limit a SQL 2005 Failover Cluster from seeing the shared storage.
I am tying to set up an SQL 2005, SP1 failover cluster on a new set of hardware. Everytime I try to run the install, I get this error
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.
I've gone through this doc (http://msdn2.microsoft.com/en-us/library/ms189910.aspx) and checked all of the applicable cautions:
I don't have an antivirus package running.
All of the SQL setup pre-checks run fine.
I have a SQL Group created, with the shared drive as a resource.
NBT is disabled on both heartbeat NIC's.
NBT is explicitly enabled on both external NIC's.
While I do have DDNS running, just to be safe I've pre-created an A record for my SQL VR.
Both nodes are registered in DNS and Setup correctly finds the second node.
In the Application event log on the second node (the one failing...), I get MSI Installer 'Install Started' successes (and sometimes I even get "Product: Microsoft SQL Server 2005 -- Installation completed successfully.")
I am running the install as myself, a Domain Admin and am explicitly added to the Administrators group on both servers.
Remote Registry is running.
Task Scheduler is running.
There is plenty of space everywhere.
All of the Admin shares are enabled.
The node I am running the install from is the owner of all of the cluster groups and resources:
Cluster group
MSDTC group
SQL group
This is all that is in my setup log:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Time : Tue Nov 06 16:45:52 2007
Task did not appear to start on machine: \ERLEW01B: 267013
I'm at a total loss and I'm getting very frustrated...
Hello All, I am trying the following script to upgrade SQL Server 2005 SP1 to SP2. I have an Active Passive cluster configuration. I have default instances of SQL Server. I am using the following script.
The sql server install fails to run. When I used the above command with just
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /quiet still the summary.txt file came with authentication success and that is all. I changed the above script and did
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /instancename=instancename of the cluster
This worked, however the install patched the passive node (DB engine, all the cluster unaware components) but failed to patch the DB engine on the Active node. I had to run the SQL Server sp2 install manually but still it did not patch the DB engine on the primary node
1. Can someone please help me with this issue as I want the unattended install to work. so it installs both active and passive node. I will post the final output and also the ADS script to do this as a bonus if this works.
Here is the summary.txt file.
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID msftesql Database Services Service 5152 MSSQLSERVER Database Services Service 4412 ResrcMon.exe Database Services Application SHOMSCSService 4688 ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2153 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file D:Microsoft SQL ServerMSSQL.1MSSQLData for user sqlservice. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 1129 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 2004 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- ********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29506
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get: SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node. There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253 KB Number: KB921896 Machine: DB1 OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: Yes Log Location on Passive Nodes: (DB1) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix (DB2) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.1.2047 x86 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD Integration Services ENU SP1 9.00.2047.00 x86 STANDARD SQL Server Native Client ENU 9.00.2047.00 x86 Client Components ENU SP1 9.1.2047 x86 STANDARD MSXML 6.0 Parser ENU 6.00.3883.8 x86 SQLXML4 ENU 9.00.2047.00 x86 Backward Compatibility ENU 8.05.1704 x86 Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
I am trying to install SQL Server 2012 onto an already configured and validated windows failover cluster (server 2012) but the process is hanging after installing the setup files.
The last entry in the log is:
running discovery on remote machine
and I've left it hanging like this for 4 hours and nothing happens.
I noticed in installing a SQL2005 failover cluster instance,that it is not necessary to install on both servers. Installing on the primary node automagically installs to the secondary node. Does this constitute a COMPLETE install? It all seems to work. BUT this process does not intall client pieces (SSMS, for instance) on the secondary node. If you want that stuff there, do you then go to that box and just do a client install?
I am trying to install SQL failover cluster on one of my nodes so it should install sql on the 2nd node. It keeps coming back saying setup failed to start on the remote machine. When I look in scheduled tasks it is listed as could not run. Can someone please help.
We have sql server 2005 installed locally on 2 servers and want to set up failover clustering. Do we need to uninstall what we have then install as failover cluster? Thanks.
1. Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk. 2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode. 3. after fail over done to 2nd secondary node what mode in production(readonly or read write). 4. how to rollback to production primary ,will change data in secondary will get updated in primary.
1. In alwaysON fail over cluster, Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. After fail over done to 2nd secondary node what mode in production(readonly or read write).
4. How to rollback to production primary ,will change data in secondary will get updated in primary.
When using this connection string, the connection to MAIN is alrigth, but when we simulate a unavailability situation on "MyBase" or on the entire MAIN instance, the new connection are joining the MAIN and not the BCKUP SQL Server.
We tryed several Connection Strings including Failover_Partner, Initliag Catalog instead of database... but no one succed in joining the BCKUP SQL Server.
I precise that the DNS on the PC that connect to SQL server is configured and both MAIN and BCKUP are resolved in command line or in explorer.
Is there an other driver that must be used, or is there an other parameter to set in the connection string ?
When using this connection string, the connection to MAIN is alrigth, but when we simulate a unavailability situation on "MyBase" or on the entire MAIN instance, the new connection are joining the MAIN and not the BCKUP SQL Server.
We tryed several Connection Strings including Failover_Partner, Initliag Catalog instead of database... but no one succed in joining the BCKUP SQL Server.
I precise that the DNS on the PC that connect to SQL server is configured and both MAIN and BCKUP are resolved in command line or in explorer.
Is there an other driver that must be used, or is there an other parameter to set in the connection string ?
Curious on how this will work.. if i install sql 2005 standard edition on one virtual server.. to a fixed disk (actually 2 fixed disks.. one for C, one for D).. then install another 2005 standard edition on another virtual server.. do i just rerun the setup and suddenly the failover cluster option will NOT be greyed out?
I am intsalling SQL 2005 in an activepassive cluster. The OS is Windows 2003 with SP1. Everything installs OK but the sql server service cannot start afterwards. There are many access errors in the Security Event log - see example below - and numerous "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. " errors in both the SQL and Application event logs. I have tried installing SQL in both mixed mode and under Windows Authentication and get the same errors. I can install SQL 2005 outside of the cluster on both nodes. Other items of note: This was a SQL 2000 cluster. I uninstalled SQL 2K, the virtual name was changed (IP remained the same) and the DNS entry was updated to reflect the new name. Early in the installation process - 3 or 4 days ago - I got a few errors about the Server Principal Name had to be updated but when I do a setspn -l the both nodes are listed and the entries look fine, though there are no entries for the sql service (MSSQLSvc). Not sure if there should be entries for the virtual name, but there aren't any for either the old or new name. Does the new virtual name need to be added to AD? Here is the security error - Event ID is 560 and it looks like there's a problem with Remote Access and is generated when trying to access either node: Category: Object Access Type: Failure Audit Event_ID: 560 User: NT AuthorityNetwork Service Object Open: Object Server: SC Manager Object Type: SERVICE OBJECT Object Name: RemoteAccess Handle ID: - Operation ID: {0,134558507} Process ID: 1516 Image File Name: C:WINDOWSsystem32services.exe Primary User Name: CM-OHCO-DS006B$ Primary Domain: SWNA Primary Logon ID: (0x0,0x3E7) Client User Name: NETWORK SERVICE Client Domain: NT AUTHORITY Client Logon ID: (0x0,0x3E4) Accesses: Query status of service
One other informational message that may be of use - looks like there's a problem with dll's for remote access, though this isn't pertaining to SQL: The description for Event ID ( 0 ) in Source ( srmservice ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: srmservice error: 0, Started the agent (srmagent.exe)..
Installing SQl2005 into on Win2003 2 node cluster, at the very end of the setup receive a message 'Remote Setup failed'. Referred to some sql logs and found this; Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603 Aborting queue processing as nested installer has completed Message pump returning: 1603
I've seen some similar errors on the web and suggestions about the Task Scheduler being started on both nodes, but I ensured these were both started before the install. SQL2005 does seem to be ok on the node1 where the install was made, but fails when trying to failover to node 2.
I have attempted to install SP1 on to my SQL 2005 Server numerous times and cannot get it to be successful. It failes on database services everytime and the log and event log report that my account cannot change permissions on the Data directory. My system is running Server 2003 R2 Ent x64. I have a Cluster setup with no second node at this time (future additon). I am also using a mount point inside the Data directory for logs. I have monitored the install using FileMon and do not see any file access issues during the installation process. I have also looked at the files and directories within the Data directory and all security ACLs seem fine. I am running the install with an account that has admin permission on the box. The service account I am using to run the sql service does not have admin permission but it is in the groups that SQL sets up at install time and those groups are assigned to the Data directory and other directories that the install configures. Any and all help us greatly appriciated!!
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
Process: Install OS Patch OS to SP1 Cluster OS on SAN Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks Configure MSDTC (network access, configure cluster resources)
Start SQL Installation Install RTM Binaries on Node 1 for Default Instance Install Workstation and non-cluster components on remaining nodes Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either: Hang while waiting for the first passive node for the default instance; or Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
When you try to re-apply SP2 for SQL 2005 on node added to cluster it continously fails?
Only way to apply SP2 is to shut down original node(with SP2 allready applied) and then apply SP2 and hotfixes on additional node!
I would like to see some reply from SQL support team for this 'issue'. Is this normal? This bring many issues when you have more than one sql on 2 node cluster....etc
I am trying to apply MS SQL Server 2005 SP1 onto a 2 node cluster running Windows Server 2003, but it fails for SQL and the Analysis Services components of SQL Server, the error I am getting is MSP returned 1603 for both components. I have tried rebooting the machines but still get the same issue, the only additional dependency for SQL that I have added is for a 2nd physical disk. log details are below.
Many thanks in advance for any help you can provide on this problem.
01/15/2007 12:26:26.937 ================================================================================ 01/15/2007 12:26:26.953 Hotfix package launched 01/15/2007 12:26:27.703 Product discovery successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.703 SP Level check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.734 Product language check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.750 Product version check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.765 Command-line instance name check completed during the install process 01/15/2007 12:26:27.781 Baseline build check completed during the install process 01/15/2007 12:29:31.734 Attempting to install instance: MSSQLSERVER 01/15/2007 12:29:31.750 Enumerating passive cluster nodes 01/15/2007 12:29:31.765 Patching available passive node: GBCONV1A002N03 01/15/2007 12:29:31.781 Attempting to patch running passive node: GBCONV1A002N03 01/15/2007 12:29:31.796 Waiting for first successfully completed passive node 01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \GBCONV1A002N03 01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \GBCONV1A002N03 01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \GBCONV1A002N03 01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:28.671 Scheduled task for product instance target has completed 01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received 01/15/2007 12:30:33.734 Removed scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.953 Remote process completed for product instance target 01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0 01/15/2007 12:30:36.812 First successful passive node has been completed 01/15/2007 12:30:36.828 Attempting to install target: GBCONV1A002N01 01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp 01/15/2007 12:30:36.890 Attempting to check for locked files: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp 01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:WINDOWSHotfixOLAP9LogsOLAP9_Hotfix_KB913090_sqlrun_as.msp.out 01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation. 01/15/2007 12:30:41.140 Unable to check MSP file: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp 01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 689 01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER 01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch 01/15/2007 12:30:41.218 All running passive nodes have completed their patch 01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER 01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER 01/15/2007 12:30:41.250 01/15/2007 12:30:41.281 Product Status Summary: 01/15/2007 12:30:41.296 Product: SQL Server Native Client (64-bit) 01/15/2007 12:30:41.312 SQL Server Native Client (64-bit) (RTM ) - Success 01/15/2007 12:30:41.312 01/15/2007 12:30:41.328 Product: Setup Support Files (64-bit) 01/15/2007 12:30:41.343 Setup Support Files (64-bit) (RTM ) - Success 01/15/2007 12:30:41.359 01/15/2007 12:30:41.375 Product: Database Services (64-bit) 01/15/2007 12:30:41.390 Database Services (64-bit) (SP1 2047 ENU GBCONV1A002V03) - Failure 01/15/2007 12:30:41.406 Analysis Services (64-bit) (RTM 1399 ENU GBCONV1A002V04) - Failure 01/15/2007 12:30:41.406 01/15/2007 12:30:41.421 Product: Integration Services (64-bit) 01/15/2007 12:30:41.437 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied 01/15/2007 12:30:41.453 01/15/2007 12:30:41.468 Product: MSXML 6.0 Parser (64-bit) 01/15/2007 12:30:41.484 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.484 01/15/2007 12:30:41.515 Product: Backward Compatibility (64-bit) 01/15/2007 12:30:41.531 Backward Compatibility (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.546 01/15/2007 12:30:41.546 Product: Microsoft SQL Server VSS Writer (64-bit) 01/15/2007 12:30:41.578 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.593 01/15/2007 12:48:34.562 Hotfix package closed
SQL Server 2005 Enterprise Edition X64 keeps failing during the install. Every single compnent installes EXCEPT the actual database engine. The only error message I get is that the server failed to install because of a fatal error. This happens when the installer is trying to set "internal parameters" on the database engine install phase.
I have tried uninstaling everything and even used the Windows Install Clean up tool to clean out bogus references after my 1st attempt to install the DB server, but nothing has helped. I hope someone has some ideas on how to proceed.
The server is a brand new Dell PowerEdge 1900 SC running 2 Quad Core Xeon 2.0 GHz processors, 8 GB of RAM and Windows Server 20003 RC2 X64 factory installed from Dell.
I attempted to post the verbose setup log in this post, but it was to long. I can email the text file or upload it to our web server and link it in here if some one wants to see it. It wasn't a whole lot of help to me.
Microsoft SQL Server 2005 Setup beginning at Wed Jun 28 19:02:06 2006 Process ID : 1220 E:Serverssetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2006/5/28 19:2:5 Complete: LoadResourcesAction at: 2006/5/28 19:2:5, returned true Running: ParseBootstrapOptionsAction at: 2006/5/28 19:2:5 Loaded DLL:E:Serversxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2006/5/28 19:2:6, returned false Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run: Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Mon Jun 13 14:30:00 2005 Function Name: sqls::CryptSameUserSameMachine::ProtectData Source Line Number: 50
2 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "1220"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2006/5/28 19:2:6 Complete: ValidateWinNTAction at: 2006/5/28 19:2:6, returned true Running: ValidateMinOSAction at: 2006/5/28 19:2:6 Complete: ValidateMinOSAction at: 2006/5/28 19:2:6, returned true Running: PerformSCCAction at: 2006/5/28 19:2:6 Complete: PerformSCCAction at: 2006/5/28 19:2:6, returned true Running: ActivateLoggingAction at: 2006/5/28 19:2:6 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 00D9CFC4Unable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44
Class not registered. Failed to create CAB file due to datastore exception Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "1220"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.HostSetup Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Message pump returning: 2
I am attempting to install SQL Server express on an XP (SP2) machine with a Pentium processor. The .NET framework version is 2.0. All previous versions of SQL server and related components have been uninstalled, and all related files deleted. Also, during installation, I installed SQL Express using the local service account (vs. network service) per a suggestion in a related thread. I have installed/unistalled numerous times, and continue to receive the same error. At this point, this is becoming a critical issue related to a client ASP.NET application using a SQL express 2005 database. I was hoping by now that MS would have released a new version or patch that would solve this problem, but that does not seem to be the case, that I'm aware of.
Summary Log:
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Aug 21 14:59:31 2007
Machine : DEBASER1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : MSXML 6.0 Parser (KB933579) Product Version : 6.10.1200.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_MSXML6_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : SQL Server Database Services Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server 2005 Express Edition Product Version : 9.2.3042.00 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQL.log Last Action : InstallFinalize Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (3) The system cannot find the path specified. Error Number : 29503 --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Microsoft SQL Server 2005 Setup beginning at Tue Aug 21 14:59:31 2007 Process ID : 2960 c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.3042.0 Running: LoadResourcesAction at: 2007/7/21 14:59:31 Complete: LoadResourcesAction at: 2007/7/21 14:59:31, returned true Running: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3609.0 Complete: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31, returned true Running: ValidateWinNTAction at: 2007/7/21 14:59:31 Complete: ValidateWinNTAction at: 2007/7/21 14:59:31, returned true Running: ValidateMinOSAction at: 2007/7/21 14:59:31 Complete: ValidateMinOSAction at: 2007/7/21 14:59:31, returned true Running: PerformSCCAction at: 2007/7/21 14:59:31 Complete: PerformSCCAction at: 2007/7/21 14:59:31, returned true Running: ActivateLoggingAction at: 2007/7/21 14:59:31 Complete: ActivateLoggingAction at: 2007/7/21 14:59:31, returned true Running: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31 Complete: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2960" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2007/7/21 14:59:31 Complete: PerformDotNetCheck2 at: 2007/7/21 14:59:31, returned true Running: InvokeSqlSetupDllAction at: 2007/7/21 14:59:31 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.3042.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [DEBASER1] 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 = DEBASER1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = DEBASER1, Article = XMLDomDocument, Result = 0 (0x0) Machine = DEBASER1, Article = Processor, Result = 0 (0x0) Machine = DEBASER1, Article = PhysicalMemory, Result = 0 (0x0) Machine = DEBASER1, Article = DiskFreeSpace, Result = 0 (0x0) Machine = DEBASER1, Article = OSVersion, Result = 0 (0x0) Machine = DEBASER1, Article = OSServicePack, Result = 0 (0x0) Machine = DEBASER1, Article = OSType, Result = 0 (0x0) Machine = DEBASER1, Article = AdminShare, Result = 0 (0x0) Machine = DEBASER1, Article = PendingReboot, Result = 0 (0x0) Machine = DEBASER1, Article = IEVersion, Result = 0 (0x0) Machine = DEBASER1, Article = DriveWriteAccess, Result = 0 (0x0) Machine = DEBASER1, Article = COMPlus, Result = 0 (0x0) Machine = DEBASER1, Article = ASPNETVersionRegistration, Result = 0 (0x0) Machine = DEBASER1, Article = MDAC25Version, Result = 0 (0x0) Machine = DEBASER1, Article = SKUUpgrade, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: DEBASER1 ******************************************* 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: CheckPassed Article: Pending Reboot 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: CheckPassed <Func Name='PerformDetections'> 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0'> <Func Name='DisplaySCCWizard'> CSetupBootstrapWizard returned 1 <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'> Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2007/7/21 15:0:29, returned true Running: SetPackageInstallStateAction at: 2007/7/21 15:0:29 Complete: SetPackageInstallStateAction at: 2007/7/21 15:0:29, returned true Running: DeterminePackageTransformsAction at: 2007/7/21 15:0:29 Complete: DeterminePackageTransformsAction at: 2007/7/21 15:0:30, returned true Running: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30 Complete: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30, returned true Running: OpenPipeAction at: 2007/7/21 15:0:30 Complete: OpenPipeAction at: 2007/7/21 15:0:30, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2007/7/21 15:0:30 Complete: CreatePipeAction at: 2007/7/21 15:0:30, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false. Running: PopulateMutatorDbAction at: 2007/7/21 15:0:30 Complete: PopulateMutatorDbAction at: 2007/7/21 15:0:30, returned true Running: GenerateRequestsAction at: 2007/7/21 15:0:30 SQL_Engine = 3 SQL_Data_Files = 3 SQL_Replication = -1 SQL_FullText = -1 SQL_SharedTools = 3 SQL_BC_DEP = -1 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = -1 Connectivity = -1 SQL_Tools90 = -1 SQL_WarehouseDevWorkbench = -1 SDK = -1 SQLXML = -1 Tools_Legacy = -1 TOOLS_BC_DEP = -1 SQL_SSMSEE = -1 SQL_Documentation = -1 SQL_BooksOnline = -1 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2007/7/21 15:0:32, returned true Running: CreateProgressWindowAction at: 2007/7/21 15:0:32 Complete: CreateProgressWindowAction at: 2007/7/21 15:0:32, returned true Running: ScheduleActionAction at: 2007/7/21 15:0:32 Complete: ScheduleActionAction at: 2007/7/21 15:0:33, returned true Skipped: InstallASAction.11 Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: No install request found for package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: No install request found for package: "ns", install will be skipped as a result. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result. Running: InstallSqlAction.11 at: 2007/7/21 15:0:33 Installing: sqlsupport on target: DEBASER1 Complete: InstallSqlAction.11 at: 2007/7/21 15:11:8, returned true Running: InstallSqlAction.12 at: 2007/7/21 15:11:8 Installing: sqlncli on target: DEBASER1 Complete: InstallSqlAction.12 at: 2007/7/21 15:11:17, returned true Skipped: InstallSqlAction.18 Skipped: Action "InstallSqlAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.21 at: 2007/7/21 15:11:17 Installing: sqlwriter on target: DEBASER1 Complete: InstallSqlAction.21 at: 2007/7/21 15:11:22, returned true Skipped: InstallSqlAction.22 Skipped: Action "InstallSqlAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.9 at: 2007/7/21 15:11:22 Installing: msxml6 on target: DEBASER1 Complete: InstallSqlAction.9 at: 2007/7/21 15:11:24, returned true Skipped: InstallToolsAction.11 Skipped: Action "InstallToolsAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.12 Skipped: Action "InstallToolsAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.13 Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis: No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.18 Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.20 Skipped: Action "InstallToolsAction.20" was not run. Information reported during analysis: No install request found for package: "BOL", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.22 Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.23 Skipped: Action "InstallToolsAction.23" was not run. Information reported during analysis: No install request found for package: "ssmsee", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.9 Skipped: Action "InstallToolsAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "tools", install will be skipped as a result. Skipped: InstallNSAction.10 Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result. Running: InstallSqlAction at: 2007/7/21 15:11:25 Installing: sql on target: DEBASER1 Failed to install package Fatal error during installation. Setting package return code to: 29503 Complete: InstallSqlAction at: 2007/7/21 15:15:29, returned false Error: Action "InstallSqlAction" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Skipped: InstallToolsAction.10 Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result. Skipped: InstallASAction Skipped: Action "InstallASAction" was not run. Information reported during analysis: No install request found for package: "as", install will be skipped as a result. Skipped: InstallRSAction Skipped: Action "InstallRSAction" was not run. Information reported during analysis: No install request found for package: "rs", install will be skipped as a result. Skipped: InstallToolsAction Skipped: Action "InstallToolsAction" was not run. Information reported during analysis: No install request found for package: "tools", install will be skipped as a result. Skipped: RepairForBackwardsCompatRedistAction Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis: Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run: Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchMSDE2000" failed due to a precondition. Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run: Action: "UninstallForSQLAction" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchLibertySql" failed due to a precondition. Skipped: UninstallForRS2000Action Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis: Action: "UninstallForRS2000Action" will be skipped due to the following condition: Condition "Action: InstallRSAction was skipped." returned true. Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run: Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition: Condition "The Clustered SQL Server instance that hosts is installed." returned false. Running: ReportChainingResults at: 2007/7/21 15:15:29 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 3 Error Code: 0x80070003 (3) Windows Error Text: The system cannot find the path specified.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Nov 16 20:31:57 2006 Function Name: sqls::ReportChainingResults:erform Source Line Number: 3521
---- Context ----------------------------------------------- sqls::HostSetupPackageInstallerSynch:ostCommit sqls::HighlyAvailablePackage:reInstall led due to cancel code received from cancel source: 29539
I am having a problem installing the first instance in our two node cluster. We're running 64-bit 2003. I'm trying to install the database engine and client tools only, so of course I get the IIS warning for both nodes. This is expected because I don't want Reporting Services. So the install should still work. However, I'm also getting the ASP.net registration message on only one node.
"Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS)."
I suspect that I should be getting the error on both nodes because I don't have IIS installed on either node. But again, I only get a warning for one node. This is probably the cause of my failure because it sees the nodes as being out of sync. I'm not sure how to correct this though when it appears that the nodes are exactly the same. Does anybody have any ideas? Thanks in advance!
Do I have install sp2 on each node in the cluster or do I just need to install it on the active node and reboot? Do I need to pause the active node? I was looking for some documentation for this and didn't mention anything regarding pausing the active node in the cluster in order to apply the sp2 for sql 2005.
I am trying to install a new database onto a SQL 2005 cluster with installshield and am getting an error that I can not find any info on. The error is as follows.
"Cannot use program file ... for cluster server. Only 4 metafiles on which the cluster resources of the server has a dependency can be used."
I will confess to knowing very little about clustering so any help would be greatly appreciated.
I have a Cluster environment that has SQL 2000 Enterprise installed. I would like to install SQL 2005 Enterprise as well. What should I watch out for. Do I need to specify a named instance for the 05 install, setup is giving me the option and does see the 2000 instance? Is there a document that walks through this installation?
