I'm trying to upgrade IBM iSeries Access using an OS Deployment Provisioning Template to ensure that a series of tasks are comlpeted in a set order
1 Remove the existing version of iSeries Access - Completes
2.Restart the PC to comlete the uninstallation process - Completes
3.Unpack the installation files to a temporary folder from a previously downloaded archive. - Completes
4.Run the iSeries Access installer setup.exe (Installshield) - fails, the installer exits immediately.
However if I then connect to the PC and run the installer it works. The PC OS is XP SP3 and I'm using Landesk 8.8 SP4 any ideas?
Is there a reason why the installer is exiting immediatley in the event viewer?
To do a true test, you need to open up the local system command prompt when you connect to the pc and launch the installer, because provisioning runs all its jobs as Local System.
Do do that in XP, connect to the machine and open up command prompt and type this:
at xx:xx /interactive cmd.exe (where xx:xx is the time + a minute)
at 14:45 /interactive cmd.exe
wait the minute and a local system command prompt will launch,
Then try launching the executable and see if you are getting the same results.
Does it always fail, or sometimes fail ? I am seeing SWD fail intermittently during provisioning - but if it is always failing its a different problem.
The installer exits with the return code -2147483646.
If I create a second deployment template which only unpacks the instalation files and then runs the installer (i.e a copy of failing deployment minus the uninstall) this works
This always works in test on the LAN, but then fails during more extensive testing over the WAN
Is your delivery method for the provisioning task a run or download from source delivery method?
Can the machines on the WAN access the software share sufficiently?
If using a download from source delivery method, do all the additional files exist in the package?
Does the deliverymethod have any "require non-ras" connection settings enabled?
Hopefully will give you a few things to look at on this one