Hello,
We are trying to create the ZimbraConnectorOLK_8.8.9.1775_x64.msi package with WAPT 2.1 on a Windows 10 machine.
When we launch the package creation wizard with the MSI file, the "Silent options" and "Uninstall key" checkboxes are grayed out!
When we run the installation in PyScripter, it stops and fails with the error
"Waiting for key {2922BA16-159F-4B0C-92C2-A0DBBAB56D51} to appear in the Windows registry."
The installation itself completes successfully, and the application runs, but it displays an error on the machine. Furthermore, after installation, we don't have this key in
the Windows registry.
Thank you for your help.
[SOLVED] Creating the Zimbra connector package
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Moloc,
There are standard flags for installing MSI packages, which is why the wizard doesn't offer them for MSIs.
The problem with your MSI is that the uninstallation key defined in the MSI metadata is not the same as the one written at the end of the installation (it's really not clean, but oh well, it happens). You therefore need to override the uninstallation key for the `install_msi_if_needed` function to work. Otherwise, this function won't find the uninstallation key after the MSI installation (because it's not the correct one in the metadata), and will therefore conclude that the installation failed.
Using `run()` allows you to bypass the automatic check of the uninstallation key. However, to have a clean package, it's recommended to include it to allow for uninstallation if possible.
I'm marking the topic as resolved.
Best regards,
Denis
There are standard flags for installing MSI packages, which is why the wizard doesn't offer them for MSIs.
The problem with your MSI is that the uninstallation key defined in the MSI metadata is not the same as the one written at the end of the installation (it's really not clean, but oh well, it happens). You therefore need to override the uninstallation key for the `install_msi_if_needed` function to work. Otherwise, this function won't find the uninstallation key after the MSI installation (because it's not the correct one in the metadata), and will therefore conclude that the installation failed.
Using `run()` allows you to bypass the automatic check of the uninstallation key. However, to have a clean package, it's recommended to include it to allow for uninstallation if possible.
I'm marking the topic as resolved.
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
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
