Remote install fails on second node | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Remote install fails on second node

I have a active/passive cluster. W2K NOS. When I try and install sql on both<br /> the install fails but I am able to install on the local machine. I know the<br /> failure is with the remote install but I am unable to determine error. What<br /> does error 121 mean in my situation. I have all of the accounts setup with <br />the correct permissions and correct network settings. Why would I be losing <br />communication for the install to fail on the remote. NICs seems to be runnin<br />g fine on both servers. I can communicate on the network with both servers a<br />nd to each other. Here is the sql log for the install. I am a newbie so any <br />help would be appreciated. <br /><br /><br />NumRemoteServers=1<br />Server.1=DEINVMGMT2<br />[Server.1]<br />NumRemoteServices=1<br />1.app=\DEINVMGMT1C$SQLINS~1x86setupsetupsql.exe<br />1.server=DEINVMGMT2<br />1.script=\DEINVMGMT1admin$DEINVMGMT2_MSSQLSERVER.iss<br />1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f "\DEINVMGMT1C$SQLINS~1×8<br />6setupsetup.ins" -f1 %s -f2 "\DEINVMGMT2admin$setup.log" -e "stpsilnt._<br />ex" -x "C:"<br />1.user=MTAIREPLANTSYSdmnPlantSystems<br />1.password=0439daabe3<br />1.name=SQLSetup1<br />1.sqlsetup=Y<br />1.copyexe=cnvsvc1.exe<br />15:54:26 Setup is performing required operations on cluster nodes. This may<br /> take a few minutes.<br />15:54:26 C:WINNTTEMPSqlSetupBin
emsetup.exe C:WINNT
emsetup.ini<br />15:55:29 Process Exit Code: (121) The semaphore timeout period has expired.<br /><br />15:55:29 Begin Action : GetRemsetupRetCode<br />15:55:29 Installation return status on DEINVMGMT2 : 121<br />15:55:29 End Action : GetRemsetupRetCode<br />#### SQL Server Remote Setup – Start Time 08/10/04 15:54:26 ####<br /><br />CThreadPool::RunUntilCompleteHlpr create thread, index=0<br />CThread::Run thread [0xa4] created for execution.<br />CThread:<img src=’/community/emoticons/emotion-4.gif’ alt=’:p‘ />rocess [0xa4]<br />CThreadPool::RunUntilCompleteHlpr start thread [0xa4],index=0<br />Script file copied to ‘\DEINVMGMT2ADMIN$DEINVMGMT2_MSSQLSERVER.iss’ succe<br />ssfully.<br /><br />Installing remote service (DEINVMGMT2).<br /><br />An error occured in the service create (DEINVMGMT2): 121.<br /><br />CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0<br />CThreadPool::RunUntilCompleteHlpr signaled thread [0xa4]<br />Thread [0xa4] exit code: [0x79]<br />CThreadPool::RunUntilComplete returned 121<br />CThreadPool::RunUntilComplete execution level=1, need execution: 0<br />One or more errors occurred while running the remote/unattended setups.<br /><br />Disconnecting from remote machine (DEINVMGMT2).<br /><br />Service removed successfully.<br /><br />
I had the same problem. This is a common problem with the install. After a Microsoft support call, the solution from them was to
do the install of the second node from the second node directly
(rather than through the first node). Hope this helps.
quote:Originally posted by stevem123 I had the same problem. This is a common problem with the install. After a Microsoft support call, the solution from them was to
do the install of the second node from the second node directly
(rather than through the first node). Hope this helps.
I was able to install directly to the second node, but it took forever to install. What was Microsoft’s explanation why this happens? I need to know install the service pack. Now do I install the service pack onto the second node or do I fail over the cluster first to the second node then run the service pack update? Thanks for the help.
]]>