/build/static/layout/Breadcrumb_cap_w.png

"InstallScript Engine is missing from this machine" Work Around

Hi ITNINJA,

I am working with Oracle Hyperian smartview for Office, Fusion Edition. Extracted the msi and tried instaling silently so got this error "The InstallScript Engine is missing from this machine... " so If I ran the "ISScript10.Msi" first and then my application msi next its installing without any errors. I am okay with this but when I searched online come across with ISSETUPDRIVEN=1 property but when I applied that,it didn't work for me 

Ref:

http://www.itninja.com/question/hyperion-smartview-officeaddin

http://www.itninja.com/question/msi-error-log 

so my question is

a) What is the best practice to handle this type of error (Installthe msi first or use public properties and CA's??)


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Refer below
Posted by: jagadeish 12 years ago
Red Belt
3

Check your main msi has any f1, f2, f3...fn custom actions..

If they are there then you have to install ISScript10.msi as a pre-req.. 

If they are not there then you can break the ISScript10.msi dependency by commenting other ISScript related custom actions (not f1, f2..fn) in main msi..

ISSETUPDRIVEN=1 is to bypass Setup.EXE not to skip ISScript10.msi dependency

Posted by: Arminius 12 years ago
Second Degree Green Belt
0

The best way to handle prerequisites is to install them; it sounds like you are trying to work around a requirement for the MSI.  Doing that will take a lot more effort than ensuring that your environment has what is needed to install the required software.

Posted by: anonymous_9363 12 years ago
Red Belt
0

- Your build should ideally include all the IS runtimes/engines

- ISSETUPDRIVEN is used to force MSIs to run outside the control of the vendor's set-up stub. You will sometimes need to capture activity which a stub undertakes, as many vendors are too stupid to work out how to add that activity into their MSIs.

It's easy enough to test if the stub does anything like that: install the extracted MSI, "hide" the installation data in the registry and then perform a gap-capture using the stub.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