Uninstall of IBM System I Access For Windows V6R1M0 SI35607 failing
Updated: 18 Sep 2010 | 5 comments
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.
discussion Filed Under:
Comments
Try running msiexec /i and
Try running msiexec /i and then select the uninstall option from the maintenance menu?
Do you see the same error?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks for your
I was able to solve this issue by modifying conditions on custom actions that should not run at uninstall.
That was my first thought...
...but then I decided it was unlikely that a large company like IBM would make such a basic mistake and then miss it in testing. Or was this not a vendor MSI ?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
>I decided
>I decided it was unlikely that a large company like IBM would make such a basic mistake
Best laugh of the day so far. Thanks, Ed.
The original iSeries Access MSI failed to include half the features that IBM's legacy installer installed, not the least of which was the 5250 Emulator.
How about DLLs which contain COM information but no DLLRegisterSever entry-point and which therefore have to be registered individually using an IBM utility? You knew about that one, Atom, yes? It is documented in ApDeploy's 'Package KB' for iSeries Access.
They are beyond dumb...
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Glad to put a smile on your face...
IBM certainly have a knack in producing applications with weird characteristics. Even back in the last century there was a Tivoli management program (IIRC) that would not work until the ownership of the files was changed to "administrator". Go figure.....
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.