installshield appears to hang
Hi
I am trying to deploy an app which requires installshield 11.5
I extracted the 11.5 msi from the application setup.exe and used it to install installshield 11.5
I have created a transform for my packaged app and when I go to test it sometimes it works and other times it just hangs on "Preparing to install".
I have logged both the successful and unsuccessful attempts to install and below is the section that I think is causing the problem (both from the install that works and the one that doesn't).
I have read a lot about the DCOM permissions needing to be set for isscript which I have done. What puzzles me is why it runs sometimes but not others. Thanks
G
*** Section from log where it works ***
MSI (c) (70:98) [13:52:04:225]: Doing action: ISStartup
Action start 13:52:04: ISStartup.
MSI (c) (70:98) [13:52:04:240]: Transforming table CustomAction.
MSI (c) (70:F8) [13:52:04:240]: Cloaking enabled.
MSI (c) (70:F8) [13:52:04:240]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (70:F8) [13:52:04:240]: Connected to service for CA interface.
MSI (c) (70:98) [13:52:04:240]: Transforming table Binary.
MSI (c) (70:50) [13:52:04:240]: Invoking remote custom action. DLL: C:\DOCUME~1\name\LOCALS~1\Temp\MSI6.tmp, Entrypoint: StartUp
....
*** Section from log where it doesn't work ***
Action start 14:59:35: ISStartup.
MSI (c) (88:9C) [14:59:35:188]: Transforming table CustomAction.
MSI (c) (88:9C) [14:59:35:188]: Transforming table Binary.
MSI (c) (88:E8) [14:59:35:344]: Invoking remote custom action. DLL: C:\DOCUME~1\name\LOCALS~1\Temp\MSI2.tmp, Entrypoint: MsiServerStartup
MSI (c) (88:9C) [14:59:35:344]: Cloaking enabled.
MSI (c) (88:9C) [14:59:35:344]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (88:9C) [14:59:35:344]: Connected to service for CA interface.
1: ISStartUp Failure. OpenEvent, Error = 0x2
Action ended 14:59:36: ISStartup. Return value 3.
....
I am trying to deploy an app which requires installshield 11.5
I extracted the 11.5 msi from the application setup.exe and used it to install installshield 11.5
I have created a transform for my packaged app and when I go to test it sometimes it works and other times it just hangs on "Preparing to install".
I have logged both the successful and unsuccessful attempts to install and below is the section that I think is causing the problem (both from the install that works and the one that doesn't).
I have read a lot about the DCOM permissions needing to be set for isscript which I have done. What puzzles me is why it runs sometimes but not others. Thanks
G
*** Section from log where it works ***
MSI (c) (70:98) [13:52:04:225]: Doing action: ISStartup
Action start 13:52:04: ISStartup.
MSI (c) (70:98) [13:52:04:240]: Transforming table CustomAction.
MSI (c) (70:F8) [13:52:04:240]: Cloaking enabled.
MSI (c) (70:F8) [13:52:04:240]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (70:F8) [13:52:04:240]: Connected to service for CA interface.
MSI (c) (70:98) [13:52:04:240]: Transforming table Binary.
MSI (c) (70:50) [13:52:04:240]: Invoking remote custom action. DLL: C:\DOCUME~1\name\LOCALS~1\Temp\MSI6.tmp, Entrypoint: StartUp
....
*** Section from log where it doesn't work ***
Action start 14:59:35: ISStartup.
MSI (c) (88:9C) [14:59:35:188]: Transforming table CustomAction.
MSI (c) (88:9C) [14:59:35:188]: Transforming table Binary.
MSI (c) (88:E8) [14:59:35:344]: Invoking remote custom action. DLL: C:\DOCUME~1\name\LOCALS~1\Temp\MSI2.tmp, Entrypoint: MsiServerStartup
MSI (c) (88:9C) [14:59:35:344]: Cloaking enabled.
MSI (c) (88:9C) [14:59:35:344]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (88:9C) [14:59:35:344]: Connected to service for CA interface.
1: ISStartUp Failure. OpenEvent, Error = 0x2
Action ended 14:59:36: ISStartup. Return value 3.
....
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
rbc827
14 years ago
I had the same problem trying to install Smartview through an SMS deployment. I know this is an old thread, but I wanted to share with you what I did to get this app installed.
The issue is with ISScript10.exe changing the DCOM permissions to interactive user. You need to extract the ISScript10.exe from the Smartview package. I created a WISE script to do the following:
1. Install ISScript10.exe (silently)
2. Run this vbscript to modify the DCOM settings
3. Install Smartview.exe (silently)
vbscript:
Const HKEY_CLASSES_ROOT = &H80000000
On Error Resume Next
Set objShell = CreateObject("WScript.Shell")
strComputer = "."
Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
strComputer & "\root\default:StdRegProv")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_DCOMApplicationSetting",,48)
For Each objItem in colItems
If objItem.Description <> "" Then
arrFind=Split(objItem.Description)
For i=0 To UBound(arrFind)
If lcase(arrFind(i))="installshield" then
strKeyPath = "AppID\" & objItem.AppID
strEntryName = "RunAs"
strValue = ""
objReg.DeleteValue HKEY_CLASSES_ROOT,strKeyPath,strEntryName
End if
Next
End If
Next
The issue is with ISScript10.exe changing the DCOM permissions to interactive user. You need to extract the ISScript10.exe from the Smartview package. I created a WISE script to do the following:
1. Install ISScript10.exe (silently)
2. Run this vbscript to modify the DCOM settings
3. Install Smartview.exe (silently)
vbscript:
Const HKEY_CLASSES_ROOT = &H80000000
On Error Resume Next
Set objShell = CreateObject("WScript.Shell")
strComputer = "."
Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
strComputer & "\root\default:StdRegProv")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_DCOMApplicationSetting",,48)
For Each objItem in colItems
If objItem.Description <> "" Then
arrFind=Split(objItem.Description)
For i=0 To UBound(arrFind)
If lcase(arrFind(i))="installshield" then
strKeyPath = "AppID\" & objItem.AppID
strEntryName = "RunAs"
strValue = ""
objReg.DeleteValue HKEY_CLASSES_ROOT,strKeyPath,strEntryName
End if
Next
End If
Next
Posted by:
jmcfadyen
16 years ago
check to see if there are any processes running starting with _Is-xxxxxx usually it fails when other processes are still hanging around.
Posted by:
DevilsArcade
15 years ago
I've been having this same issue with an application called Hyperion Smartview. I extracted the isscript10.msi and smartview.msi, and am running issscript first, smartview second. Same issue - isscript installs fine, but the smartview install appears to hang on - "please wait while windows configures....". i'd say it happens most of the time, not all.
if you end the idriver process, and the hanging msiexec processes, then delete the contents of C:\Program Files\Common Files\InstallShield\Driver directory, THEN run isscript.msi then your smartview (in my case) msi will work.
the problem is, when you go to remove the application from add\remove programs, it will hang there. you will notice the idriver process has started up again.
there has to be a better way. thoughts anyone??
if you end the idriver process, and the hanging msiexec processes, then delete the contents of C:\Program Files\Common Files\InstallShield\Driver directory, THEN run isscript.msi then your smartview (in my case) msi will work.
the problem is, when you go to remove the application from add\remove programs, it will hang there. you will notice the idriver process has started up again.
there has to be a better way. thoughts anyone??
Posted by:
anonymous_9363
15 years ago
In both cases, I'd say that this is the DCOM permissions issue.
@Graeme, you say you've "done" this: have you checked that the change is in place before executing your package? Bear in mind, if you're using the DCOM-changing script that's floating around, that it doesn't contain ALL the GUIDs you might need for the different IS versions.
@Graeme, you say you've "done" this: have you checked that the change is in place before executing your package? Bear in mind, if you're using the DCOM-changing script that's floating around, that it doesn't contain ALL the GUIDs you might need for the different IS versions.
Posted by:
anonymous_9363
14 years ago
Nice script (apart from the total absence of error-trapping) but somewhat superfluous. Plus, of course, the executing user requires local administrator rights or, at the very least, write access to the HKLM registry hive.
Inside the EXE is an MSI. Extract the MSI, remove the offending registry entry via a transform and deploy (silently).
Inside the EXE is an MSI. Extract the MSI, remove the offending registry entry via a transform and deploy (silently).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
