That is because the msiexec.exe is not in the JVM path. If you want the tuner to use the system path you need to set a tuner property marimba.launch.inheritPath=yes

marimba.launch.inheritPath

specifies whether the system variable PATH (and the directory paths

specified in that variable) is included in the paths that the Java Virtual

Machine (JVM) can see. For example, if you have a custom channel and

you want to use functions in .dll and .class files with directory paths

that are specified in PATH, then set this property to yes.

Valid value: yes or no

Default value: no

Hope this helps

-Greg

Actually NO there will not be any impact it just allowing the tuner to additionally check the System Path Variable for exe'es. You could add the msiexec.exe into the package as a workaround however its going to make the package bigger and also makes it redundant to do something like that because the exe should already be available on the machine you are deploying the package too.

Deploying the property is a the best method for installing packages that use binaries already in the system path.

You can also use below in the .bat file

@echo OFF

cd\

C:

%windir%\system32\MsiExec.exe /X {product code} /qn

yep that would work too.. you are basically hardcoding the path of the exe in the script.