Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

ISScript error

2 replies to this topic


  • Members
  • 1 posts

Posted 14 June 2002 - 01:00

The installer gets instmsia.exe and installs, however i receive an error that isscript does not excisst and that the isscript.msi should be run manually. How do I include this in the pftw or in the project so it installs (if needed) ???


  • Members
  • 11 posts

Posted 14 June 2004 - 10:12

how do u run your instmsia.exe ??? did you make sure that you have msi.dll in your system folder... if you have.. did you launch it using the launch app and wait???


  • Moderators
  • 1,447 posts

Posted 14 June 2004 - 11:23

Some background: instmsia.exe is the Windows Installer engine. ISScript is the runtime engine for Installshield's own scripting language (Installscript). This engine is only needed if you install an Installscript based MSI setup OR use Installscript custom actions in your setup. You must be doing one or the other.

The error shows up because you are not including the ISScript engine in your setup, and the setup is not able to download the engine from the Internet. You cam use the release wizard to specify to include the engine in the SETUP.EXE, to include it as a merge module, to download it from the internet, or do none of the above. You must have specified to not include the engine in the setup and to not download it from the internet. In this case the setup will fail on all systems where the engine is not already installed (with the right version).

This error may also occur if you are trying to run an MSI file directly without launching it through a setup.exe bootstrapper. If the ISScript engine is not included as a merge module the ISScript engine must be installed prior to launching an MSI file that requires Installscript directly.

That might be a lot more info than you needed. How to solve: include the engine with the setup.exe. This is the most reliable and simple solution. Sometimes the engine downloaded from the Installshield site is out of date and then your setup will still fail.
-Stein Åsmul