Best Answer Stefan Krueger , 04 December 2014 - 12:42
You're already ignoring the exit code, so this is a bit strange. What's in the log in case of failure?
Go to the full postBest Answer Stefan Krueger , 04 December 2014 - 12:42
You're already ignoring the exit code, so this is a bit strange. What's in the log in case of failure?
Go to the full postPosted 04 December 2014 - 12:34
We're running a custom action on uninstall with the following parameters:
Executable Filekey - Name of exefile to be run, it's installed during installation
Return Processing - Synchronus (Ignores exit code)
In-Script Execution - Immediate Execution
Execution Scheduling - Always execute
Run During Patch Uninstall - No
Sequence, Install Exec Condition - REMOVE="ALL"
This works for most of our customers, but for unknown reasons, the CA fails for some customers. This stops the uninstallation and completely prevents uninstallation. It's not critical that the CA succeeds and we would rather have the uninstallation to continue rather than stop on this error.
In what way can we accomplish this?
Any help is greatly appreciated!
Posted 04 December 2014 - 12:42 Best Answer
You're already ignoring the exit code, so this is a bit strange. What's in the log in case of failure?
Stefan Krüger
InstallSite.org twitter facebook
Posted 04 December 2014 - 13:34
Thanks for confirming that Return Processing - Synchronus (Ignores exit code) is the correct way of handling it! I just noticed that the installation previous to our current does not ignore the exit code. So that explains why some customers have this problem. But for the future things should be working well.