Difference between revisions of "Error 1722"
From WPKG | Open Source Software Deployment and Distribution
m |
|||
| Line 12: | Line 12: | ||
# Make shortcut to cmd.exe, click on it with right button and select runas admin, then "cd" to path where installer is and run your msiexec command. | # Make shortcut to cmd.exe, click on it with right button and select runas admin, then "cd" to path where installer is and run your msiexec command. | ||
# For install across network or localy use "psexec" from Systeminternals with localhost and "-h" parameters, eg. "psexec -h localhost msiexec /le wpkg_error.txt /i WPKG_Client_1.3.14-x64.msi" | # For install across network or localy use "psexec" from Systeminternals with localhost and "-h" parameters, eg. "psexec -h localhost msiexec /le wpkg_error.txt /i WPKG_Client_1.3.14-x64.msi" | ||
| + | |||
| + | |||
| + | [[Category: Other]] | ||
Revision as of 04:49, 27 March 2013
Error 1722 workaround
Windows UAC (User Account Control) can cause the client installation to fail with a message like the following:
You must have an administrative privilege to run this tool.
This happens even when being launched by an `Administrator'. The WPKG logs show this:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _A9459942_EE79_497A_9080_F39DDA8A7B80, location: C:\Program Files\wpkg\wpkginst.exe, command: --SETTINGSFILE=
The solution is to launch a command window with elevated privileges and use that to start the installer. Quoting from one post of many:
- Make shortcut to cmd.exe, click on it with right button and select runas admin, then "cd" to path where installer is and run your msiexec command.
- For install across network or localy use "psexec" from Systeminternals with localhost and "-h" parameters, eg. "psexec -h localhost msiexec /le wpkg_error.txt /i WPKG_Client_1.3.14-x64.msi"