IKERNEL.EXE Failed to Launch
Setup initialization errors can be caused by a number of factors. This is a non-exhaustive list of possible resolutions: Insufficient permissions on the machine. If you are using a Windows NT or a Windows 2000 machine, you need to have administrative permission to run a n InstallShield Professional 6.x setup. Make sure you have the correct permissions.If you just ran an InstallShield setup, the engine takes a few seconds at the end of the installation to clean up. During this time Ikernel.exe (the engine file) is running in memory from a previous process; that is why you are not allowed to launch another setup. Waiting a few seconds and running the setup again should resolve this.Check and make sure Ikernel.exe is not in memory. If it is, and not setup is running at the time, end that task.Clean out the Temp directory.Delete the Program Files\Common Files\InstallShield\Engine folder and then rerun the setup.Reinstalling Internet Explorer (IE) 5.x can also repair a number of corrupted/missing core Windows files from your machine, so reinstalling IE 5.x and the NT service pack is also suggested.You may not have sufficient COM permissions. For information on how to troubleshoot this, see Knowledge Base article Q104986, INFO: Initialization Error Troubleshooting.A potential cause is a messing Stdole32.tlb file. This is a core Windows file and should exist on your machine. Make sure that if you get this file from another machine, the machine is running the same operating system as the target machine.If you are trying to install to a Windows 98 machine, download and run DCom98.exe from the following site: http://www.microsoft.com/com/dcom/dcom98/download.asp.Make sure that you are using the latest version of the InstallShield engine. To install the latest engine, see Knowledge Base article Q105097, INFO: Install the Latest Version of Ikernel.exe.