2005 Enterprise sp 2 install fails - 11009

I've had something similar with this. I've found a solution to update SQL Server to SP3. It also works with SP2.

http://www.df5ea.com/index.php/2009/06/prepare-sql-server-2005-in-a-cl...ered-en

> On Thursday, July 17, 2008 3:42 PM frankm wrote:

> 2 Node Cluster SQL Server 2005 Enterprise edition (RTM 1399) fails the sp2
> install with a 11009 failure.
>
> I have enabled the tcp in the config manager.
>
> Anyone have any experience with this?
> I see some references to neeeding domain admin.
> and Netbios and lmhosts settings, but those look like workarounds rather
> that a fix.
>
> Thanks in advance
> frankm


>> On Thursday, July 17, 2008 3:55 PM frankm wrote:

>> Time: 07/17/2008 14:03:30.911
>> KB Number: KB921896
>> Machine: FPDB05P
>> OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service
>> Pack 2 (Build 3790)
>> Package Language: 1033 (ENU)
>> Package Platform: x86
>> Package SP Level: 2
>> Package Version: 3042
>> Command-line parameters specified:
>> Cluster Installation: Yes
>> Log Location on Passive Nodes:
>> (FPDB05P) C:\Program Files\Microsoft SQL Server\90\Setup
>> Bootstrap\LOG\Hotfix
>> (FPDB06P) C:\Program Files\Microsoft SQL Server\90\Setup
>> Bootstrap\LOG\Hotfix
>>
>> **********************************************************************************
>> Prerequisites Check & Status
>> SQLSupport: Passed
>>
>> **********************************************************************************
>> Products Detected Language Level Patch Level
>> Platform Edition
>> Setup Support Files ENU 9.2.3042
>> x86
>> Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00
>> x86 ENTERPRISE
>> Notification Services ENU SP2 9.00.3159.00
>> x86 ENTERPRISE
>> Integration Services ENU SP2 9.00.3159.00
>> x86 ENTERPRISE
>> SQL Server Native Client ENU 9.00.3042.00
>> x86
>> Client Components ENU SP2 9.2.3159
>> x86 ENTERPRISE
>> MSXML 6.0 Parser ENU 6.10.1200.0
>> x86
>> SQLXML4 ENU 9.00.3042.00
>> x86
>> Backward Compatibility ENU 8.05.2004
>> x86
>> Microsoft SQL Server VSS Writer ENU 9.00.3042.00
>> x86
>>
>> **********************************************************************************
>> Products Disqualified & Reason
>> Product Reason
>> Notification Services The product instance NS been
>> patched with more recent updates.
>> Integration Services The product instance Integration
>> Services been patched with more recent updates.
>> Client Components The product instance SQL Tools
>> been patched with more recent updates.
>>
>> **********************************************************************************
>> Processes Locking Files
>> Process Name Feature Type User Name
>> PID
>> msftesql Database Services Service
>> 5456
>> MSSQLSERVER Database Services Service
>> 5136
>> resrcmon.exe Database Services Application USAC\P130420B
>> 3700
>> SQLSERVERAGENT Database Services Service
>> 1636
>> SQLBrowser Database Services Service
>> 1728
>>
>> **********************************************************************************
>> Product Installation Status
>> Product : Setup Support Files
>> Product Version (Previous): 3042
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>> Product : Database Services (MSSQLSERVER)
>> Product Version (Previous): 1399
>> Product Version (Final) :
>> Status : Failure
>> Log File :
>> Error Number : 11009
>> Error Description : No passive nodes were successfully patched
>> ----------------------------------------------------------------------------------
>> Product : Notification Services
>> Product Version (Previous): 3159
>> Product Version (Final) :
>> Status : NA
>> Log File :
>> Error Description : The product instance NS been patched with more
>> recent updates.
>> ----------------------------------------------------------------------------------
>> Product : Integration Services
>> Product Version (Previous): 3159
>> Product Version (Final) :
>> Status : NA
>> Log File :
>> Error Description : The product instance Integration Services been
>> patched with more recent updates.
>> ----------------------------------------------------------------------------------
>> Product : SQL Server Native Client
>> Product Version (Previous): 3042
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>> Product : Client Components
>> Product Version (Previous): 3159
>> Product Version (Final) :
>> Status : NA
>> Log File :
>> Error Description : The product instance SQL Tools been patched with
>> more recent updates.
>> ----------------------------------------------------------------------------------
>> Product : MSXML 6.0 Parser
>> Product Version (Previous): 1200
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>> Product : SQLXML4
>> Product Version (Previous): 3042
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>> Product : Backward Compatibility
>> Product Version (Previous): 2004
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>> Product : Microsoft SQL Server VSS Writer
>> Product Version (Previous): 3042
>> Product Version (Final) :
>> Status : Not Selected
>> Log File :
>> Error Description :
>> ----------------------------------------------------------------------------------
>>
>> **********************************************************************************
>> Summary
>> No passive nodes were successfully patched
>> Exit Code Returned: 11009
>>
>>
>> "Denny Cherry" wrote in message
>>


