I am getting the following during my project install: CustomAction ISLockPermissionsCost returned actual error code 1603.
I have my Locked-Down Permissions set to Custom InstallShield handling
I figure it has to do with a few folder permissions that we have to set. Maybe they were not set correctly. So if anyone can see anything wrong with the permission settings could you let me know.
Here is what we have: We create some folders under [ALLUSERSPROFILE]CompanyName\Product\Config and UL. The Config and UL folders have the permissions set on them They are set as follows:
Name(s): Domain - [%USERDOMAIN] User - Everyone
Permissions: Modify Read & Execute List Folder Contents Read Write
Now if any of these are incorrectly set or something else is completely wrong then could someone point out the mistake?
These settings don't appear to have any issues at first glance.
A verbose log of the install would be recommended in this scenario as the ISLockPermissionsInstall custom action will usually log the reason or associated system error that can help isolate the cause of the behavior.
I got this error when I defined some permissions, but then ended up moving some components to different directories. It seemed to hose it up...
So I went into the direct editor, deleted all of the entries in ISLockPermissions table then recreated them in the setup view and it seems to be ok now.
