The Setup:
Windows Server 2003 Enterprise SP2 7GB RAM
SQL Server 2000 SP4 + AWE Hotfix
2 Node cluster Active/Passive
10 SQL Instances Running

The Issue:

SQL Instance fails to come back on after taking it offline. From event
viewer the error states that the ERRORLOG can't be found. When
checking in registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\GSQP038A
\MSSQLServer\Parameters\

* SQLArg0 -dR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\data
\master.mdf
* SQLArg1 -eR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\log
\ERRORLOG
* SQLArg2 -lR:\Program Files\Microsoft SQL Server\MSSQL$GSQQ009A\data
\mastlog.ldf

From above the details are obviously incorrect the instance name is
different (GSQQ009A resides on the same cluster as GSQP038A) and the
path is incorrect, drive paths should be O:\ and not R:\

When we update the registry with the correct details, the service has
to be started by restarting the SQL Service via the services.mmc and
not cluster admin.mmc. The SQL Service comes back online however takes
longer than it should.

Then we bring Service back online via cluster admin and all is fine
however the registry parameters have now changed back to incorrect
drive/instance so when taken offline again it will not come back
online.

So the problem lies (we think) with MS Clustering Services overwriting
registry keys from another SQL Instance. This occurs on both nodes.

Any ideas as to why this is happening?

Thanks In Advance

Scott