>>> On Thursday, July 17, 2008 3:55 PM Denny Cherry wrote:

>>> What are the errors in your install log?
>>>
>>> Denny
>>>
>>> wrote:


>>>> On Thursday, July 17, 2008 4:16 PM ekre wrote:

>>>> Did you see this one?
>>>>
>>>> http://www.eggheadcafe.com/software/aspnet/29753567/sql-server-2005-sp...aili.as
>>>>
>>>> --
>>>> Ekrem ?nsoy


>>>>> On Thursday, July 17, 2008 5:05 PM frankm wrote:

>>>>> Yep, thanks...
>>>>> The MSDTC was already in the cluster group when I first was hit by 11009.
>>>>> I tried deleting the MSDTC from the cluster group and recreating the MSDTC
>>>>> in the sql goup and that was no joy.
>>>>> So I re-created it in the cluster gorup and left it there.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Ekrem ?nsoy" wrote in message
>>>>>


>>>>>> On Friday, July 18, 2008 5:54 AM changli wrote:

>>>>>> Hi Frankm,
>>>>>> Could you please also check if there were any error messages in your System
>>>>>> Event log? I often see this issue when SQL Server Browser Services was not
>>>>>> started on the two servers. There are some similar issues on Microsoft
>>>>>> forum. You may refer to:
>>>>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2929900&SiteID=1
>>>>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=331406&SiteID=1
>>>>>>
>>>>>> Hope this helps. If you have any other questions or concerns, please feel
>>>>>> free to let me know.
>>>>>>
>>>>>> Best regards,
>>>>>> Charles Wang
>>>>>> Microsoft Online Community Support
>>>>>> ===========================================================
>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>> comments and suggestions about how we can improve the
>>>>>> support we provide to you. Please feel free to let my manager
>>>>>> know what you think of the level of service provided. You can
>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>> ===========================================================
>>>>>> Get notification to my posts through email? Please refer to
>>>>>> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>>>>>> ications.
>>>>>>
>>>>>> Note: The MSDN Managed Newsgroup support offering is for
>>>>>> non-urgent issues where an initial response from the community
>>>>>> or a Microsoft Support Engineer within 1 business day is acceptable.
>>>>>> Please note that each follow up response may take approximately
>>>>>> 2 business days as the support professional working with you may
>>>>>> need further investigation to reach the most efficient resolution.
>>>>>> The offering is not appropriate for situations
>>>>>> that require urgent, real-time or phone-based interactions or complex
>>>>>> project analysis and dump analysis issues. Issues of this nature are best
>>>>>> handled working with a dedicated Microsoft Support Engineer by
>>>>>> contacting Microsoft Customer Support Services (CSS) at
>>>>>> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>>>>>> ============================================================
>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>> =========================================================


>>>>>>> On Friday, July 18, 2008 8:19 AM frankm wrote:

>>>>>>> I checked the system event log, there are no errors that wourld tell me
>>>>>>> there were any services issues.
>>>>>>>
>>>>>>> I checked both SQL Server browser services in services control manager,they
>>>>>>> are both running.


>>>>>>>> On Monday, July 21, 2008 4:18 AM changli wrote:

