Installation error following package transfer to a group

[JeromeD.]

Good morning,

In the interest of optimization, we have integrated the office suite into a group of common applications.
This update had no impact on the entire fleet, except for one Windows 10 PC on which the office suite uninstalled itself upon rebooting the machine and can no longer be reinstalled.
Since this manipulation, I have a package error line and then a second line (+) which indicates a new installation.

Is it possible to manually delete the entire package installation history to start with a clean installation? Any other solutions?

Here is the error message displayed on the console:

Code: Select all

installing Office 2019
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4082, in install_wapt
    exitstatus = setup.install()
  File "C:\WINDOWS\TEMP\waptxvvldmt5\setup.py", line 26, in install
  File "C:\Program Files (x86)\wapt\common.py", line 3859, in run
    return ensure_unicode(run(*arg, pidlist=self.pidlist,**args))
  File "C:\Program Files (x86)\wapt\waptutils.py", line 2118, in run
    raise CalledProcessErrorOutput(proc.returncode, cmd, ''.join(output))
waptutils.CalledProcessErrorOutput: Command '"setup.exe" /configure "Configuration.xml"' returned non-zero exit status 1603.
Output:

CalledProcessErrorOutput: Command '"setup.exe" /configure "Configuration.xml"' returned non-zero exit status 1603.
Output:

WAPT version: 2.4.0.14080
OS Server: Ubuntu 22.04lts
Operating system of the administration machine: Windows 10

Thank you in advance for your reply.

[dcardon]

Hello Jérôme,

since the package is dependent on the package group, the machine will try to install it until the installation is successful. However, the problem isn't so much the group dependency, but rather that the Office 2019 installation is failing on the machine in question.

The error code 1603 is quite generic. We would need to see what the exact problem is on the machine by running the installation manually and see if the issue can be resolved.

If the problem doesn't occur when performing the installation manually as a local administrator, then we should test it as a local system user by connecting with `psexec -i -s cmd.exe`. The WAPT agent runs under a local system account.

Regards,

Denis

[t.heroult]

Hello,

One possible solution: Look in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products.
Search for a key corresponding to the software and, if so, delete it (after exporting it as a backup).
This has often resolved this type of issue for me.

Regards,
Tom