Application Name: Serena ChangeMan Version
Application Version:8.1.4
Packaging Tool Used: WISE

I have an Application, which is exe (setup.exe). When extracted I found ISSRIPT engine along with other config file and MSI.

The application has been developed using INSTALLSHIELD.

When I run the MSI, it says that, “Cannot launch MSI without first running setup.exe”.

So, I created a response MST with ISSETUPDRIVEN=1. Now the installation begins, but when the installation takes place, it reached 90% of the installation and then rolls back.

I have logged the installation, but seems no error is mentioned in the log file.

Can anyone suggest me any solution for this?

~many thanks.
sabs
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
Hi,
you need to analyze the log file, to see where the install breaks.
Regards, Nick
Answered 01/20/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
2
G'Day SAB's,

Sounds like a dcom error to me.
Try running this vb script embedded into your mst (type 70) near the beginning of the Exe Immediate/Deferred (after CostInitialize) and again after InstallFinalise. We have done this to all versions of ISScript version files that we deploy without issues.

'This script changes the DCOM Identity for launching applications from the Interactive User mode to the Launching User
'Especially useful when using ISScript applications.
Dim WMIService, WshShell, DComApps, DComApp
Set WMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set WshShell = CreateObject("WScript.Shell")
Set DComApps = WMIService.ExecQuery("Select * from Win32_DComApplicationSetting where Caption='InstallShield InstallDriver' and RunAsUser='Interactive User'")
Set DComApps1 = WMIService.ExecQuery("Select * from Win32_DComApplicationSetting where Caption='InstallShield InstallDriver String Table' and RunAsUser='Interactive User'")
For Each DComApp In DComApps
WshShell.RegDelete "HKEY_CLASSES_ROOT\AppID\" & DComApp.AppID & "\RunAs"
Next
For Each DComApp In DComApps1
WshShell.RegDelete "HKEY_CLASSES_ROOT\AppID\" & DComApp.AppID & "\RunAs"
Next

Regards
Wayne
Answered 01/20/2008 by: WayneB
Blue Belt

Please log in to comment
0
I know it's frowned upon to make direct modifications to vendor apps but with isscript files why couldn't you just change the registry entry in the Registry table from "Interactive User" to "Launching User" Wouldn't this work as well?
Answered 01/25/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
ORIGINAL: joedown

I know it's frowned upon to make direct modifications to vendor apps but with isscript files why couldn't you just change the registry entry in the Registry table from "Interactive User" to "Launching User" Wouldn't this work as well?
It's frowned upon because there's no need to directly edit ANY MSI - just apply a transform.
Answered 01/28/2008 by: VBScab
Red Belt

Please log in to comment
0
VBSCab -> please do not mind , but we are not talking about the MSI to be edited. The problem that I am facing is after creating Transform.

~thanks,sabs.
Answered 01/28/2008 by: sabsbecool
Senior Yellow Belt

Please log in to comment
0
Er, I quoted JoeDown's post and, in the bottom-right corner of my post, it states 'in reply to joedown'...
Answered 01/28/2008 by: VBScab
Red Belt

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