Active/Active CLuster can not add 2nd Node

Help, I have an active/active cluster with SQL2k5 Ent with SP2 installed on node1 that is currently running live apps, I need to add the 2nd node to have fail over functionality but if I use the Change Install from Add or Remove Programs on the primary node to add the 2nd node I get the following error.

"The File 'c:\....\SqlRun_SQL.ms' is not a valid installation package for the product Microsoft SQL Server 2005(SQL2K5VVS01). Try to find the installation package 'SqlRun_SQL.msi' in a folder from which you can install Microsoft SQL Server 2005(SQL2K5VVS01).

No I assume this is because node 1 has had service pack two applied. Does anyone have instructions how I can add node two without having to completely uninstall Node 1, as the doc’s with SQL2005 SP2 say it can not be removed, a complete uninstall of 2005 must be done?

You may have to 'break' the cluster, install SQL and SP2 on your second node, and then reestablish the cluster.|||

Hmmm was hoping for a simpler sounding fix as not the confident with cluster administration, as this live cluster also has two other SQL2000 instances running in a side by side config, reporting services and file shares.

Also wondering is there a way to get the 'SqlRun_SQL.msi' from service pack two installer, as it may run if I could get it to read this?

Accessing Second Record Set

hello all,
i had two stored procedures,where the 1st SP is calling 2nd SP(which returns 2 record sets).
how can i access the second recordset from the 1st SP
it would a great help if anyone help me out!!
thanx in advance,
ravi.WHY? I mean, you could rig up some hackneyed process that loads the data into a temp table and parses out the recordset you want, or whatever, but there is just never a good reason for building applications this way. One stored procedure should return one recordset. One function should return one recordset.|||I agree with Blindman 100% on this issue. Stored procedures can return more than one result set. This is to allow for nested procedures that each return their own result sets (like sp_help does). I can't think of any reason that a procedure should be designed to intentionally return more than one result set, other than as a user convenience "wrapper" for a group of other procedures.

-PatP