Active Active 2nd instance setup woes | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Active Active 2nd instance setup woes

Hi,<br />We installed our cluster a few months back and setup the first SQL instance fine and well.<br />We created the first instance as Named Instance (not default as seems to be most common menthod) <b>SQLVS1SQL2005INST1</b>. We also upgraded this SQL instance to SP2.<br />We also created our second instance as on second virtual server <b>SQLVS2SQL2005INST2</b> with its own disk arrays.<br /><br />Now to install our second SQL instance, we logged onto the second physical node and ran through the SQL installation wizard..<br /><br />Only the <i>WS components, books online, devt tools </i> were installed on this node, so we selected all other components except <i>analysis services</i>.<br /><br />At the Setup Progress page a couple of ‘products’ failed (think from memory were <i>’SQL Server Database Services’ </i> and <i>’reporting services'</i>).<br /><br />We couldn’t progress any further with installation so used add/remove programs to remove the second instance. On our second attempt to setup we had <i>’Pending Reboot Requirement (Error)'</i> so rebooted this 2nd node.<br />This seems to have made our disk arrays for the 2nd node disappear from cluster, and also this node is unable to see the Quorum or node1 disk arrays now either <img src=’/community/emoticons/emotion-6.gif’ alt=’:(‘ /><br /><br />Does anybody have any ideas as to where we may have gone wrong or best way to remedy problems?
Alight – we found the reason the Quorum drives etc were appearing was we had to restart the 1st node as well <img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br />This error crops up a bit from the logs of ‘SQL Server Database Services – Refer to setup log for details.'<br /><i>MSI (s) (2C:94) [15:30:19:028]: Note: 1: 2262 2: Error 3: -2147287038 </i><br /><br /><b>the event viewer has the following errors:</b><br /><br />Product: Microsoft SQL Server 2005 (64-bit) – Update ‘Hotfix 3024 for SQL Server Database Services 2005 (64-bit) ENU (KB000000)’ could not be installed. Error code 1603. Additional information is available in the log file C:program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0017_WRSV-CLUS1B_SQL.log.<br /><br /><br />Product: Microsoft SQL Server 2005 (64-bit) — Error 29550. The setup has encountered an error while Upgrading Components. The error: -2147019873<br />Error message: The group or resource is not in the correct state to perform the requested operation.<br /><br /><b>and the following group of 3 errors cycling 6 times within about 90seconds:</b><br />[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.<br /><br />[sqsrvres] ODBC sqldriverconnect failed<br /><br />[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired<br /><br /><br /><br /><br />we are thinking maybe our problem is due to the first instance being SP2, and our installation being SP1.<br /><i>The Edition Change Check warning we got during the prerequisite check was ‘to change and exisitn ginstance of MS SQL server 2005 to a different edition of SQL server 2005, you must run SQL server 2005 setup from the command prompt and include the SKUUPGRADE=1 parameter</i><br /><br />Looking this up on google it seems others who ran with the parameter didn’t resolve their problem [<img src=’/community/emoticons/emotion-6.gif’ alt=’:(‘ />]
This is the default behavior of SQL Server 2005. You can change this by using the Surface Area Configuration tool. So check whether it has been changed there in addition to relevant protocols are enabled.
Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Thanks for the reply Satya.<br /><br />We managed to get it up and running… Think the main thing holding us back was we were attempting the install with a ‘Cluster’ account we made which had all the SQL Admins grou ppermissions.<br />It didn’t have Enterprise Admins and Schema Admins permissions and when we tried the install with an ac**** with both these group memberships it worked [<img src=’/community/emoticons/emotion-2.gif’ alt=’:D‘ />]
Hello Satya,
Iam also getting the same error, But what exactly I should do in Surface area configuration?
could you plz tell me the steps to do in surface area configuration?

WHat is the service pack level on SQL Server?
Also when you are getting thsi error?

The service pack is SP2. And Iam getting this error exactly while the message "starting services mssqlserverINS1" on the setup wizard, and it is waiting for couple of mintes ,then its giving the error:
Product: Microsoft SQL Server 2005 (64-bit) — Error 29550. The setup has encountered an error while Upgrading Components. The error: -2147019873
Error message: The group or resource is not in the correct state to perform the requested operation.
any help would be appreciated