![]() | |
![]() |
| | Thread Tools | Display Modes |
#71
| |||
| |||
|
|
Should I install SP3a on the one node BEFORE adding the second node? "Geoff N. Hiten" wrote: The second node typiclly takes some time. Here are a few things to ensure a smooth install. Install account should be a domain account that is a local admin on all nodes. Log in to all nodes at least once with service account and install accounts. Make sure admin shares are not disabled (This is how SQL gets to the install media) You might find it helpful to copy the install media to a local disk rather than the CD. If you are installing from a UNC share, make sure all machines can see it. If you are installing from a mapped drive, don't. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "Mark" <Mark (AT) discussions (DOT) microsoft.com> wrote in message news:2C50C23C-7E16-4CE0-9DB2-057F4507D642 (AT) microsoft (DOT) com... I've got the one-node failover cluster installed - like a breeze... I went back and am adding the second node now, but it's sitting at "Setup is performing required operations on cluster nodes...." and has been for around 10 minutes... I checked the log on Node 2 and it seems to be in the middle of installation of the Full-Text Search component... Is this normal?? "Geoff N. Hiten" wrote: The other possibility is you are using SQL 2000, not SQL 2000a. The "a" release has one DLL changed to make it immune to slammer. Look at the date on the i386 folder. If it is not 2003 or later, you have old media. Download a new copy and try the install. SQL 2000 without the "a" media won't install on Windows 2003. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "Mark" <Mark (AT) discussions (DOT) microsoft.com> wrote in message news:E287DCE9-F100-4CDD-8708-0E747A3EAF5E (AT) microsoft (DOT) com... Sweet, I knew you'd understand... Doh! From looking at the logs I believe it's this: http://support.microsoft.com/kb/318672/EN-US/ But I was wondering if there are any online steps to setting up a one node failover cluster and then adding the second node?? Thanks, Mark "Edwin vMierlo [MVP]" wrote: Mark, great detail on what you have done trying to solve...uhhh... something ... but you missed out on telling us what is the problem you are trying to solve ? ;-) "Mark" <Mark (AT) discussions (DOT) microsoft.com> wrote in message news:4AA77AD4-8F06-416C-AEC5-45392A49E70D (AT) microsoft (DOT) com... Ok, I've tried everything I can think of. The logs are of little help. I've walked through the KB article, setting up the Named Pipes connection to install a named instance, I've tried just a default instance, the cluster works fine and all I get back is Setup cannot complete the operation on both nodes> and then cleanup and that's it. I've been doing this for FOUR days... What AM I MISSING! Cluster working, can failover both the MSDTC Group and the Cluster Group. Have 2 other shared disks (data/logs). I don't know if maybe I need to cleanup the previous installations (attempted) somehow - but I don't know how or where or what... I'm so frustrated at this point. Please ANY AND ALL SUGGESTIONS ARE SO WELCOME!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!! I'm BEGGING!!!!!!!!!!!!!! |
![]() |
| Thread Tools | |
| Display Modes | |
| |