Hi Everyone,

I'm having a heck of a time trying to get KB954606 to install on our two SQL
2005 clusters. First it wouldn't install via WU so I downloaded it and went
to do it manually. Everything appears to go just fine and then at the very
end you get the dreaded rollback action and then the failure summary shows;

Error Description: MSP Error: 29512 SQL Server Setup was unable add user NT
AUTHORITY\SYSTEM to local group DOMAINNAME\MSSQL2005 Services.

I'm using a domain admin account to install the update. Why is it trying to
add NT AUTHORITY\SYSTEM to a domain group when it says "local" group in the
display?

If you re-run the update everything besides the SQL instances say they have
been upgraded.

Looking at the servers, whomever configured these SQL clusters from the
start has the services starting under Local System and are not using a
service account. Would changing SQL to use a service account potentially fix
this?

From the install log I see the following;

MSI (s) (24!10) [19:01:17:579]: PROPERTY CHANGE: Adding
Rollback_sqlGroup.D20239D7_E87C_40C9_9837_E70B8D48 82C2 property. Its value
is '1
0
0
Installing Local Groups
50000
DOMAINNAME\MSSQL2005 Services
'.
MSI (s) (24!10) [19:01:17:579]: Doing action:
Rollback_sqlGroup.D20239D7_E87C_40C9_9837_E70B8D48 82C2

Thanks in advance!

Hi Brian, you might want to try the workarounds posted in these threads:

http://tinyurl.com/7h9rg4

http://tinyurl.com/7lge5h

http://tinyurl.com/ay2l3b

They aren't specific to that hotfix but the underlying symptom and/or
resolution may be the same.

(And FWIW I too have had problems installing post-SP2 hotfixes on clusters,
though with different error messages.)

A






On 1/4/09 7:21 PM, in article
1EAD4C0B-6FD6-486B-BE0C-35F86D207508...soft (DOT) com, "Brian Day"
<bdaytech (AT) verizon (DOT) net> wrote:

Hi Aaron,

Thank you for the suggestions. I'll check them out and see if something
works. I re-ran the install once more while logged in as a local admin
account and the same problem happened. Hopefully something here will make it
stick.

-brian

"Aaron Bertrand [SQL Server MVP]" <ten.xoc (AT) dnartreb (DOT) noraa> wrote

Hi Brian,

I'm facing exaclty the same issue. Did you managed to find any solution?

Thanks

Michal

"Brian" wrote:

Are your distmdl files in the same location as your master database files? If
they are not this can cause patches to fail.

I suspect on a cluster the 2nd node will have to be cluster owner for this
patch to install correctly. I have not tested this assumption yet.