Hi there,

I am trying to install: Microsoft VSNet integrations for C++ and Fortran
This integrates the Intel Fortran Compiler into Visual Studio .NET.

When I run the MSI which should integrate the program, but in stead, I get this error message:

The InstallScript engine is missing from this machine. If available, please run ISScript.msi, or contact your support personnel for further assistance.

I installed the ISscript 8 msi delivered with the installation package, but no luck yet.

Anyone some advice?

Kind regards,
Dennis
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Dennis!

The different ISScript Engines is, for some reason not backward-compatible, so if you need ISScript 9, you have to install ISScript 9...

But if you took it from the installation, it's supposed to work...

Maybe you can try download the other ISScripts versions and see if any of those works.

/Jonas
Answered 03/17/2006 by: jonasm
Blue Belt

Please log in to comment
0
I tried different version, but no succes yet.

Isn't it possible to strip the ISscript check from the package?
Answered 03/17/2006 by: MARIN
Orange Senior Belt

Please log in to comment
0
http://itninja.com/blog/view/7.8-gigabyte-size-limit-in-nt''s-ntfs4
^
Follow those instructions and it should work as long as the correct version of ISSCRIPT is already installed on the workstations or gets installed before the package.
Answered 03/17/2006 by: ComfortablySad
Yellow Belt

Please log in to comment
0
Hi again!

You can usually remove the ISScript check, but I would not recommend you to do it.
If your install can't find the ISScript Engine, your installation might fail because it probably needs the ISScript file thats missing.

/Jonas
Answered 03/17/2006 by: jonasm
Blue Belt

Please log in to comment
0
@ComfortablySad

I tried your solution, but the OnCheckSilentInstall custom action does not exist. Can I create it, and what value shout it get?
Answered 03/20/2006 by: MARIN
Orange Senior Belt

Please log in to comment
0
Guys the original versions of ISScript.msi cannot be installed in local system account(thru tools like landdesk or scheduling thru 'at' command) . Make sure that you remove the property RunasUser thru ORCA in the Isscript.msi to enable its installation in LSA account.
Answered 03/20/2006 by: Satin
Senior Yellow Belt

Please log in to comment
0
The ISscript that is delivered with the installer does not contain a RunasUser property in the property table.
Answered 03/20/2006 by: MARIN
Orange Senior Belt

Please log in to comment
0
InstallShield Tech Article here
Answered 03/20/2006 by: abritton
Senior Yellow Belt

Please log in to comment
0
Opps !! it is the RunAs name key in the registry table that you have to delete
Answered 03/20/2006 by: Satin
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity