Equisys technical notes

Technical guidance, explanations and fixes for our products

PRB: Unable to complete the Zetalink install



ID: ZTN2002

This Zetalink technical note applies to:

  • Zetalink 1.0


  1. Install freezes during install and progress bar stops.
  2. Install terminates prematurely. If SETUP.EXE was run (not ZETALINK.MSI directly) then ZETALINKINSTALL.LOG (found in temp directory) will include the following text:

1: Starting script engine COM server...

1: Opening script file...

1: Starting Kernel wrapper...

1: Failed to create script engine...

1: Script Handler initialization failed, error = 0x0


  1. Windows installer engine failed to initialise correctly.
  2. InstallShield script engine failed to initialise correctly.


  1. Stop and restart the Windows installer service before running SETUP.EXE. If this happens again, restart the Windows Installer service and run the ZETALINK.MSI file directly.
  2. Follow the instructions in InstallShield article Q105408 - Setup initialisation errors can be caused by a number of factors. This is a non-exhaustive list of possible resolutions:
    1. Insufficient permissions on the machine. If you are using a Windows NT or a Windows 2000 machine, you need to have administrative permissions to run an InstallShield setup. Make sure you have the correct permissions.
    2. 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 or KNLWRAP.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.
    3. Check and make sure IKERNEL.EXE or KNLWRAP.EXE is not in memory. If it is, and no setup is running at the time, end that task and restart the system.
    4. Clear out the Temp directory.
    5. Delete the Program Files\Common Files\InstallShield folder and then rerun the setup.
    6. 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.
    7. Another possibility is that you do not have sufficient COM permissions. (Q104986) To give yourself the necessary permissions you need to do the following:
      1. Go to a command prompt and type DCOMCNFG.EXE. This launches the Distributed COM Configuration Properties dialog box.
      2. Click the Default Security tab.
      3. Click the Edit Default button in the Default Access Permissions section.
      4. Make sure that "Interactive" and "System" are listed in "Default Access" permission list.
      5. Apply all the changes and try to run your setup. Make sure that IKERNEL.EXE or KNLWRAP.EXE are not still running from a previous install.
    8. The other potential cause is a missing STDOLE.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 operation system as the machine you are trying to run the setup on.


This has been identified by InstallShield as a problem with the software versions given above (see Article ID:   Q105408 on http://support.installshield.com/kb/default.asp

Last updated: 15 November 2001 (AVS/DH)

Equisys Logo, Document Management and Expense Management for Business Central

Replaced by script