Installing SQL 2000 on Windows 2003 Clustered Nodes

Hi all,
I'm trying to install SQL 2000 on a Windows 2003 Server Cluster. I've set
up two nodes in the cluster. When I try to install SQL on Node1, I get the
following error: "can't install sql server on all clustered nodes." Anyone
have any ideas?
TIAHi,
Please check following article:
http://www.winnetmag.com/Article/Ar...0037/40037.html
I had problems with Cluster installation on Windows2003 before most of the
time the problem was a service which is running on both nodes. Like MOM
Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
try to stop all unnecessary service on both nodes (take them to manual on
both nodes and reboot them then try setup again.)
Verfiy that the user you use has administrative rights on both nodes and
able to access administrative shares.
And verify that you don't have any name resolution problems. (Each node
using same DNS , WINS etc..)
Hope this helps.
"Michael C#" wrote:

> Hi all,
> I'm trying to install SQL 2000 on a Windows 2003 Server Cluster. I've set
> up two nodes in the cluster. When I try to install SQL on Node1, I get th
e
> following error: "can't install sql server on all clustered nodes." Anyo
ne
> have any ideas?
> TIA
>
>|||Thanks Umut. I think I found the problem (or rather problems!) We just got
a completely new system and half the stuff that was supposed to be
pre-configured wasn't... After about 3 hours of re-configuring everything
it's finally up and running
Thanks again!
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:9A933689-21BC-46B8-968F-4D1F3D0EF309@.microsoft.com...[vbcol=seagreen]
> Hi,
> Please check following article:
> http://www.winnetmag.com/Article/Ar...0037/40037.html
>
> I had problems with Cluster installation on Windows2003 before most of the
> time the problem was a service which is running on both nodes. Like MOM
> Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
> try to stop all unnecessary service on both nodes (take them to manual on
> both nodes and reboot them then try setup again.)
> Verfiy that the user you use has administrative rights on both nodes and
> able to access administrative shares.
> And verify that you don't have any name resolution problems. (Each node
> using same DNS , WINS etc..)
>
> Hope this helps.
>
> "Michael C#" wrote:
>