Hi,

After a few frustrating hours yesterday of continually seeing this
error message when trying to install an instance of SQL2000a on to
Windows 2003 cluster I managed to get it to work. In my case the
answer was simple, on both nodes copy the entire SQL2000a install
directories to c:\SQL2000a (has to be in the same place on both nodes)
on both cluster nodes and then the install worked fine. I also copied
the the SP3a directories to c:\SQL2000a\SP3a on both nodes and had no
problem installing that.

Originally I was trying to install SQL from a network share which both
nodes had access to (which I checked several times) and had already
disabled AV on the nodes etc. What was most annoying was in none of
the books or articles I read about clustering SQL was the fact that
installing from a network share is not going to work, unless I've
missed something.

Anyways hopefully this will help someone else.

Gareth

I have seen this happen from time to time. I know you are fixed, but this Q
is what you wanted
http://support.microsoft.com/default...b;en-us;818548

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog

"Gareth" <gb_brown (AT) hotmail (DOT) com> wrote

Well how do you know if your install is version a

I am trying to install a new virtual instance and found that when I begin
setup the only drives I see are the Quorum drives. I dont see my other 3
volumes that are in my MSDTC group. I installed initially a couple months
ago without a flaw.

NOW>....I can only see my Quorum resources.
"Gareth" <gb_brown (AT) hotmail (DOT) com> wrote

Hi dibblm,

Before i begin the SQL virtual instllation, i create a separate group in
clustering services, always being the name of the SQL virtual server your
going to create. Then add a the disk resource to this group and bring it
online. Make sure the disk is online on the node you'll be starting the
installation from. Then you should see the disk resourse in the setup.

I am new to clustering but this method has worked for me.
Anyone, please advice if this is not the Microsoft reccommended way.

Thanks,
PK

--
Message posted via http://www.sqlmonster.com

Is a separate disk drive is needed for Quorum in setting up a Windows 2003
cluster? What type of raid config you are using for sql (1 or 1+0)? How
many drives you have on your disk array?

Also what's the best way to archive tables with binary data? Flat
files/bcp/DTS may not work if need to import binary data(not a fixed length
column) with quotes etc. What I am thinking is export to another database
and back it up/archive on a regular basis. That way it will be easy to
restore when needed. Any other options?

Thanks
BVR

Thanks
"dibblm" <dibblm (AT) hotmail (DOT) com> wrote