May 13, 2009 at 3:35 pm
On a production failover cluster the SP3 install will not get past the "awaiting first complete passive cluster node" screen. From looking at the logs this is the part where it trys to create the scheduled tasks on the passive node. I've verified the Task Scheduler Service is running on both nodes and that I can manually create and run a scheduled task from node to node.
I've even detached all user databases and tried, same result.
Tried kicking off the install from both nodes.
Tried to replicate it in a test environment, always works fine in the test environment.
Does anyone have any ideas or seen this issue?
Thanks
May 13, 2009 at 3:41 pm
Do not Stop any Services and Log off from node2, when you are applying SP3 from Node1.
May 13, 2009 at 3:45 pm
No services were stopped and no users were logged into node2.
It's SQL 2005 Standard x64.
May 13, 2009 at 4:10 pm
--
Andrew Hatfield
May 13, 2009 at 4:31 pm
Nothing at all in the System or App event viewer logs.
Yes MSDTC is running.
Nothing in the MSSQL\MSSQL.x\LOG\ log.
Last entries in the SQL Bootstrap logs shown below….
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Hotfix_15.log
Attempting to pause the 32 bit ngen queue
Attempting to pause the 64 bit ngen queue
Installing product: SQL9
Installing instance: ****
Enumerating passive cluster nodes
Patching available passive node: *****
Waiting for first completed passive node
Patching passive node: *****
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary_15.txt
Processes Locking Files
Process Name Feature Type User Name PID
resrcmon.exe SQL Server Native Client Application NA\****** 1876
MSSQL$**** SQL Server Native Client Service 5220
SQLBrowser Database Services Service 2312
SQLWriter Microsoft SQL Server VSS Writer Service NT AUTHORITY\SYSTEM 2372
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply