Trying to install a MSI that requires ISscript
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
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
Answers (9)
Please log in to answer
Posted by:
jonasm
18 years ago
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
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
Posted by:
MARIN
18 years ago
I tried different version, but no succes yet.
Isn't it possible to strip the ISscript check from the package?
Isn't it possible to strip the ISscript check from the package?
Posted by:
ComfortablySad
18 years ago
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.
^
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.
Posted by:
jonasm
18 years ago
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
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
Posted by:
MARIN
18 years ago
@ComfortablySad
I tried your solution, but the OnCheckSilentInstall custom action does not exist. Can I create it, and what value shout it get?
I tried your solution, but the OnCheckSilentInstall custom action does not exist. Can I create it, and what value shout it get?
Posted by:
Satin
18 years ago
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.
Posted by:
MARIN
18 years ago
The ISscript that is delivered with the installer does not contain a RunasUser property in the property table.
Posted by:
Satin
18 years ago
Opps !! it is the RunAs name key in the registry table that you have to delete
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.