I am getting the following error while validating the mst package.

Value below MinValue; Table: LockPermissions, Column: Permission, Key(s): HCL_HOME_ROOT.CreateFolder.[%USERDOMAIN].[APPGROUP] ice03.html LockPermissions Permission HCL_HOME_ROOT CreateFolder [%USERDOMAIN] [APPGROUP]
Evaluation: ICE03

Help me to resolve the error
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


In what amounts to a direct contradiction of my normal advice, i.e. to fix problems and not work around them, I'd suggest that you abandon the use of the LockPermissions table. No-one in their right mind uses it. Instead, use one of the many, much more flexible third-party tools to do that via a Custom Action.

My own preference is for SetACL (because the one tool can do file and registry permissioning) but there's XCACLS, SubInACL and, of course, the built-in SecEdit.
Answered 06/05/2008 by: VBScab
Red Belt

Please log in to comment
Instead of using lock permission i will suggest to use custom action to give permission.
Answered 06/05/2008 by: packengg
Orange Belt

Please log in to comment

Wasn't that what Ian (VBScab) just suggested?

However, there shouldn't be a problem using the LockPermissions table if you are certain that it's only your single package that is going to use that file, registry or folder. Just have in mind that it will replace the ACL on the object.
Answered 06/05/2008 by: AngelD
Red Belt

Please log in to comment