IBM DB2 Connect Personal 9.5 Silent install issue
Hi,
I created a package IBM DB2 Connect Personal 9.5 version for Win 7. I created a silent install with response file as given in the vendor site and wrapped it with wise script. When pushed through SCCM, installation is failing with error code 1602 (Installation cancelled by User). When I manually run the wise script exe getting the same error code 1602 (Installation cancelled by User), but when I run the wise script exe with Run As Admin mode, its installing fine without any errors. Does any one have any idea how to push it through SCCM with out error.
I created a package IBM DB2 Connect Personal 9.5 version for Win 7. I created a silent install with response file as given in the vendor site and wrapped it with wise script. When pushed through SCCM, installation is failing with error code 1602 (Installation cancelled by User). When I manually run the wise script exe getting the same error code 1602 (Installation cancelled by User), but when I run the wise script exe with Run As Admin mode, its installing fine without any errors. Does any one have any idea how to push it through SCCM with out error.
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
naveen.packager
13 years ago
Does the stand alone command line install (without using wise script.exe) installs the app fine? If so check ur wise script if any configuration message is present.
Posted by:
kewl.ravs
13 years ago
Hi Naveen,
I ran the vendor setup.exe with response file i got the same error. When I run it through batch file using Run As Administrator, its working fine. So I dont think its the problem with wise script
I ran the vendor setup.exe with response file i got the same error. When I run it through batch file using Run As Administrator, its working fine. So I dont think its the problem with wise script
Posted by:
naveen.packager
13 years ago
Hmm..yes, its not the problem with wise script. There are several causes found for this when i googled this issue. I can't tell you the exact cause in your case.
Thanks.
Thanks.
Posted by:
kewl.ravs
13 years ago
Its having a vendor msi which is not working fine when i create a transform for it.
Posted by:
anonymous_9363
13 years ago
...so you decided that the best thing to do, rather than find out why the MSI/MST combination wasn't working, would be to create a lash-up which is also not working. When your car makes an unusual noise, is your solution to turn the stereo up so that you can no longer hear any noise whatsoever?
Posted by:
naveen.packager
13 years ago
Its having a vendor msi which is not working fine when i create a transform for it.
Try to trouble shoot the error. If you have any issues guys here will help you.
Posted by:
kardock
13 years ago
ORIGINAL: VBScab
...so you decided that the best thing to do, rather than find out why the MSI/MST combination wasn't working, would be to create a lash-up which is also not working. When your car makes an unusual noise, is your solution to turn the stereo up so that you can no longer hear any noise whatsoever?
VBScab, i love you man!
Posted by:
anonymous_9363
13 years ago
If 'DB2 Connect' is anything like the joke which calls itself 'iSeries Access' you may have fallen victim to IBM's We Know Best attitude, whereby their DLLs contain COM information but which cannot be registered with the standard Windows APIs (which unknowing packagers use when they use RegSvr32 to register DLLs/OCXs). There is a command line utility in 'iSeries Access' which you must use to register such DLLs. I can't recall its name but I'm sure I posted it in a Package KB 'Note' for that application.
And again, if 'DB2 Connect' is like 'iSeries Access', there will be LOTS of files which require registration.
And again, if 'DB2 Connect' is like 'iSeries Access', there will be LOTS of files which require registration.
Posted by:
kewl.ravs
13 years ago
Guys,
I tried to troubleshoot MSI, but not succeeded. But I solved the issue with setup.exe. in the setup.exe properties, compatabilty tab, checked Run this Program as an Administrator. That solved my problem.
I tried to troubleshoot MSI, but not succeeded. But I solved the issue with setup.exe. in the setup.exe properties, compatabilty tab, checked Run this Program as an Administrator. That solved my problem.
Posted by:
naveen.packager
13 years ago
Hmmm...good. Thanks for posting the solution. But in my point of view, if you have a msi which can be transformed, then better way is to transform it than using setup.iss
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.