Distribution of IBM I Access for Windows 7.1
Hello- this is my 1st Managed Installation. I am installing IBM I Access for Windows 7.1. The target computers have version IBM ISeries Access for Windows 5.8 on them now. I have a directory with a single sub-directory, and when I manually run this, it completes perfectly, no interaction required -
setup /S /v/qn
So I zipped the folder & the subfolder under it, and it is on the KBox now. When I launch the Managed Software Installation, it is getting tripped up as follows -
The primary language version Mri2924 that is currently installed does not match any available language versions. The upgrade cannot continue. Something changes when I am deploying via the KBox compared to a manual install, & having problems with is - any help is appreciated.
setup /S /v/qn
So I zipped the folder & the subfolder under it, and it is on the KBox now. When I launch the Managed Software Installation, it is getting tripped up as follows -
The primary language version Mri2924 that is currently installed does not match any available language versions. The upgrade cannot continue. Something changes when I am deploying via the KBox compared to a manual install, & having problems with is - any help is appreciated.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
Allblack
8 years ago
It is easier to just uninstall the old version and do a fresh install: IBM Access Ver 7.1 64bit version only has the American option English language file.
Posted by:
Estherqiqi
12 years ago
Hi TomLCT,
Mind to share how you configure the silent upgrade to v7.1 using KBOX?
Posted by:
anonymous_9363
13 years ago
My suspicion would be that it's trying to find the installed language(s) but, because the KBox uses the local System account, there won't be any.
Does the EXE extract and execute an MSI?
Does the EXE extract and execute an MSI?
Posted by:
tomlct
13 years ago
Thank you for the reply. I am not sure, & I will try to find out & re-post.
Posted by:
tomlct
13 years ago
I believe it uses "cwbinstall.msi", because when I went to the target, and to the Kace folder with the installation, I issued "cwbinstall.msi" and had the same message.
Posted by:
tomlct
13 years ago
Hello - it is working now, thanks to the assistance I received from Kace support (Mark Gonzales). The folder structure I was using for my manual install had a folder "MRI2924" at the same level as the folder with all the install files, NOT under it. My manual install must have seen it. I did quick experiment - on the target that was not working, I stuck a copy of that folder where KACE had placed the package, in the same folder, and a manual install on that target worked, so on my source, I just put a copy of this folder UNDER my root level install folder, and repackaged it, and reloaded to the KBox, and OK now.
Comments:
-
Hi TomLCt, mind to share how you actually upgrade the version through KBOX? - Estherqiqi 12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.