I have 2 applications (CorelDraw Suite 11 and Reflex Magnetics Disknet) which require ISScript.msi to be installed first. They both require a different version of ISScript. I have managed to deploy them by installing one package at one OU in AD and the other at a child OU. This has worked OK but is not ideal.

I have now come to install another application (Virtual PC) on my PC only which has it's own msi and also requires ISScript.

I am trying to install this manually using the included setup.exe and recieve the following error:

"The InstalScript engine on this machine is older than the version required to run this setup. If available please install the latest version of ISScript.msi."

I have tried installing each of the versions of this I have found, right up to version 10, and re-run the setup and still get the same error.

I have read on some posts there is a way of removing the need for ISScript from an application but cannot find any posts explaining how to do this. I am assuming I will run into further problems if I need to install a new peice of software over the network which requires ISScript.

Any help very much appreciated.

Thanks,
Mark

Just to add I am using Wise Package Studio Pro
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
installshield right [:)].. well try launching the msi's intead of using its setup.exe using a command line and see if you get the same result on the installation.. the msi's should be in the same folder as the setup exe's else you need to extract them
Answered 07/08/2005 by: rikx2
Purple Belt

Please log in to comment
0
The first 2 applications are installed using their msi using a GPO. Virtual PC does have an msi which, when run gives the same error message.
Answered 07/08/2005 by: markberry
Senior Yellow Belt

Please log in to comment
0
ISScript.msi *should* be backwards compatible. Look through InstallShield.com (or your software library) for the latest ISScript.msi that you can find, and see if that works. I hope it does, because if not you're going to get into a wacky situation of upgrading & downgrading ISScript to make your MSI's work. That would suck.
Answered 07/08/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
My best suggestion is if you have a Vendor supplied MSI, create a MST and customize it instead of using manual run or snapshot or virtual OS. I had a bad experience on creating msi for a MSI...
Answered 07/08/2005 by: Sathia
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: VikingLoki

ISScript.msi *should* be backwards compatible. Look through InstallShield.com (or your software library) for the latest ISScript.msi that you can find, and see if that works. I hope it does, because if not you're going to get into a wacky situation of upgrading & downgrading ISScript to make your MSI's work. That would suck.




So if I install ISScript 10 by msi before any other applications they should, in theory, all install.

Will give it ago. Thanks,

Mark
Answered 07/08/2005 by: markberry
Senior Yellow Belt

Please log in to comment
0
Hi

May i know what is your deployment mode? tool? in some of the installers, u can call a new application's msi as a dependency...
Answered 07/09/2005 by: Sathia
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: Sathia

Hi

May i know what is your deployment mode? tool? in some of the installers, u can call a new application's msi as a dependency...


Using AD to deploy on a per-pc basis. Generally using Wise Package Studio to package applications, although the 2 apps mentioned above come with their own msi.
Answered 07/11/2005 by: markberry
Senior Yellow Belt

Please log in to comment
0
Hi,

delete c:\program files\common files\InstallShield and all registry entries for isscript (delete whole hives, not only keys and don't forget to backup them before deleting :-)) ), than try to run setup.exe (it has its own isscript.msi of correct version).

The problem is that you are deploying isscript through AD, i got the same problem .... :-((


Norika
Answered 07/12/2005 by: norika
Yellow Belt

Please log in to comment
2
Maybe I should clarify. The Setup.exe essentially launches two MSIs, ISScript.msi & [the app].msi. ISScript.msi is your typical MSI. [the app].msi is not a complete MSI, it resides on information being passed to it by Setup.exe. This is what mucks up AD deployments. It's expecting a legacy setup.exe install, or a command, but instead it gets two Windows Installer actions.

The BEST solution is to convert the Setup.exe/MSI into a standard MSI, but this requires the expensive InstallShield Admin Studio 6. Description is available HERE.

If you don't have Admin Studio 6, what you want to do is remove the Setup.exe and have two MSI installs, with ISScript as the prerequisite. ISScript is easily broken out, by copying & deploying ISScript.msi. The other MSI is a bit trickier. Follow the instructions HERE. Remember, ISScript must be installed on the machine, at equal or higher version level than what was supplied with the install, before the modified MSI will work.

Yes, you can get away with keeping the setup.exe and using it for deployment. But IMO, it ends up being more trouble in the long run. Straight MSIs are much easier to live with.
Answered 07/12/2005 by: VikingLoki
Second Degree Brown Belt

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