Difference between revisions of "Error 1722"
From WPKG | Open Source Software Deployment and Distribution
(Description and workaround for Error 1722 (UAC error)) |
m (Add missing </code> and avoid buggy display) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == Error 1722 workaround == | + | <noinclude>== Error 1722 workaround ==</noinclude> |
| − | Windows UAC (User Account Control) can cause the client to fail with a message like the following: | + | 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.'' | ''You must have an administrative privilege to run this tool.'' | ||
| − | This happens even when being launched by an `Administrator' | + | This happens even when being launched by an `Administrator'. The WPKG logs show this: |
<BLOCKQUOTE>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=</BLOCKQUOTE> | <BLOCKQUOTE>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=</BLOCKQUOTE> | ||
| Line 10: | Line 10: | ||
The solution is to launch a command window with elevated privileges and use that to start the installer. Quoting from [http://lists.wpkg.org/pipermail/wpkg-users/2012-April/008727.html one post of many]: | The solution is to launch a command window with elevated privileges and use that to start the installer. Quoting from [http://lists.wpkg.org/pipermail/wpkg-users/2012-April/008727.html one post of many]: | ||
| − | # Make shortcut to cmd.exe | + | '''Install''' |
| + | # Make shortcut to cmd.exe | ||
| + | # Right click on it and select runas administrator | ||
| + | # "cd" to path where installer is, e.g. <code>cd C:\Users\Myname\Downloads</code> | ||
| + | # Run your msiexec command. | ||
| + | ## <code>msiexec /i "WPKG Client 1.3.14-x32.msi"</code> | ||
| + | ## For network, enter full path i.e <code>msiexec /i "\\server1\MyShare\WPKG Client 1.3.14-x32.msi"</code> | ||
| + | |||
| + | '''Install Alt''' | ||
# 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]] | ||
Latest revision as of 17:38, 5 October 2016
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:
Install
- Make shortcut to cmd.exe
- Right click on it and select runas administrator
- "cd" to path where installer is, e.g.
cd C:\Users\Myname\Downloads - Run your msiexec command.
-
msiexec /i "WPKG Client 1.3.14-x32.msi" - For network, enter full path i.e
msiexec /i "\\server1\MyShare\WPKG Client 1.3.14-x32.msi"
-
Install Alt
- 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"