Page 1 of 1

Error 1603

Published: October 8, 2024 - 10:57 AM
by TITCHI
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.

Re: Error 1603

Published: October 8, 2024 - 10:59 AM
by TITCHI
Here is the package setup:
def install():
# Declaring local variables

# Installing the software
print("Installing: windows-installer-cortex-850624_x64.msi")
install_msi_if_needed('windows-installer-cortex-850624_x64.msi')

Re: Error 1603

Published: October 8, 2024 - 11:03 AM
by sfonteneau
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).

Re: Error 1603

Published: October 8, 2024 - 12:38 PM
by TITCHI
When installing the .msi file on my computer, I get this error:
Screenshot 2024-10-08 122442.png
Screenshot 2024-10-08 122442.png (11.4 KB) Viewed 4222 times
And then, after ignoring the error, I get another error at the end of the installation:
Screenshot 2024-10-08 122442.png
Screenshot 2024-10-08 122442.png (11.4 KB) Viewed 4222 times

Re: Error 1603

Published: October 8, 2024 - 9:24 PM
by sfonteneau
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.

Re: Error 1603

Published: October 9, 2024 - 9:49 AM
by dcardon
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

Re: Error 1603

Published: October 10, 2024 - 09:13
by t.heroult
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.