Template install MSI error

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
HugoDams
Messages: 11
Registration: July 18, 2022 - 11:11
Location: Le Mans

July 18, 2022 - 11:55

Good morning,
I work on WAPT 2.2, installed on a Windows VM. I design and test packages in a Windows VM dedicated to their development.
I wanted to use the WAPT utility to create a package to install an MSI. Before finalizing the creation, I used PyScripter to make sure everything was correct.
So the package is very basic, it looks like this:

Code: Select all

def install():
    # Declaring local variables

    # Installing the software
    print("Installing: ATLAS 9.81.2.msi")
    install_msi_if_needed('ATLAS 9.81.2.msi')

When I run WAPT: install Here is what the Python interpreter returns:

Code: Select all

*** Remote Interpreter Reinitialized ***
Command Line : install "c:\waptdev\dams-atlas9_9.81.2.200-1_windows_PROD-wapt\WAPT\.."
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
Installing WAPT files c:\waptdev\dams-atlas9_9.81.2.200-1_windows_PROD-wapt
Installing: ATLAS 9.81.2.msi
2022-07-18 10:24:22,146 CRITICAL Fatal error in install script: CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "ATLAS 9.81.2.msi" ' returned non-zero exit status 1603.
Output::
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4035, in install_wapt
    exitstatus = setup.install()
  File "c:\waptdev\dams-atlas9_9.81.2.200-1_windows_PROD-wapt\setup.py", line 16, in install
    install_msi_if_needed('ATLAS 9.81.2.msi')
  File "C:\Program Files (x86)\wapt\common.py", line 3990, in new_func
    return func(*args, **kwargs)
  File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 1501, in install_msi_if_needed
    run(r'msiexec /norestart /q /i "%s" %s' % (msi, props), accept_returncodes=accept_returncodes, timeout=timeout, pidlist=pidlist)
  File "C:\Program Files (x86)\wapt\waptutils.py", line 2126, in run
    raise CalledProcessErrorOutput(proc.returncode, cmd, ''.join(output))
waptutils.CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "ATLAS 9.81.2.msi" ' returned non-zero exit status 1603.
Output:

FATAL ERROR : CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "ATLAS 9.81.2.msi" ' returned non-zero exit status 1603.
Output:
Exit code:  3

I would like to understand what I did wrong, or what I didn't do, that made it not work.
Thank you for your help, I hope I've been clear
Hugo
Last edited by HugoDams on Jul 26, 2022 - 11:48, edited 2 times.
alain17
Messages: 24
Registration: June 17, 2022 - 07:32

July 18, 2022 - 1:53 PM

Hello,

According to Microsoft documentation, error 1603 can occur if, for example, the tool you are trying to install is already present on the system. Therefore, if you are testing your WAPT package and the machine on which you are developing the package is already equipped with it, it may not work.

Have a good day!
User avatar
vcardon
WAPT Expert
Messages: 278
Registration: Oct 06, 2017 - 10:55 p.m.
Location: Nantes, France

July 18, 2022 - 1:55 PM

HugoDams wrote: Jul 18, 2022 - 11:55 waptutils.CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "ATLAS 9.81.2.msi" ' returned non-zero exit status 1603.
Search

Code: Select all

1603
You might find a solution in the forum.
Vincent CARDON
Tranquil IT
HugoDams
Messages: 11
Registration: July 18, 2022 - 11:11
Location: Le Mans

July 18, 2022 - 2:33 PM

alain17 wrote: Jul 18, 2022 - 1:53 PM Error 1603 can be raised if, for example, the tool you are trying to install is already present on the system
Good morning,
No, the test machine is completely clean as of this morning (except for the waptdev package)
HugoDams
Messages: 11
Registration: July 18, 2022 - 11:11
Location: Le Mans

July 18, 2022 - 2:45 PM

Hello Vincent,

The order:

Code: Select all

msiexec /norestart /passive /i "ATLAS 9.81.2.msi"
Run directly from the command prompt, it works correctly (I used /passive instead of /q to see the progress). So I don't think it's an issue with the MSI.

Hugo
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

July 18, 2022 - 6:39 PM

Hello Hugo,

The wapt agent runs in a LOCAL SYSTEM context, which is different from that of the administrator.

Could you test the installation by escalating privileges with psexec (tis-ms-pstools package)?

Code: Select all

psexec -i -s cmd
Then launch the installation via command line as you just did.

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
HugoDams
Messages: 11
Registration: July 18, 2022 - 11:11
Location: Le Mans

July 19, 2022 - 11:37

Hi Denis,

Here's what I've tested:

1: Installed the "ms-pstools" package -> forced the installation on the machine containing the package -> installed the Atlas package -> forced the Atlas installation.
Result: no installation

. 2: Command psexec -i -s cmd in PowerShell as administrator -> attempted to install the MSI in the command prompt opened by the PowerShell command with the quiet option.
Result: successful install/uninstall.

Is there a specific procedure to follow with the "ms-pstools" package to successfully launch the MSI installation?

Edit: To clarify, the test was performed independently on clean clones.

Thanks,

Hugo
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

July 19, 2022 - 12:32

Hi Hugo,

the psexec command is just to test the installation under a LOCAL SYSTEM account. Some installers behave differently under an Admin account and a Local System account, hence the test (but it's just for testing purposes; there's no need to install the package for deployment itself :-) ).

According to your test results, the installation proceeds correctly in a cmd.exe launched with psexec, so there are no issues there.

Do you see anything in the Event Viewer when the installation fails?

Best regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
HugoDams
Messages: 11
Registration: July 18, 2022 - 11:11
Location: Le Mans

July 19, 2022 - 2:11 PM

dcardon wrote: Jul 19, 2022 - 12:32 Do you have anything in the event viewer when the installation crashes?
I get this message when I try to install it in an admin command prompt:

Product: ATLAS -- Error 1606. Could not access network location CustomDisplays.

According to the internet, it could be:
  • Faulty Windows Registry settings (usually a broken key/subkey in the operating database)
    - the install is clean this morning on this test machine
  • Incompatibility of programs with the current operating system
    - no problem there
  • Folder redirection or permission problems
    - the MSI file is on the user's desktop, cmd is in admin mode
  • The presence of malware
    - I don't think so :D
I don't often use the event viewer; I'm in Windows Logs -> Application (I think I'm in the right place)

Hugo
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

July 19, 2022 - 2:16 PM

Does the installer require network resources to complete the installation (such as file sharing on a server)?

Could you please check if the solution offered by Autodesk can resolve your issue?

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked