Failed to install: Cumulative hotfix package (build 2153) for SQL Server 2005 (KB918222)

Hi experts!

I try to update SQL Server 2005 SP1 with the Cumulative hotfix package (build 2153). I need to do this, because I get an error this hotfix is said to fix... and of course - the update completely crashes (sending an error report to microsoft).

Here is what the log looks like:

Failed ACL:
SetSecurityFileDescriptor is failed at the error code 5; Converted SDDL: '(A;OICI;FA;;;S-1-5-21-1276437202-3579633377-1796755180-1012)'
Error Code: 0x80077342 (29506)
Windows Error Text: Source File Name: sqlca\sqlsddlca.cpp
Compiler Timestamp: Tue Apr 11 11:45:24 2006
Function Name: ExceptionInSDDL
Source Line Number: 65

- Context --

Setting status of unmanaged components and removing unmanaged resources

MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 29506
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user SQL. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.

Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user SQL. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
<Failure Type='Fatal' Error='29506'>
<EndFunc Name='LaunchFunction' Return='29506' GetLastError='0'>
MSI (s) (50:34) [23:18:29:886]: User policy value 'DisableRollback' is 0
MSI (s) (50:34) [23:18:29:886]: Machine policy value 'DisableRollback' is 0
Action ended 23:18:29: InstallFinalize. Return value 3.
MSI (s) (50:34) [23:18:29:964]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=910146116,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (50:34) [23:18:29:964]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (50:34) [23:18:29:964]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (50:34) [23:18:29:964]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (50:34) [23:18:29:964]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e2.rbf)
MSI (s) (50:34) [23:18:29:964]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e3.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e4.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e5.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e6.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlFileSDDL.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Setting File Security,Template=File: [1])
MSI (s) (50:34) [23:18:29:979]: Executing op: ProductInfo(ProductKey={130A3BE1-85CC-4135-8EA7-5A724EE6CE2C},ProductName=Microsoft SQL Server 2005,PackageName=SqlRun_SQL.msi,Language=1033,Version=151062527,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\Setup\,PackageCode={3185FC73-41E0-43F4-97DF-2254C4D7C667},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlUserSecurity.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Setting User Security,Template=Account: [1])
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing Local Groups,)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing Local Groups,)
MSI (s) (50:34) [23:18:29:979]: Executing op: CustomActionRollback(Action=Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlGroupMember,CustomActionData=1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$KMAUSQL01SRV$MSSQLSERVER NT AUTHORITY\LocalService )
MSI (s) (50:68) [23:18:29:995]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICD9.tmp, Entrypoint: Rollback_sqlGroupMember
<Func Name='LaunchFunction'>

I would really be thankful for any hint regarding what to do to solve this problem.... As said - I have an error occuring, this hotfix is said to fix - to be exact, it's the one stating "not to be able to build the execution plan under some circumstances when using a SQL query inside a stored procedure"

Help greatly appreciated!!

Greetings, Wolfgang

Make sure the acct used to startup sqlserver service has read/write access to the folder listed. Also, be sure you login as admin to run setup.

|||

Thanks for your reply oj!

Actually I was logged in as member of the 'Administrators' group... That's what bugged me so much... But as I followed your hint and tried to modify the permissions of the folder manually I immediately got a Windows-Authentication Modal Popup - telling me that I have to authenticate to the domain...

So the problem was that I was local administrator but the hotfix-installation in fact needed mit to be also domain-administrator (don't really understand why though).

I just contacted the Domain-Admin and made him install the hotfix ;-) It worked... Thanks for the hint!

Regards,
Wolfgang

Factorized association

Hello,

Let’s say (for simplicity), in my site you can do one of two things – look at products and buy products.

I want to build an association structure between my products based on those two actions, but(!) when a user looks at two products it creates less important association than when the user actually bought those two products.

So basically, I want to give a different factor base on different actions occurred on my products.

How do I build my structure? How do I query it?

You could also build a single model with two nested tables, one for purchased products and one for browsed products. The browsed products would be input and the purchased input and predict. This would let you answer the question "people who browsed these products bought these products" and "people who purchased these products also purchased these products".

There currently is no way to set a weighting on this, however.

Another option is to simply build two models and interpret the results as you need to on your site.

|||

New, but somewhat similar problem-

Let's say - I’m running a music sharing site where users can rate the songs from 1 to 5.

How do I use this rating in my calculations for associating songs?

Meaning – the association between two songs is stronger when a user rate them both with 5, and weaker (even negative) when the rate is low.

Fact Table Design - Help

Hi There,
I have to build a Fact table, and I have this situation.
My OLTP database, keeps always the last image of the
record.
Table
Incident(IncidentId, CreationTimme, StatusId, PriorityId,
rankId, Description, ..)
My Log Database, keeps a table per field and tracks all
the changes.
Incident_CreationTime(IncidentId, CreationTime, Timestamp)
Incident_StatusId(IncidentId, StatusId, Timestamp)
Incident_PriorityId(IncidentId, PriorityId, Timestamp)
Incident_RankId(IncidentId, RankId, Timestamp)
You got the Idea.
I have to be based on the Log database to create my Fact
Table of Incident. So what's the best way to create the
fact table in this case ? What about the dimension too ?
ThanksWhat are you trying to measure and how are you measuring it "by" ?
These are the inputs to your design, not the existing schema!
"Elie Khammar" <ekhammar@.positron.qc.ca> wrote in message
news:0cd301c3bb40$ec0fb7e0$a401280a@.phx.gbl...

quote:

---

