Install Fails On X64 Cluster Nodes.
Feb 13, 2006
I can't seem to install SQL Server 2005 (x64 version) on an x64 Win2k3 two node cluster.
I get all the way through the configuration and setup fails because it cannot start a task on the remote node. The error message indicates to check the task scheduler log file, which I have and I cannot find any 'errors' in the file.
Google/MSDN/Technet turn up nothing on multiple searches. Has anyone else run into this problem?
My installation account is a local admin on both machines, so is the sql cluster account. For the life of me I cannot figure out what's different for an x64 install vs 32bit....
View 2 Replies
ADVERTISEMENT
Oct 5, 2007
Hi There
I have found no real documentation on this, so any links would be greatly appreciated.
We have an existing 2 node active active cluster.
A default and and named instance SS2005 Enterprise Edition are installed on the cluster.
Recently we acquired new hardware, 2 servers, which we added to the cluster so we now have a 4 node cluster.
The 2 new nodes have OS etc installed.
Now i have installed sql on a new multi node cluster, i have upgraded sql server in an existing cluster BUT i have never installed sql on an existing cluster for new nodes for multiple instances.
Now i presume you simply run the install on one of the new nodes, do this for a default instance, selecting both 2 new nodes to installl on. And do this again for the named instance.
But in the past I have never been promoted for which nodes to install sql on, it simply does all the nodes BUT i do not want this.
And how will the cluster know where the binary files are for each instance on the new nodes?
In a nutshell, how do i install sql server 2005 for 2 new nodes in an existing 4 node cluster for multiple instances ?
Thanx
View 5 Replies
View Related
Apr 15, 2004
I'm trying to install SQL into a new cluster. The cluster service is up and running fine. I can even fail it from Node 1 to Node 2 with no problem.
However, when I try to install SQL, I get a screen that tells me that SQL is performing required operations on the cluster nodes...this may take a few minutes.
After hanging on that message for a looong time, SQL comes up with a generic message that the install failed and that SQL is cleaning up. Then, nothing. No error message, nothing that I can track down.
Some system information:
Node 1. Dell PE2650, 2x 2.8 GHz, 2 GB RAM
- Windows 2000 Advanced Server
- Dell Perc3/DC RAID/SCSI Controller
- Dell Perc3/DI Integrated RAID Controller
Node 2. Dell PE2650, 2x 2.8 GHz, 2 GB RAM
- Windows 2000 Advanced Server
- Dell Perc3/DC RAID/SCSI Controller
- Dell Perc3/DI Integrated RAID Controller
Shared Storage. Dell PV220
- Q: Quorum (1 GB)
- S: Data (136 GB)
- T: Logs (20 GB)
Additional Notes:
1. I am using a checklist from Dell and another from MS.
2. I have also downloaded and read the checklist from sql-server-performance.com.
3. I have ensured that the comclust.exe was run on both nodes prior to starting the SQL installation
4. I am using SQL Enterprise Edition. We used the same CD to install a cluster server two weeks ago.
Questions:
1. Where can I find an installation error log that might point more specifically to where the problem might be?
2. Any thoughts on what the problem might be?
3. Anyone ever experience something similar?
View 3 Replies
View Related
Sep 28, 2007
Have SQL 2000 SP4 clustered instance running now. Attempted inplace upgrade to SQL 2K5 standard edition.
Boxes are Windows 32 bit Ent Edition, SP2. Install wizard installed pre-req's just fine, and I got past the "components to install" box of the install wizard. When I clicked next, the current 2000 instance (already installed component) was grayed out and I could not select it. Checking the messages in the install wizard, I saw that my "upgrade was blocked".
I cancelled out of the install wizard to verify all requirements.
Bounced both boxes, and now when I try to run the install wizard, it tried to install the required support files (ASP.net 2.0, SQL Native Client and what not) and then the install wizard hangs..... and never comes back. I have to kill it from taskmgr. Bounced the boxes and tried again, same thing. Install wizard hangs forever.
Yes, I am running from the active node holding the cluster resources. Yes, SQL 2000 instance is cold. Yes, I've checked add/remove programs and there is nothing to uninstall.
Checked event viewer and I see the following errors:
Hanging application setup.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Fault bucket 238575085.
I've reached out to our TAM, but any help would be appreciated. No matter how many times I try, the install wizard now chokes and never comes back.
View 8 Replies
View Related
Jan 31, 2006
I'm running into issues installing SQL 2005 Enterprise on a Win2003 server. They seem to be related to missing rights. I've done a lot of research and have come up empty. Does anyone know why I'm getting these log entries? Thanks for any help.
Running: OpenPipeAction at: 2006/0/31 11:35:35
Complete: OpenPipeAction at: 2006/0/31 11:35:35, returned false
Error: Action "OpenPipeAction" failed during execution.
Error: 0x80070005 TaskScheduler::SetTargetComputer for \SERVER
Complete: RunRemoteSetupAction at: 2006/0/31 11:35:35, returned false
Error: Action "RunRemoteSetupAction" failed during execution. Error information reported during run:
Attempting to determine log files for remote install.
Connection to remote computer's scheduler service.
Error: 80070005 Access is denied.
Skipped: InstallASAction.11
Waiting for actions from remote setup(s)
Breaking wait state and aborting package due to cancel code received: 1602
Remote setup(s) are ready
Notify package action is determined: 1602
Error Code: 0x800700e9 (233)
Windows Error Text: No process is on the other end of the pipe.
Source File Name: remotemessageliboverlappedpipelistener.cpp
Compiler Timestamp: Fri Jul 29 01:13:51 2005
Function Name: sqls::OverlappedPipeListener::writePipe
Source Line Number: 294
Notification failed to send.
View 9 Replies
View Related
May 3, 2007
On a multi node Win2003 x64 R2.
When preforming install for 2nd SQL instance. Setup fails with log entries
Task did not appear to start on machine NODE2 : 267013
Task did not appear to start on machine NODE3 : 267013
Note: first install worked fine - after getting over MSDTC issues...
Also have confirm task scheduler service is running on all nodes.
Anyone with some insights?
Regards
View 3 Replies
View Related
Jul 15, 2015
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical)
2. MSDTC
3. SQL ServerÂ
4. windows ClusterÂ
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
View 9 Replies
View Related
Oct 12, 2007
HI There
We had an existing 2 node active / active cluster, 1 running a default instance of Sql Server 2005 Enterprise Edition 9.0.3152 (SP2 + Hotfixes) and the other running a named instance of the same version.
We recently added 2 new nodes to the cluster, they were successfully added and we tested the cluster group failover successfuly to the new nodes.
Last night we tried to install Sql Server 2005 Enterprise edition on the new nodes.
I followed to proper proceudure of modifying the installation for both instances and selecting the 2 new nodes to apply them to. This went 100%. Sql Server 2005 successfully installed for both instances on the 2 new nodes, all log files were successful.
We then tried to apply SP2, we tried the following:
1. We ran SP2 from the active node, but when we go to the screen to select what you want to apply SP2 too we could not select anything, if you clicked on database engine the message said that these instances were already at a later version and we could not proceed. This is how i successfully applied SP2 to the original 2 node cluster but it does not work for additional nodes to an exisitng cluster.
This is also what all the documentation we could find said, refer to SP2 release notes under the topic "Failover Cluster Installation", it is also the method we found when googling.
2. We then tried what is described under SP2 release notes "Rebuild a SQL Server 2005 SP2 Failover Cluster Node".
We ran SP2 from the new nodes while they were passive, but when we got the screen where you select what to apply the SP2 too we could not select database engine the message at the bottom said that SP2 must be run from the active node and that we were attempting it from the passive node, this is what we tried in step 1 described above.
3. This was a last resort. We were advised to try failing over the instance to the new node and then running SP2. Personally i thought this was a bad idea, one should never fail over a instance of sql server to a node with incompatible binary versions and secondly when we installed sql server on the new nodes a warnng popped up before hand stating that the instances were at a later version and that the new nodes must be at this version before attempting fail over. I thought that sql would not even start, to my surprie we successfully failed over the sql group to the new node, when we ran SP2 it looked good we could select the database engine on the new node to apply SP2 too, BUT after clicking next after a few seconds the SP2 installation just closed, NO INFORMAITONAL MESSAGES NO ERRORS NO WARNINGS it just closed an never came back.
I had never seen this happen on a cluster before, needless to say this made me very nervous so we failed the sql group back to the original nodes and gave up.
PLEASE can some tell me how to apply SP2 to 2 new nodes in a 4 node cluster all methods descibed in SP2 release notes and other documentation as descibed above in step 1 and 2 do not work !
Thank You
View 3 Replies
View Related
Jul 15, 2015
I'm setting up a cluster to test a new deployments of SQL2K14 on a WSFC cluster (W2K12R2). Starwinds VS. the built in iSCSI service?Will either one allow me to build a cluster consisting of two nodes? Do I need to dedicate a third node to run the iSCSI storage?
View 4 Replies
View Related
Mar 13, 2008
Hello,
We currently have a 2 node Active/Passive 2 named instance SQL 2000 cluster. We will be chaning the configuration to Active/Active, basically moving 1 instance to the passive node (so we can take advantage of the resources on the passive node).
We would also like to add 3 nodes to the cluster making it a 5 node SQL cluster. What we are thinking of doing is basically making it an Active/Active/Active/Active with the 5th server being passive. The question I have is will I be able to add and install the 3 new nodes without having to redo the SQL cluster? Should I install the two new active nodes with the default SQL instace or do I have to install SQL with named instances? (actually I think the named instances is the way to go but then I wouldn't be posting here if I was sure about the answer).
Thx!
-Albert-
View 2 Replies
View Related
Mar 17, 2014
How many nodes can you have in a cluster with SQL 2012 alwaysOn.
I understand that availability groups are limited to 5 nodes but if you had a 10 node cluster and decided to create multiple availability groups using various nodes within the 10 nodes but never exceeding 5, is that possible?
Or is there a counter or some validation from SQL AlwaysOn that actually hard limits to a grand total of 5 nodes in a cluster?
View 6 Replies
View Related
Apr 17, 2014
I had a cluster running on 3 nodes (windows failover cluster) with server 2012 and SQL server 2012 running in the cluster. Well, I thought I'd just go ahead and rename all 3 of the hosts with new hostnames and it apparently broke the cluster pretty bad. Now when I open failover cluster manager I cannot see anything nor can I connect to the cluster object in AD. I re-named all of the hosts back to their original names but that didn't work.
View 5 Replies
View Related
Aug 6, 2014
Is it possible to create a cluster configuration, where 2 (or more) SQL Server instances running on different servers will simultaneously serve the same database attached to the same storage? Something like this:
Instance A Instance B Instance C
(active) (active) (active)
| /
| /
| /
SAN for Database and Quorum
The point would be to improve reliability and performance at the same time. All nodes would share load. If a node fails, the other nodes still work and take over the load.
I know a failover cluster can be done, where 1 instance is active and others are passive (active/passive) which improves reliability, but in this configuration just 1 instance is serving at the same time.
(As far as I understand, the active/active configuration is meant to run different databases on 2 (or more) instances such that the databases on a failing node are taken over by any other instances in the cluster.)
View 9 Replies
View Related
May 23, 2006
My question is, I'd like my actual cluster to have 4 servers. The virtual server that will be running SQL 2005 will only be installed on 2 of those nodes. Will this work or do I have to split my cluster in to 2 to meet the SQL Server 2005 2 node failover limitation? A basic config for the cluster would be like below....
ClusterSQLNode
Active SQL 2005 Server
ClusterExchNode
Active Exchange Server
ClusterAppNode
Active Application Server
ClusterFailoverNode
Failover SQL 2005
Failover Exchange
Failover Application
Will SQL 2005 install in a 4 server cluster if I only install it on to two of the nodes? Any potential gotchas?
View 1 Replies
View Related
Jan 21, 2015
Can we add physical nodes and VMs to windows cluster?
View 7 Replies
View Related
Nov 22, 2015
I have encountered issue by add a node to SQL cluster
Server 2012 R2 Datacenter version
SQL 2012 Enterprise edition
Error Status>
number of cluster nodes supported for edition - failed
I have failed to bypass with Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode
View 2 Replies
View Related
Sep 9, 2015
I'm just starting to work with AlwaysOn Availability and WSFC.
I have in my environment (in Azure) a DC, WSFC and to SQL instances, so I have 3 nodes in my Failover Cluster:
WSFCÂ
SQL1
SQL2
If I simulate failure by shutting down one of the SQL boxes my Availability group seamlessly fails over to the other SQL instance - which is great.
However, I'm starting to look into the workings of the Quorum, my envt has the default settings and when I shutdown both of my SQL servers I expected the Cluster itself to go offline as 2 out of the 3 votes will be negative, but the Cluster is still up - Screenshot below when SQL1 and SQL2 are shutdown:
Going through the Wizard (but not changing anything) it shows following config:
View 6 Replies
View Related
Jul 9, 2015
I am setting up a 3 node cluster as part of an availability group.Initially I tested failover between nodes using SQL Management Studio and everything failed over successfully when I stopped a node, and I was still able to write queries. I started to test with an application which connects using an SQL user and whenever I would switch nodes, I would get login failed. I believe the cause of this issue is because the server logins SID's which are tied to the database are different than the server logins on the other nodes which resulted in login failed.how can I ensure that the server logins SID's are the same between nodes? Is there a way of copying this over or how is this supposed to be done? I read a little about contained databases where I could just set the login on the database itself vs. creating a server login but I would rather not go down that route.Â
View 4 Replies
View Related
Aug 15, 2007
The error I got is:
Hotfix.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
EventType : sqlsesetup P1 : sysdbupg.sql P2 : 0x7361
P3 : odbcstatement__execute_batch@sysdbupg.sql@3 P4 : 0x7361
P5 : lib_odbc_statement.h@91 P6 : unknown P7 : sql9 P8 : hotfix@
P9 : x86 P10 : 3042
Log Location: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
I tried to search internet, however, I couldn't get solution.
My SQL server 2005 is standard version, OS Windows server 2003 sp2, I am using Administrator account to install it.
Thanks a lot,
Rex
View 9 Replies
View Related
May 8, 2008
We are trying to install the Standard Edition of SQL Server 2005. We already have SQL Express installed. Standard won't install and Express won't uninstall.
We have tried every suggestion we can find and some we made up. When we try to install Standard, we get to the bit where you choose what you want to install and the only thing available is workstation components.
There are so many cases of this on the Internat that I can't believe MS have not solved the issue. And I am stunned that they want to charge us more money to talk to us about how to fix something we just paid them an arm and a leg for!
What do I need to tell you to get some idea of where to go next with this?
View 11 Replies
View Related
Dec 30, 2006
I have SQL Server 2000 SP4
Cluster Services running data on SAN
I have two groups SQL1 owner SQLCL1, SQL2 owner SQLCL2
Active resources
SQLCL1 owner SQLCL1 group SQL1
SQLCL2 ower SQLCL2 group SQL2
Every 2 weeks at 1:30 on a friday of all days The active resources for SQL1CL1 switch to SQLCL2 so under active resources i have all of SQL1 in there.
I then decided to flip flop everything SQL1 to SQLCL2
Then again 2 weeks later again SQL1 fails over .....
I cannot figure out why that every 2 weeks this is failing over to the other nodes.
Any advice is appreciated
View 2 Replies
View Related
Jun 2, 2006
am trying to install sql 2005 with cluster option in win 2003 R2
servers
and keep getting sql database setup failed error.Summary log show that
it failed with error number 67.
It doesn't even create a SQLSetup0004_M2MTPONE_SQL.log file. core log
shows
Complete: DetectLocalBootstrapAction at: 2006/5/1 18:15:31, returned
true
Running: LaunchLocalBootstrapAction at: 2006/5/1 18:15:31
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe"
finished and returned: 67
Aborting queue processing as nested installer has completed
Message pump returning: 67
We have two machines in running enterprises version of R2 in a cluster.
I tried running the setup from both machines and got the same error.
I am trying to find a solution for more than week but no luck. Any
help is appreciated.
thanks - Kailash
Part of Summary log:
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : \M2MTPONEC$Program FilesMicrosoft SQL
Server90Setup BootstrapLOGFilesSQLSetup0004_NEWTPNT1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%Microsoft SQL Server90Setup
BootstrapLOGSummary.txt.
Time : Thu Jun 01 18:18:54 2006
View 5 Replies
View Related
Dec 29, 2007
I am expirincing an issue that should have been corrected in SP2. When following the steps to enable DTC on my Windows 2003 SP2 Cluster, I get the following error in the event log:
Event Type: Error
Event Source: MSDTC
Event Category: Cluster
Event ID: 4394
Date: 12/28/2007
Time: 11:30:03 PM
User: N/A
Computer: NODE1
Description:
MS DTC's log information has not been configured correctly in the shared cluster registry. Error Specifics: d:tcomcomplusdtcsharedmtxclumtxclusetuphelper.cpp:557, Pid: 3652, CmdLine: C:WINDOWSsystem32msdtc.exe
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 40 00 80 .@.€
I have tried re-applying SP2 but it does not fix the issue. Does anyone have any idea how to fix this?
Below is the environment:
NODE1: Windows 2003 Enterprise Edition, SP2, 512MB RAM
NODE2: Windows 2003 Enterprise Edition, SP2, 512MB RAM
Both servers are hosted on Virtual Server 2005 R2
Share resources in the cluster are:
Quorum Disk is "Q:"
MSDTC Disk is "T:"
SQL Dist is "S:"
View 1 Replies
View Related
Jan 23, 2006
I'm building an SQL Server 2005 cluster on a Windows 2003 cluster. Windows 2003 cluster and MSDTC service are all up and running properly. No problems there, but when I try to install SQL Server 2005 as a cluster service, it fails. The installation goes past the stage where it validates both the nodes and doesn't find any issue there, but when it tries to install fiels it fails. It fails on node 2. When I checked the scduled installer job it creates on node2 to install, the job never seems to run and fails. I'm using only one user account to setup windows cluster MSDTC and SQL Server. Now the complications: It is 64 bit Windows 2003 and SQL Server 2005. Also, the node 1 is built to be a domain controller as well.
Any help will be highly appreciated.
View 8 Replies
View Related
May 22, 2007
I had a stand alone sql server that I upgraded to a cluster. I have an odbc connection called my_connection. The odbc test works fine. When I call the dsn from a php script it fails with this message:
Warning: odbc_connect(): SQL error: [Microsoft][ODBC SQL Server Driver][DBNETLIB
]SQL Server does not exist or access denied., SQL state 08001 in SQLConnect in D
:storage est.php on line 3
Could not connect to my_connection!
This same script works fine from any other computer. Is there an issue with connecting to a virtual server from the node via ODBC? Is there something I need to change in the client protocols?
Thanks in advance.
View 6 Replies
View Related
Sep 19, 2007
I'm have been assigned the task of installing SQL Server 2005 as a cluster on a Windows cluster that has already been setup with a sans.
I've done alot of reading the past two days and I still have a few questions which I need answered before I begin.
Our setup-
DC - nothing but domain controller
S1 - SQL server 1
S2 - SQL server 2
S1 and S2 share the following drives (database) (transaction logs) (F) (G)
Do I install SQL on each of the clusters? If so, do I just follow the instructions the exact same? And am I suppose to power S2 down while I install SQL on S1 and then vice-versa?
Thanks.
View 6 Replies
View Related
Jan 17, 2007
2 issues:
1. have 4 drives and all are within the SQL resource group but can see only 1 drive through management studio when doing a backup
2. Is restore only possible through the /backup folder on the default installation path as it is a small drive so can a restore be possible from any other locations
Any help
View 1 Replies
View Related
May 28, 2000
We have successfully been using MSCS with MSSQL7 (SP1) running under NT4 EE
(SP6a), installed in an active/active configuration using, two DELL
PowerEdge 6350 machines. Recently I installed MSSQL7 (SP2), I followed the
instructions that came with SP2, and unclustered the SQL nodes using the
Failover Cluster Wizard, and installed SP2, this was uneventful, and
appeared to install correctly. Next I tried to recluster the SQL nodes
using the Failover Cluster Wizard as directed. This failed with: "Could not
run setup on remote machine. SQL Cluster Setup failed." So I began the
usual research using the usual resources, and have found articles that
discusses this error, and the things to look for when it happens. I have
exhausted all suggestions without success. I appear to have everything
correctly configured. I have enabled Cluster Logging (level 3), following
are the two things I have found that indicate something is wrong:
1. In the SQL Error Log the following gets logged when I run the wizard:
"Attempting to initialize Distributed Transaction Coordinator."
"Failed to obtain TransactionDispenserInterface:
XACT_E_TMNOTAVAILABLE"
2. In the Cluster Log I see the following message repeatedly:
"[ClRtlCopySecurityDescriptor] MakeSelfRelativeSD failed,
0x00000551"
3. In the sqlclstr.log I see the following, without an indication of
which file is missing:
"[reghelp.h:235] : 2 (0x2): The system cannot find the file
specified."
"[clushelp.cpp:166] : 259 (0x103): No more data is available."
"[validate.cpp:147] DeleteTestGroup:OpenClusterResource: 5007
(0x138f): The cluster resource could not be found."
"~~~ XXX InstallRemote failed"
Does anyone have any ideas about what could be causing this problem?
Many thanks in advance.
Christpher Cutts
LifeMasters Supported SelfCare
View 1 Replies
View Related
Jul 23, 2005
I posted this to the ms sql clustering news group, but I thought I'dpost it here just in case someone here knew the answser. This problemhas had me baffled for 5 months, and I'm not seeing any supportarticles from Microsoft on it, yet. Anyone here got a clue?About 5 months ago, I posted a query to this group after experiencingfailures with my database maintenance plans (during the verify phase)that run on SQL Clusters on Windows 2003(http://groups-beta.google.com/group...9b?dmode=source)I was re-posting this in hopes that someone knows of a fix besidescoding a home-brew verify step in to the backup job to check the file'sintegrity?Thanks,TW
View 1 Replies
View Related
Aug 11, 2006
I have two clustered server. (ms sql 2000 server, windows 2003 server) now i need to add one new server to the cluster and take the secondary node off.
I have installed SP4 & hotfix in my SQL Server cluster before.
My question is do I still need to install SP4 & hotfix in my new server?
Thanks in advance
View 1 Replies
View Related
Feb 13, 2007
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.
For a premier product, this installation SUCKS.
Whooo. Okay. I feel better.
Here's my situation:
4-node Cluster (Windows 2003 Enterprise Edition), SP1
SQL 2005 Enterprise Edition
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.
Regards,
hmscott
View 2 Replies
View Related
Aug 7, 2007
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
any explanation is appreciated
rgds
Sinisa
View 1 Replies
View Related
Feb 21, 2007
Just to confirm I do need to run SQL 2005 SP2 on the passive node. but the passive node should be rebooted.
View 1 Replies
View Related
