This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: ICACLS fails on Windows temp folder
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 16, 2011
07:12 AM
ICACLS fails on Windows temp folder
Hi,
I am running a custom action setting folder permissions on the windows temp directory. This is my command:
icacls.exe %WINDIR%\Temp /grant "NETWORK SERVICE":RD
The installer fails with error 1722 on some systems:
Note: 1: 1722 2: SetFolderPerms 3: C:\Windows\SysWOW64\ 4: "C:\Windows\SysWOW64\cmd.exe" /c "C:\Program Files (x86)\MYPROGRAM\SetFolderPermissions.bat"
Running the installer from the command prompt sometimes resolves the problem, which leads me to believe that the installer needs Administrative rights to succeed, but I am not sure.
What could be the cause, and what should I do to resolve it.
I will buy a fictive beer for whoever saves my behind 🙂
Thank you!
I am running a custom action setting folder permissions on the windows temp directory. This is my command:
icacls.exe %WINDIR%\Temp /grant "NETWORK SERVICE":RD
The installer fails with error 1722 on some systems:
Note: 1: 1722 2: SetFolderPerms 3: C:\Windows\SysWOW64\ 4: "C:\Windows\SysWOW64\cmd.exe" /c "C:\Program Files (x86)\MYPROGRAM\SetFolderPermissions.bat"
Running the installer from the command prompt sometimes resolves the problem, which leads me to believe that the installer needs Administrative rights to succeed, but I am not sure.
What could be the cause, and what should I do to resolve it.
I will buy a fictive beer for whoever saves my behind 🙂
Thank you!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 17, 2011
04:34 PM
UI Sequenec and Immediate Execute Sequence don't get privilege elevation. Set your custom action to run in Deferred (Execute) Sequence. Or set it to Deferred (Execute) Sequence in System Context if it should run without impersonation. For further explanation, please refer to Installation Phases and In-Script Execution Options for Custom Actions in Windows Installer.