> Hi There,
> I have to build a Fact table, and I have this situation.
> My OLTP database, keeps always the last image of the
> record.
> Table
> Incident(IncidentId, CreationTimme, StatusId, PriorityId,
> rankId, Description, ..)
> My Log Database, keeps a table per field and tracks all
> the changes.
> Incident_CreationTime(IncidentId, CreationTime, Timestamp)
> Incident_StatusId(IncidentId, StatusId, Timestamp)
> Incident_PriorityId(IncidentId, PriorityId, Timestamp)
> Incident_RankId(IncidentId, RankId, Timestamp)
> You got the Idea.
> I have to be based on the Log database to create my Fact
> Table of Incident. So what's the best way to create the
> fact table in this case ? What about the dimension too ?
> Thanks
>

---

|||I'm trying to measure the number of incidents per
Statusid, PriorityId, per RankId.

quote:

---

>--Original Message--
>What are you trying to measure and how are you measuring

---

it "by" ?

quote:

---

>These are the inputs to your design, not the existing

---

schema!

quote:

---

>
>"Elie Khammar" <ekhammar@.positron.qc.ca> wrote in message
>news:0cd301c3bb40$ec0fb7e0$a401280a@.phx.gbl...
PriorityId,[QUOTE]
Timestamp)[QUOTE]
>
>.
>

---

|||You probably forgot about the date dimension. Then your fact table would
look something like:
DateID
StatusID
PriorityID
RankID
IncidentCount
And you would have four dimension tables, Date, Status, Priority, and Rank
each having the descriptive elements of those dimensions, like Date,
StatusDescription, PriorityNumber, RankNumber, or whatever is meaninful for
you for those dimensions.
"Elie Khammar" <ekhammar@.positron.qc.ca> wrote in message
news:067401c3bb4f$b6e6dee0$a001280a@.phx.gbl...[QUOTE]
> I'm trying to measure the number of incidents per
> Statusid, PriorityId, per RankId.
>
> it "by" ?
> schema!
> PriorityId,
> Timestamp)|||Hi Kevin,
Thanks for answering me back. I still have another
question for you.
It's not my first time that I develop a datawarehouse. My
only worry here, is the fact that these tables are related
together as many-to-many relationship in the OLTP system.
So If I do it like you suggested,
(IncidnetNumber, DateId, StatusId, PriorityId, RankId,
IncidentCount)
I could end up for each Incident something like this in my
FACT table:
1, 20031208, 1, 0, 0, 1
1, 20031208, 0, 1, 1, 1
1, 20031208, 4, 0, 0, 1
1, 20031208, 5, 0, 0, 1
Because the StatusId, PriorityId, RankId there is a
possibility that they change so many times during the life
cycle of an incident.
So what I thought to do, is to create a fact table for
each Fact_IncidentStatus, Fact_IncidentPriority,
Fact_IncidentRank each of these fact tables is related to
its own dimension. and then all those fact tables are
related to FACT_Incident which contains only unique
Incident Numbers.
Do you think this is a good design?
Thanks for your time

quote:

---

>--Original Message--
>You probably forgot about the date dimension. Then your

---

fact table would

quote:

---

>look something like:
>DateID
>StatusID
>PriorityID
>RankID
>IncidentCount
>And you would have four dimension tables, Date, Status,

---

Priority, and Rank

quote:

---

>each having the descriptive elements of those dimensions,

---

like Date,

quote:

---

>StatusDescription, PriorityNumber, RankNumber, or

---

whatever is meaninful for

quote:

---

>you for those dimensions.
>
>"Elie Khammar" <ekhammar@.positron.qc.ca> wrote in message
>news:067401c3bb4f$b6e6dee0$a001280a@.phx.gbl...
measuring[QUOTE]
message[QUOTE]
situation.[QUOTE]
all[QUOTE]
Timestamp)[QUOTE]
Fact[QUOTE]
the[QUOTE]
too ?[QUOTE]
>
>.
>

---

|||Elie,
It seems to me that you need to have a separate dimension
for the incident numbers.
You need:
DIM_Date
DIM_Status
DIM_Priority
DIM_Rank
DIM_Incident
And:
FACT_IncidentCount
With a surrogate key from each of your dimensions and a
count field that would contain just the number "1". As
the cube aggregated on each dimension, it would add the
count field up.
Hope this helps,
Asa Monsey

quote:

---

>--Original Message--
>Hi Kevin,
>Thanks for answering me back. I still have another
>question for you.
>It's not my first time that I develop a datawarehouse. My
>only worry here, is the fact that these tables are

---

related

quote:

---

>together as many-to-many relationship in the OLTP system.
>So If I do it like you suggested,
>(IncidnetNumber, DateId, StatusId, PriorityId, RankId,
>IncidentCount)
>I could end up for each Incident something like this in

---

my

quote:

---

>FACT table:
>1, 20031208, 1, 0, 0, 1
>1, 20031208, 0, 1, 1, 1
>1, 20031208, 4, 0, 0, 1
>1, 20031208, 5, 0, 0, 1
>Because the StatusId, PriorityId, RankId there is a
>possibility that they change so many times during the

---

life

quote:

---

>cycle of an incident.
>So what I thought to do, is to create a fact table for
>each Fact_IncidentStatus, Fact_IncidentPriority,
>Fact_IncidentRank each of these fact tables is related to
>its own dimension. and then all those fact tables are
>related to FACT_Incident which contains only unique
>Incident Numbers.
>Do you think this is a good design?
>Thanks for your time
>
>
>fact table would
>Priority, and Rank
dimensions,[QUOTE]
>like Date,
>whatever is meaninful for
>measuring
>message
>situation.
>all
>Timestamp)
>Fact
>the
>too ?
>.
>

---