Here are a few things to check.

Make sure the disk resources are all online on the node you are running the
install from.
Do not combine multiple disk resources into a single group until AFTER the
install is completed.
Make sure the disk resources are formatted correctly.
Make sure the disk resources have been brought online at least once on each
host node.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Darren Summers" <Darren.Summers (AT) Prosource (DOT) it> wrote

the same name.

If this is a Windows 2003 cluster and you have mounted volumes, this
behavior can occur. Mounted volumes are not supported on a cluster where
SQL Server 2000 is installed.

Check out this article:

http://support.microsoft.com/default.aspx?scid=kb;[LN];819546
SQL Server 2000 support for mounted volumes

Rand
This posting is provided "as is" with no warranties and confers no rights.

Hi

Thanks for replying. Forgot to mention that we have a Win2k SP4 servers
Tried what Geoff suggested, but still no difference
Tried calling microsoft, but they will charge £185 + VAT to speak to a technician. This I cant believe, since its a known fault within their product, and there is not a fix for it

Is DNS required to be working for SQL to install

Does anyone else have any other suggestions

Many Thank

Darren

You are assuming it is a known problem with the product, and it could be
but at this point in time we do not know that.

You said you went through Technet Article 293788 but there is another thing
that can cause this as well:

The same problem can happen if the resource has the same name as the drive
mapping.
For example, if the resource for drive H: is named "H:" rather than "Disk
H:", the same problem can happen.

If this does not solve the problem, you may want to open a support call
with Microsoft. If the problem turns out to be a problem with our product,
we usually refund the charge.

Rand

This posting is provided "as is" with no warranties and confers no rights.

You are assuming that you are running into this problem in the article. You
may be running into something entirely different. You even stated that the
article did not apply to your situation which would indicate that you are
not running into this praticular problem.

Rand
This posting is provided "as is" with no warranties and confers no rights.

You will need DNS to install and run a cluster properly. All cluster
members must be in the same domain and must be abloe to locate each other
and the domain controllers. If your DCs are NT4, then you need WINS
working. If you are running an Active Directory based domain, then DNS is
essential.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Darren Summers" <Darren.Summers (AT) Prosource (DOT) IT> wrote

product, and there is not a fix for it!

Format & reinstall of both nodes fixed problem

Darren