>>>>>>>> Hi Frankm,
>>>>>>>> Thank you for your clarification.
>>>>>>>>
>>>>>>>> For further research, could you please mail me (changliw_at_microsoft_dot_com) your SQL
>>>>>>>> Server 2005 SP2 setup logs that are located in the folder "C:\Program Files\Microsoft SQL
>>>>>>>> Server\90\Setup Bootstrap\LOG\Hotfix"? If the total size is large, I recommend that you first
>>>>>>>> mail me an email response and then I will create a workspace and let you know how to upload
>>>>>>>> the file.
>>>>>>>>
>>>>>>>> Also from my research, as a possible workaround, I recommend that you try installing SQL
>>>>>>>> Server 2005 SP2 separately on the two nodes according to the following steps to see if it helps:
>>>>>>>> 1. Failover all resource group to your current Active node and stop Cluster Services on your
>>>>>>>> passive node;
>>>>>>>> 2. Install SQL Server 2005 SP2 on the active node;
>>>>>>>> 3. After you install the SP2 on the active node, manually failover your Active to Passive node
>>>>>>>> and reboot the previous Active node;
>>>>>>>> 4. Repeat same procedure as above to the current active node.
>>>>>>>>
>>>>>>>> Before you take these actions, please first copy out your previous SQL Server 2005 SP2 setup
>>>>>>>> logs so that I can look into them for more detailed view if the above method does not work for
>>>>>>>> you.
>>>>>>>>
>>>>>>>> If you have any other questions or concerns, please feel free to let me know. It is my pleasure
>>>>>>>> to be of assistance.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Charles Wang
>>>>>>>> Microsoft Online Community Support
>>>>>>>> =========================================================
>>>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>>>> comments and suggestions about how we can improve the
>>>>>>>> support we provide to you. Please feel free to let my manager
>>>>>>>> know what you think of the level of service provided. You can
>>>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>>>> =========================================================
>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>> =========================================================


>>>>>>>>> On Monday, July 21, 2008 8:49 AM frankm wrote:

>>>>>>>>> Sending log fles. Thank you!!!


>>>>>>>>>> On Monday, July 21, 2008 8:51 AM frankm wrote:

>>>>>>>>>> BTW - do you know what setup was doing and the time of the 11009?
>>>>>>>>>>
>>>>>>>>>> What does error 11009 specificall mean?


>>>>>>>>>>> On Tuesday, July 22, 2008 3:11 AM changli wrote:

>>>>>>>>>>> Hi Frankm,
>>>>>>>>>>> Thank you for your response.
>>>>>>>>>>>
>>>>>>>>>>> The error 11009 means "No passive nodes were successfully patched". From the hotfix setup logs
>>>>>>>>>>> you sent to me, I found the following error messages:
>>>>>>>>>>> 1. Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
>>>>>>>>>>> GetServiceUserGroup failed for MSSQLSERVER, 5
>>>>>>>>>>> Error Code: 0x80070534 (1332)
>>>>>>>>>>>
>>>>>>>>>>> Windows Error Text: No mapping between account names and security IDs was done.
>>>>>>>>>>>
>>>>>>>>>>> 2. Failed to find installation media path due to datastore exception in FindSetupFolder()
>>>>>>>>>>>
>>>>>>>>>>> From the two error messages, it seems that this issue is most likely related to permission and your
>>>>>>>>>>> SP2 installation path. Based on the two error messages, I would like to ask you two questions:
>>>>>>>>>>> 1. Was your SQL Server service account a domain administrator account?
>>>>>>>>>>> You can check this from Services list. Double click your SQL Server services, switch to the Log On
>>>>>>>>>>> tab and you can find the service account. If it is not a domain administrator, try changing it to a
>>>>>>>>>>> domain administrator on each node to see if it helps.
>>>>>>>>>>>
>>>>>>>>>>> 2. How did you install your SQL Server 2005 SP2, locally from your active node or remotely from a
>>>>>>>>>>> network share folder?
>>>>>>>>>>> If you installed your SQL Server 2005 SP2 from a network share, I recommend that you try
>>>>>>>>>>> removing the Hotfix folder and installing the patch only from your active node.
>>>>>>>>>>> If the SP2 patch installation media was on your active node, please check what the result is if
>>>>>>>>>>> you specify a domain administrator account for "Remote User Account" during the SP2 installation.
>>>>>>>>>>>
>>>>>>>>>>> Hope this helps. If you have any other questions or concerns. Have a nice day!
>>>>>>>>>>>
>>>>>>>>>>> Best regards,
>>>>>>>>>>> Charles Wang
>>>>>>>>>>> Microsoft Online Community Support
>>>>>>>>>>> =========================================================
>>>>>>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>>>>>>> comments and suggestions about how we can improve the
>>>>>>>>>>> support we provide to you. Please feel free to let my manager
>>>>>>>>>>> know what you think of the level of service provided. You can
>>>>>>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>>>>>>> =========================================================
>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>>>>> =========================================================


