Uninstall of IBM System I Access For Windows V6R1M0 SI35607 failing
Installing this software via msi is no problem but when I execute the msiexec /x command to trigger an uninstall, I get the followin error:
Error 1713 IBM system i access for Windows V6R1M0 cannot install one of its required products.
Contact your technical support group.
Has anyone else encountered this error before.
Do you have better experiences using the setup.exe that is provided as well by the vendor.
Error 1713 IBM system i access for Windows V6R1M0 cannot install one of its required products.
Contact your technical support group.
Has anyone else encountered this error before.
Do you have better experiences using the setup.exe that is provided as well by the vendor.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
IBM's MSIs have always been entertaining. I'll wager this one has a Custom Action which isn't conditioned to only run on installation. A verbose log will show which CA is failing.
Posted by:
ikke
14 years ago
I was able to solve this issue by modifying conditions on custom actions that should not run at uninstall, thanks a lot !.
Posted by:
anonymous_9363
14 years ago
Why not help someone else who may have the same problem at some future time by posting the exact details (i.e. principally the CA name) in the 'Package KB' for IBM iSeries Access?
Posted by:
ikke
14 years ago
I have posted this in the 'Package KB' and my entry will have to be approved still.
Posted by:
kingskawn
13 years ago
Hi Ikke, I looked over packageID but didn't find your document.
Can you please tell me how you installed V6R1 silently?
Can you please tell me how you installed V6R1 silently?
Posted by:
anonymous_9363
13 years ago
The thread is actually about silent uninstall.
Anyway, as I mention, IBM's MSIs are always good for a giggle. For example, a CA in the DB2 Client MSI insists that a response file (normally used by the set-up stub) is present or it fails. You'll need to go through those CAs and either kludge a work-around or condition-out the CA. Alternatively, you could use the set-up stub with a response file. The IBMweb site has details of how to create and use such a file for deployments.
Anyway, as I mention, IBM's MSIs are always good for a giggle. For example, a CA in the DB2 Client MSI insists that a response file (normally used by the set-up stub) is present or it fails. You'll need to go through those CAs and either kludge a work-around or condition-out the CA. Alternatively, you could use the set-up stub with a response file. The IBMweb site has details of how to create and use such a file for deployments.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.