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

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
ProcMon, ProcMon, ProcMon, ProcMon, ProcMon, ProcMon....
Answered 04/07/2009 by: VBScab
Red Belt

Please log in to comment
0
The VMWare build requires ISSCRIPTENGINE to install InstallShield MSIs.

Install ISSCRIPTENGINE before u install ur application
Answered 04/07/2009 by: mekaywe
Brown Belt

Please log in to comment
0
or try the property ISSETUPDRIVEN=1.

sometimes it works!
Answered 04/07/2009 by: kardock
Second Degree Green Belt

Please log in to comment
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.
Answered 04/08/2009 by: VBScab
Red Belt

Please log in to comment
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!
Answered 04/08/2009 by: kardock
Second Degree Green Belt

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