[RESOLVED] Mattermost-Desktop package issue

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
Yannick
Messages: 4
Registration: Sep 17, 2024 - 3:16 p.m.

September 17, 2024 - 3:30 PM

Hello,

Since the last update of the Mattermost-desktop package (version 5.9.0), installations are no longer working.
Worse, the WAPT Console indicates that the packages are installed and up to date.

As a result, the existing machines remain on version 5.8, and new workstations do not have the program.
Attached is a screenshot of the installation on a new PC.

Server version: 2.5.5
OS: Debian 10.13
Admin machine: Windows 10 Pro.

After investigation, it seems that the installer cannot find MSIEXEC on the client machine, while other packages requiring MSIEXEC install correctly.

Can you help me resolve this issue?

Sincerely,
Yannick
Attachments
wapt-matter-1.png
wapt-matter-1.png (2.41 KB) Viewed 3004 times
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 17, 2024 - 10:57 PM

Hi Yannick

, thanks for reporting the error.

Actually, I checked the history, and Mattermost has switched its installer to "Non- Allusers" by default.

I've just fixed the package. It will uninstall the old Mattermost if it's present in AppData, then reinstall it in Program Files.

Thanks for the report.
Yannick
Messages: 4
Registration: Sep 17, 2024 - 3:16 p.m.

September 18, 2024 - 08:24

Good morning,

Thank you for your response.
The new package has been successfully downloaded from the repository.

Unfortunately, I'm getting an error on the PC.

Code: Select all

Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4235, in install_wapt
    exitstatus = setup.install()
  File "C:\Windows\TEMP\wapte7rizsbz\setup.py", line 17, in install
  File "C:\Program Files (x86)\wapt\common.py", line 3991, in run
    return ensure_unicode(run(*arg, pidlist=self.pidlist,**args))
  File "C:\Program Files (x86)\wapt\waptutils.py", line 2177, in run
    raise CalledProcessErrorOutput(proc.returncode, cmd, ''.join(output))
waptutils.CalledProcessErrorOutput: Command ['MsiExec.exe', '/X{95C1D261-22CB-4CD2-A091-892601E8B17E}', '/q', '/norestart'] returned non-zero exit status 1605.
Output:C e t t e   a c t i o n   e s t   v a l i d e   u n i q u e m e n t   p o u r   l e s   p r o d u i t s   d Ú j Ó   i n s t a l l Ú s . 
 

Code: Select all

CalledProcessErrorOutput: Command ['MsiExec.exe', '/X{95C1D261-22CB-4CD2-A091-892601E8B17E}', '/q', '/norestart'] returned non-zero exit status 1605.
Output:C e t t e   a c t i o n   e s t   v a l i d e   u n i q u e m e n t   p o u r   l e s   p r o d u i t s   d Ú j Ó   i n s t a l l Ú s . 
 

The Mattermost-desktop 5.8 package was indeed on the PC before the update.
But since the new package uninstalls the old version, it is impossible to perform a new installation.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 18, 2024 - 09:56

I've just fixed a potential problem (which I can't reproduce here)

I had created a loop: "For all software that is associated with and has the name 'mattermost', uninstall it." But if several programs had the name "mattermost," then we could try uninstalling a program that no longer existed because we had just uninstalled it. I'm not sure if that's the case where you are.

In your case:

We are trying to uninstall Mattermost using the command:

Code: Select all

MsiExec.exe /X{95C1D261-22CB-4CD2-A091-892601E8B17E} /q /norestart
But Windows says that my product is not installed (yet the key {95C1D261-22CB-4CD2-A091-892601E8B17E} is indeed present on the machine... otherwise we wouldn't be going through the loop)
Yannick
Messages: 4
Registration: Sep 17, 2024 - 3:16 p.m.

September 18, 2024 - 10:36

I ran some tests on my computer.
If we let WAPT do its thing, we always get the same error.

However, if I uninstall from Windows and then reinstall from WAPT, everything works fine

I just pushed the new package to a user machine that no longer has Mattermost since the package was pushed last night => Failure with the error:

Code: Select all

CalledProcessErrorOutput: Command ['MsiExec.exe', '/X{95C1D261-22CB-4CD2-A091-892601E8B17E}', '/q', '/norestart'] returned non-zero exit status 1605.
Output:C e t t e   a c t i o n   e s t   v a l i d e   u n i q u e m e n t   p o u r   l e s   p r o d u i t s   d Ú j Ó   i n s t a l l Ú s . 
Same error when doing a forced installation.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 18, 2024 - 11:21

Yannick wrote: Sep 18, 2024 - 10:36 AM I ran some tests on my machine.
If we let WAPT run, we always get the same error.

However, if we uninstall from Windows and then launch the installation from WAPT, everything goes smoothly.

I just pushed the new package to a user's machine that no longer has Mattermost since the package was pushed last night. => Failure with the error:
CalledProcessErrorOutput: Command ['MsiExec.exe', '/X{95C1D261-22CB-4CD2-A091-892601E8B17E}', '/q', '/norestart'] returned non-zero exit status 1605.
Output: This action is valid only for the products.

Same error occurs when doing a forced installation.

However, if he comes across this message, it means that the key {95C1D261-22CB-4CD2-A091-892601E8B17E} does indeed exist on the computer.
Yannick
Messages: 4
Registration: Sep 17, 2024 - 3:16 p.m.

October 9, 2024 - 12:06

Hello,

Following a cleaning of the machines, the problem is resolved.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

October 11, 2024 - 09:04

Hi Yannick,
thanks for the feedback. :-)
I'm marking the topic as resolved.
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
Locked