ISscript question

Trying to create a package for Hyperion SmartView 11.1 from Oracle. It's an InstallShield-based MSI: within the exe are one MSI for the app, and one MSI for the InstallShield script engine.

I created a similar package in the past and was able to get everything working just by writing a transform that added the ISSETUPDRIVEN property and setting the value to 1.

But no such luck with the SmartView install. For a few tries I was getting an error that the script engine on the PC was older than the version required to run the setup, but then I got my hands on the InstallShield Scripting Engine merge module, made a transform (following AngelD's instructions from http://itninja.com/question/msi-corporate-standardiser6&mpage=1&#19850 ), and tried again.

My verbose log indicates I get farther now, but I'm not getting an "installed successfully" message in the log. The log ends after listing out all the properties. These are the very last lines of the log:

Property(S): SourcedirProduct = {71CFD50E-282E-4A79-8D8B-2AFC2B1E976D}
Property(S): ProductToBeRegistered = 1
=== Logging stopped: 10/21/2009 10:51:46 ===
MSI (c) (40:48) [10:51:46:471]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (40:48) [10:51:46:487]: MainEngineThread is returning 0
=== Verbose logging stopped: 10/21/2009 10:51:46 ===

On my test PC, the folder structure is correct and the # of files installed is also correct--i.e. they're the same when I compare to a snapshot of having installed the vendor exe. All the functionality seems to be okay, so technically it seems to have been a successful install, but I'm not certain whether to call it a day since my log file never logs an "installed successfully" message.

Assuming I have more work to do, wondering if anyone has any recommendations about what next to try with the package.

Couple other things from AngelD's instructions that I did not have to do: there wasn't a OnCheckSilentInstall custom action to remove from the InstallExecuteSequence table, nor a ISVerifyScriptingRuntime custom action to remove from the InstallUISequence table.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 13 years ago
Red Belt
Don't fret about log entries. If the 'Uninstall' entry exists in the registry, the engine knows that the install completed. If you're checking success or failure programatically, use the WindowsInstaller.Installer object's ProductState property. Much more reliable...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

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

Sign up! or login


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