Tranquil IT Forum

Okay, I have a theory about the problem:

Previous versions of the client were installed at the user profile level (which caused problems for wapt deployment in a system account).
Since version 3.0.0 or 3.1.0, deployment to a system account has been working. I suspect the problem you're experiencing is related to a previous version installed under a user account. And indeed, I had forgotten that the software doesn't appear in appwiz.cpl (this could be fixed using wapt, but the client can only be uninstalled by the account that installed it, which is the system account in the case of wapt).
Before going any further, could someone experiencing this problem uninstall the client using the following command from the user account that installed it:

MsiExec.exe /X{A74BDC23-D51E-4EB2-9175-F1EC67EC37F0} /q

and reinstall it via Wapt using the system account, then test its functionality

The software is temperamental... if I understand your problem correctly, you need to start with a fresh install of the client!

Sorry, I just got back from vacation.


So, Stormshield doesn't appear in the appwiz, and as a result, running MsiExec.exe /X{A74BDC23-D51E-4EB2-9175-F1EC67EC37F0} /q gives the response: "This action is only valid for products already installed..."
It's listed in the WAPT software inventory, but it refuses to install it over the top. I even tried setting `remove_old_version = True` in the package, but that didn't do anything either.

I'm wondering if the problem might also be related to the TAP card that's created...

Also, version 3.2.0 was removed from download due to an unmentioned malfunction, and 3.2.1 hasn't been available for several days...

@olaplance, perhaps to reproduce the "bug," try installing version 2.8.0 first?


Anyway, I'll keep looking.

client updated to version 3.2.1 (FYI)

realynot wrote: ↑Feb 27, 2023 - 2:05 PM Client updated to 3.2.1 FYI

It seems to be the same problem again.
But I only tested it on a machine that already had a problem with the local service connection error

Hello,

everything went smoothly with the 3.2.1 update on my end.

For me, all your tests only confirm my theory.

My package only works with a fresh installation on a machine, but not if the client has already been installed by a method other than the wapt package (system account!).

If the message "This action is only valid for products already installed..." appears when trying to uninstall the client, it's because the uninstallation is being initiated with a different account than the one with which it was installed.

https://learn.microsoft.com/en-us/windo ... le-patches