/build/static/layout/Breadcrumb_cap_w.png

issue with installshield msi on wmware machine

When I run an installshield msi on a vmware machine. the installation stops and I see the following in the log file.
1: Failed to extract _IsUser.dll, Ignore it.
1: Failed to extract IGdi.dll, Ignore it.
When I run the msi on a physical machine, I dont't have any problems ?

What can be causing this issue ?

0 Comments   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 15 years ago
Red Belt
0
ProcMon, ProcMon, ProcMon, ProcMon, ProcMon, ProcMon....
Posted by: mekaywe 15 years ago
Brown Belt
0
The VMWare build requires ISSCRIPTENGINE to install InstallShield MSIs.

Install ISSCRIPTENGINE before u install ur application
Posted by: kardock 15 years ago
Second Degree Green Belt
0
or try the property ISSETUPDRIVEN=1.

sometimes it works!
Posted by: anonymous_9363 15 years ago
Red Belt
0
The VMWare build requires ISSCRIPTENGINE to install InstallShield MSIs.You mean, the OS build which you have on YOUR VMs requires it. VMWare itself doesn't care. Install all the IS engine/driver flavours (we're up to v12, aren't we?) on to your VM's base. I'd suggest doing the same for your standard OS build, too.

ISSETUPDRIVEN won't make any difference at all if the MSI has Custom Actions calling functions in DLLs which aren't present.
Posted by: kardock 15 years ago
Second Degree Green Belt
0
ORIGINAL: VBScab


ISSETUPDRIVEN won't make any difference at all if the MSI has Custom Actions calling functions in DLLs which aren't present.



that's good to know!

thanks!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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