>>>>>>>>>>>> On Tuesday, July 22, 2008 8:21 AM frankm wrote:

>>>>>>>>>>>> Thank you for your help and your quick response.
>>>>>>>>>>>>
>>>>>>>>>>>> 1) Q...Was your SQL Server service account a domain administrator account?
>>>>>>>>>>>> A...Having a SQL Server service account as a domain admin? I know that the
>>>>>>>>>>>> service account is not a domain admin.
>>>>>>>>>>>> Are you sure on that. This one big no-no in my world. Huge security issue.
>>>>>>>>>>>>
>>>>>>>>>>>> 2) Q...How did you install your SQL Server 2005 SP2, locally from your
>>>>>>>>>>>> active node or remotely from a network share folder?
>>>>>>>>>>>> A...Locally with the SP files and running the install on the node that owns
>>>>>>>>>>>> the SQL Server resource group.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Q...If the SP2 patch installation media was on your active node, please
>>>>>>>>>>>> check what the result is if you specify a domain administrator account for
>>>>>>>>>>>> "Remote User Account" during the SP2 installation.
>>>>>>>>>>>> A...My question is: why would I need to specify a domain admin to do a
>>>>>>>>>>>> allegedly simple service pack?
>>>>>>>>>>>> What priveleges are necessary if I can't get a domain admin?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ""Charles Wang [MSFT]"" wrote in message
>>>>>>>>>>>>


>>>>>>>>>>>>> On Wednesday, July 23, 2008 6:38 AM changli wrote:

>>>>>>>>>>>>> Hi Frankm,
>>>>>>>>>>>>> Thank you for your response.
>>>>>>>>>>>>>
>>>>>>>>>>>>> For the reason why I recommend that you try a domain admin account is to avoid any potential permission issues on some registry keys or some
>>>>>>>>>>>>> unaware system folders. Once you finished installing SQL Server 2005 SP2, you may change it back to your normal user.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Also I reviewed the hotfix log and found the following error message:
>>>>>>>>>>>>> 07/18/2008 08:00:13.126 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
>>>>>>>>>>>>> 07/18/2008 08:00:13.142 Registry: Cannot read registry key value "Debug"
>>>>>>>>>>>>> 07/18/2008 08:00:20.580 MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal
>>>>>>>>>>>>> error during installation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As you can see that there was indeed some registry key that cannot be read during the installation, however due to environment specific, it is
>>>>>>>>>>>>> hard for us to answer what caused this issue. Based on the error message, I found the following KB article:
>>>>>>>>>>>>> Error message when you try to install a SQL Server 2005 service pack or a SQL Server 2005 hotfix package: "Error 29528. The setup has
>>>>>>>>>>>>> encountered an unexpected error while Setting Internal Properties"
>>>>>>>>>>>>> http://support.microsoft.com/kb/925976/en-us
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think that this KB article addresses the reason for this issue. However the workaround will produce a big business impact on your server since
>>>>>>>>>>>>> you need to reinstall your SQL Server 2005 failover cluster instance. So my opinion is that you may try first installing SQL Server 2005 SP2 by
>>>>>>>>>>>>> changing your SQL Server service account to a domain administrator to see if it helps. If this issue can be resolved in this way, that is fine;
>>>>>>>>>>>>> otherwise I am afraid that you have to reinstall your SQL Server 2005 clustered instance before you apply SQL Server 2005 service pack.
>>>>>>>>>>>>> Remember to backup all of your databases before you take the action.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hope this helps. If you have any other questions or concerns, please feel free to let me know. I am very glad to work with you for further
>>>>>>>>>>>>> assistance.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>> Charles Wang
>>>>>>>>>>>>> Microsoft Online Community Support
>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>>>>>>>>> comments and suggestions about how we can improve the
>>>>>>>>>>>>> support we provide to you. Please feel free to let my manager
>>>>>>>>>>>>> know what you think of the level of service provided. You can
>>>>>>>>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>>>>>>> =========================================================


