Help Required!!!! Damn Urgent
I'm getting an ICE 38 error and its nt getting resolved by applying all means:: it states the following
ICE38 Error Component MAINDATA.HLP installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. Component Attributes MAINDATA.HLP
Now Sumbody please temme how to go about it.
I have to finish this package nehow by 2pm...pleaseeeeeeeeeee
ICE38 Error Component MAINDATA.HLP installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. Component Attributes MAINDATA.HLP
Now Sumbody please temme how to go about it.
I have to finish this package nehow by 2pm...pleaseeeeeeeeeee
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
timmsie
14 years ago
Posted by:
thugz888
14 years ago
Hi Devil
In order to resolve this problem the component must have a keypath referencing to a registry key not the file itself because the file is installed to USER profile. If you don't have any registy on Component MAINDATA.HLP that's under HKCU try to create a dummy registry and make it a keypath.
In order to resolve this problem the component must have a keypath referencing to a registry key not the file itself because the file is installed to USER profile. If you don't have any registy on Component MAINDATA.HLP that's under HKCU try to create a dummy registry and make it a keypath.
Posted by:
cygan
14 years ago
Posted by:
Devil
14 years ago
Posted by:
pjgeutjens
14 years ago
LockPermissions LockObject BORLAND CreateFolder Users
2 options,
If you actually want your msi to set security on the BORLAND folder (merge module maybe?) open the CreateFolder table and see why the folder BORLAND is missing.. perhaps it's in the Directory table instead.
If you don't want/need to set this security, delete the line in the LockPermissions table.
In any case beware that settings in the LockPermissions table will completely replace existing permissions, so use with care!!
PJ
Posted by:
anonymous_9363
14 years ago
Also, if you must use LockPermissions, remember that you must either use the correct account or group name according to the locale or use well-known SIDs for the account or group. For example, the group 'Administrators' will be ignored on machines set up to use a non-English locale. For example, machines set up to use French it would need to be 'Administrateurs'.
Most people use a command line tool like SetACL, XCACLS, SubInACL or SecEdit via a Custom Action for setting permissions, since by default they add permissions rather than replace them.
Most people use a command line tool like SetACL, XCACLS, SubInACL or SecEdit via a Custom Action for setting permissions, since by default they add permissions rather than replace them.
Posted by:
timmsie
14 years ago
They've fixed it in windows installer 5 apparantly!!
http://blogs.msdn.com/windows_installer_team/archive/2009/03/05/enhanced-permissions-setting-with-windows-installer-5-0.aspx
I've not tried it yet but it'll be interesting to se how it works
http://blogs.msdn.com/windows_installer_team/archive/2009/03/05/enhanced-permissions-setting-with-windows-installer-5-0.aspx
I've not tried it yet but it'll be interesting to se how it works
Posted by:
rkava
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.