It was weekend and as usual I am in office with lots of patching scheduled this weekend and guess what, patching start failing with no. of unknown issues. Among them one of patching took by my colleague \ guide failed with below error in C:\Program Files\Microsoft SQL Server\100\Setup bootstrap\Log\Summary.txt .
/**************log file says******************************/
User Input Settings:ACTION: Patch
ALLINSTANCES: False
CLUSTERPASSIVE: False
CONFIGURATIONFILE:
ENU: False
FARMACCOUNT: < empty>
FARMADMINPORT: 0FARMPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTANCEID: < empty>
INSTANCENAME: < empty>PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: False
UIMODE:
X86: False
/********************************************/
Action: As my initial investigation I checked cluadmin and made sure all resources are visible in cluadmin from node (P).
To our surprise we found none of these values are there in registry. As well we have use this SP2 setup earlier also so no chance of corrupt setup.
We also thought of trying failover from active to passive manually to check if everything is fine @ Node (P) or we might get some more details but idea was discouraged as this is very critical production server and even in maintenance window we were authorized for single failover.
The only thought we have in mind was definitely there is a issue in registry files so we plan to compare registry settings of both nodes. And when DBA tried to login on active node we got our answer Ahha Permission issue. DBA login doesn’t have permission to RDP Active node. It was like half battle is done.
We tried different windoes nt login now which have access to active node and passive node both and re-run patching in passive node, Hurray patching runs smooth. Log file says Patching completed successfully and its time to jump on other patching issues.
Observation:
Worked for me, Thanks sir
ReplyDelete