Page 1 of 1

.MSI Component Table - missing keypath?

Posted: Thu Aug 16, 2012 2:58 pm
by norbertjurkiewicz
Hello Gents,

I have a question about the generated .msi file.
The registry components in the Component table do not have a keypath, is there a reason for that?

This is cuasing ICE validation errors on some strict ICE checks we must pass.

I.E.

Component table row with error

Component..............ComponentId.....................................Directory.....Attributes.....Condition.............KeyPath
ID_5bPWR370_15d......{4A2F5697-1B46-4380-8F98-A9FD3FA1CC84}..SourceDir.....64..............AWR370 = "TRUE"....


Thanks

Re: .MSI Component Table - missing keypath?

Posted: Mon Aug 20, 2012 4:25 am
by FrancescoT
Dear User

We ran the full msi validation suite available in Orca 3.1 on a setup with a number of registry keys, but we was unable to reproduce this error.
Perhaps if you can clarify exactly which validation suite he tried and which Write Registry statements cause the failure in question.

Regards