>>>>>>>>>>>>>> On Wednesday, July 23, 2008 8:24 AM frankm wrote:

>>>>>>>>>>>>>> Thanks you very much!
>>>>>>>>>>>>>> I will look at these and try to see if I can get a domain admin.
>>>>>>>>>>>>>> What priveleges does the login need if I cannot get a full domain admin?


>>>>>>>>>>>>>>> On Thursday, July 24, 2008 6:11 AM changli wrote:

>>>>>>>>>>>>>>> Hi Frankm,
>>>>>>>>>>>>>>> It is hard to answer what exactly priveleges does the login need for your current situation.
>>>>>>>>>>>>>>> Basically if the domain account is a local administrator on both of your two cluster nodes, that is
>>>>>>>>>>>>>>> fine. However as we can see that your domain account did not work here. My suggestion is that
>>>>>>>>>>>>>>> if it is possible, use a domain admin; if not possible, try creating a new domain user and assign
>>>>>>>>>>>>>>> it to local administrators on your two cluster nodes. Set the cluster services, SQL Server service
>>>>>>>>>>>>>>> account to the new domain user; run your SQL Server 2005 SP2 installation as the new domain
>>>>>>>>>>>>>>> user.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If this still could not work, I recommend that you use the workaround mentioned in the KB article.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please feel free to let me know if you have any other questions or concerns. It is my pelasure to
>>>>>>>>>>>>>>> be of assistance.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>> Charles Wang
>>>>>>>>>>>>>>> Microsoft Online Community Support
>>>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>>>>>>>>>>> comments and suggestions about how we can improve the
>>>>>>>>>>>>>>> support we provide to you. Please feel free to let my manager
>>>>>>>>>>>>>>> know what you think of the level of service provided. You can
>>>>>>>>>>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>>>>>>>>> =========================================================


>>>>>>>>>>>>>>>> On Wednesday, July 30, 2008 6:06 AM changli wrote:

>>>>>>>>>>>>>>>> Hi Frankm,
>>>>>>>>>>>>>>>> Just check with you to see what everything is going on regarding this issue.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> If you have any further questions or concerns, please feel free to let me know. I am very
>>>>>>>>>>>>>>>> glad to work with you for further assistance.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>>> Charles Wang
>>>>>>>>>>>>>>>> Microsoft Online Community Support
>>>>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>>>>> Delighting our customers is our #1 priority. We welcome your
>>>>>>>>>>>>>>>> comments and suggestions about how we can improve the
>>>>>>>>>>>>>>>> support we provide to you. Please feel free to let my manager
>>>>>>>>>>>>>>>> know what you think of the level of service provided. You can
>>>>>>>>>>>>>>>> send feedback directly to my manager at: msdnmg.RemoveThis@microsoft.com.
>>>>>>>>>>>>>>>> =========================================================
>>>>>>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>>>>>>>>>> =========================================================


>>>>>>>>>>>>>>>>> On Wednesday, October 08, 2008 4:36 AM Pau wrote:

>>>>>>>>>>>>>>>>> Hi, I have exactly the same issue been through all the suggestions here to no
>>>>>>>>>>>>>>>>> avail except reinstall SP2 which i am not hopeful about as i suspect the same
>>>>>>>>>>>>>>>>> issue would arise again. Charles did you find a solution to this?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ""Charles Wang [MSFT]"" wrote:


>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>>>>>>> ObjectDumper LINQ To Export Collection Via .NET Reflection
>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/21737599-5a63-4672-a32c-a3...a282a3f
 >> Stay informed about: 2005 Enterprise sp 2 install fails - 11009