Setup.exe (ikernel.exe) is not copied/extracted to Program Files (x86)\Common Files\InstallShield\Engine\6\Intel 32
Hi, we are using IS for the last 3+ decades. We converted our setups originally made in IS 6.0 Professional to IS 2010 and IS 2015.
Setups work fine both in silent and UI modes. One of our customers wants to install our applications through SCCM and PSExec usig .iss files.
In Customer's environment they use system context and use PSExec to call Setup.exe in silent mode. Setup.exe's loads in memory we see the IS launcher setup in
Task Manager but after several minutes after time out the setup.exe unloads itself from memory and no real installation occurs on the target machine.
Our finding is:
The InstallShield engine (iKernel.exe) could not be installed IKernel.exe could not be copied to "C:\Program Files (x86)\Common Files\InstallShield\Engine\6\Intel 32"
Can anyone help us figuring out what really happens behind the scene on the launch of setup.exe( or more specifically ikernel.exe) and the engine unable to copy itself
on target machine's said location given above. Its amazing in our own environment setups work fine in both user and system context.
One doubt is as our setups are converted setups from IS 6.0 to IS 2015 there might be any security check in customer's environment that ikernal.exe is uanble to be
copied on the target machine.
Similarly one more question is when we convert to upper versions of IS what is then the version of iKernel.exe, is that also converts to IS 2010/2015 or this ikernel.exe
remains the same in its original version in which setup was created first time.
If after conversion to higher versions of IS ikernel remains the same in lower version, is there any possibiliy or option to convert it too to higher version in order to
avoid any confusion.
An urgent help/resolution is highly appreciated. In last will it affect if we convert even setups in IS 2015 into IS 2018.
ikernel.exe is not required If you are using InstallShield 2015 or later.
Looks like some dependent files are missing on the remote system where the setup.exe is getting executed.
My suggestion would be:
1- to upgrade the installer to IS 2018 or later.
2- While executing the setup, generate the logfile to find the root cause of the issue.