Windows 10 Package Installation 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
Locked
Nicolas Halsberghe
Messages: 5
Registration: February 15, 2019 - 11:41

February 15, 2019 - 11:47

Good morning,

Some of our PCs are starting to upgrade to Windows 10. An error occurred during the installation of a package (see error below). The package installs correctly, but the WAPT console returns this error. Note that the installation on Windows 7 machines does not report any errors.

Is there a modification to be made to the packages intended to be installed on W10?

Code: Select all

'Traceback (most recent call last):\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 4372, in install\n    force=force\n  File "C:\\Program Files (x86)\\wapt\\common.py", 
line 3591, in install_wapt\n    raise e\nCalledProcessErrorOutput: Command \'"Traps_x64_4.1.3.33176.msi" /qn CYVERA_SERVER=traps.institutdegenech.fr USE_SSL_PRIMARY=0 CYVERA_SERVER_PORT=2125 /l*v "
C:\\\\temp\\\\trapsinstall.log"\' returned non-zero exit status 1603.\nOutput:\n']]
High
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :
Contact agauvrit

February 18, 2019 - 09:42

Good morning,

There is no impact between Win7 and Win10, however, it is likely that your software will not behave in the same way.
  • What do you get in the log file C:\temp\trapsinstall.log?
  • What do you get when you throw it by hand?
High
Nicolas Halsberghe
Messages: 5
Registration: February 15, 2019 - 11:41

February 18, 2019 - 5:26 PM

Hello,

I didn't see anything unusual in the Traps log file. And when I install it manually, I don't get any errors. I added `accept_returncodes=[1603]` to setup.py so that the installation would complete without errors.

EDIT:

Here's what I found in the log file. The problem seems to be with Traps. To be continued...

MSI (s) (84:4C) [10:58:37:065]: Windows Installer has reconfigured the product. Product name: Traps 4.1.3.33176. Product version: 4.1.3.33176. Product language: 1033. Manufacturer: Palo Alto Networks, Inc.. Reconfiguration success or error status: 1603.

MSI (s) (84:4C) [10:58:37:065]: Deferring clean up of packages/files, if any exist
MSI (s) (84:4C) [10:58:37:065]: MainEngineThread is returning 1603
MSI (s) (84:20) [10:58:37:081]: RESTART MANAGER: Session closed.
MSI (s) (84:20) [10:58:37:081]: No System Restore sequence number for this installation.
=== Logging stopped: 02/19/2019 10:58:37 ===
MSI (s) (84:20) [10:58:37:081]: User policy value 'DisableRollback' is 0
MSI (s) (84:20) [10:58:37:081]: Machine policy value 'DisableRollback' is 0
MSI (s) (84:20) [10:58:37:081]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (84:20) [10:58:37:081]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (84:20) [10:58:37:081]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (84:20) [10:58:37:081]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (84:20) [10:58:37:081]: Restoring environment variables
MSI (s) (84:20) [10:58:37:081]: Destroying RemoteAPI object.
MSI (s) (84:00) [10:58:37:081]: Custom Action Manager thread ending.
MSI (c) (98:2C) [10:58:37:081]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (98:2C) [10:58:37:081]: MainEngineThread is returning 1603
=== Verbose logging stopped: 02/19/2019 10:58:37 ==
High
skoizer
Messages: 54
Registration: June 19, 2018 - 4:45 PM

February 21, 2019 - 09:02

Isn't this more of a legal issue?
When the installation is done on the Wapt service account, perhaps it needs an increased privilege level?
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT