Hello,
when I run the following package, I get the following error:
CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "windows-installer-cortex-850624_x64.msi" ' returned non-zero exit status 1603.
Thank you for your help.
Error 1603
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
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
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello, error
1603 is a classic Microsoft error:
https://learn.microsoft.com/en-us/troub ... error-1603
You would need to manually run the MSI on the machine to understand what's wrong (missing dependency or something else).
1603 is a classic Microsoft error:
https://learn.microsoft.com/en-us/troub ... error-1603
You would need to manually run the MSI on the machine to understand what's wrong (missing dependency or something else).
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The "File in use" message indicates that files are locked. Is another Palo Alto program already installed? Is this an update? If so, you might want to try stopping the existing process that's locking the files and stop it beforehand.
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Thierry,
I imagine the problem is related to an update? Normally, the installation MSI/EXE file is responsible for closing running processes. You should check if there are any flags to add or processes to stop before the update.
Regards,
Denis
I imagine the problem is related to an update? Normally, the installation MSI/EXE file is responsible for closing running processes. You should check if there are any flags to add or processes to stop before the update.
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
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
Hello,
here's another suggestion:
I sometimes encounter this problem with software updates on one or two machines, while all the others install correctly.
I've noticed that very often, simply deleting a registry key is enough:
In the "HKLM\SOFTWARE\Classes\Installer\Products" registry hive, you need to find the key that corresponds to the software and delete it.
The update then installs without any problems.
here's another suggestion:
I sometimes encounter this problem with software updates on one or two machines, while all the others install correctly.
I've noticed that very often, simply deleting a registry key is enough:
In the "HKLM\SOFTWARE\Classes\Installer\Products" registry hive, you need to find the key that corresponds to the software and delete it.
The update then installs without any problems.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
