MSI Uninstall Task without effect

Usage and Config SWD
1

Hi,

To create the MSI Uninstall task I use the following command line => msiexec.exe /x {path} /L*V {path.log} /qn
This doesn’t work at all, instead I’m using the uninstall created with the install task automatically.

Did any of you encountered this problem?

Thanks.

2

After reading through the command, I’d recommend a lowercase v.

msiexec.exe /x {path} /L*v {path.log} /qn
3

I will test this and come back with feedback, positive one :smile:.

4

I would package the BESRemover and use that in silent mode instead. If you just uninstall the msi traditionally, there will be registry keys left behind that could cause problems and even prevent you from re-installing.

Here’s a link for the tool and some commands to use:

http://software.bigfix.com/download/bes/92/util/BESRemove9.2.0.363.exe

besremove.exe [/silent] [/component]

Where component has one of the following values:
· all - remove all IEM components
· client - remove the IEM Client
· relay - remove the IEM Relay

5

I don’t think the question is about uninstalling the BES Client itself, but something else.

6

I would try testing it on the command line to see if that works.

It should be {GUID} not {path} and you need to escape brackets if you are entering them into actionscript. It will work if you are doing relevance substitution that gets the GUID { name of key of (uninstall key) of registry }

Can you share the entire actionscript? ( you can replace any “strings” / etc you don’t want to share )

7

Apologies! At first glance I thought it was a bout uninstalling the IEM client :flushed:

This is a typical format I use for msi uninstalls:

msiexec.exe /x “{123ABCABC-00A0-ABC2-ADB1-ABC00DEF}” /L*V “%windir%\Logs\application.log” /qb

However that would be in a batch file script, and you call the script from your action. For using it directly in an action script, you would need to escape curly brackets as @jgstew mentioned.

8

example of uninstall:
msiexec.exe /x {path} /L*V c:\path\app.log /qn

the difference saw in actionscript is this:
msiexe.exe /x {{path} /L*V c:\path\app.log /qn

9

That actionscript should be correct (although there appears to be a typo), but what I am confused by is {path}, because it should be a GUID, not a path.

Also, I would try putting it in quotes, so it would be:

waithidden msiexec /x “{{GUID}” /L*V c:\path\app.log /qn

1 Like
10

@jgstew sorry, by path I meant to say GUID. thanks. will edit on monday the actionscript.

1 Like
11

I found the problem, it was the automatic relevance generated by the msi package. It had a NOT … deleted and everything’s running as it should. thanks everybody for your help!

1 Like
12

And another problem seemed to be a { at the begining of the GUID as jfstew stated.
msiexec.exe /x {{GUID} /L*V C\path\app.log

Thanks for your help.

1 Like
13

The “{” character is used to surround relevance substitution in actionscript. If you need to actually use the character normally, then you must escape it by using it twice: “{{GUID}”

3 Likes