Adobe Flash Player 10.0.22.87 Installer Hangs
Adobe Flash Player 10.0.22.87 hangs on several machines during my GP deployment as well as during manual installation. If found that by killing the "ns452.tmp" process (numbers in process name are random) that the installation will finish successfully. I created the below VBScript which actively looks for *.tmp processes and kills them but am having issues adding this into an MST so that I can incorporate it in my GP deployment.
Has anyone experienced this hanging issue before? If so, is there a better workaround than the one I'm working on?
Can anyone assist in helping me get the below script to run before the actual MSI runs? I'm currently using WISE, created new MST, and have added a custom action "Call VBScipt From Embedded Code" just above InstallFinalize on the Execute Immediate tab. If run msiexec and include the mst file, I get "Error 2762. Cannot write script record. Transaction not started." The sequence number for my custom action in the InstallExecuteSequence table is 69 when InstallFinalize is 70.
If I run this script manually, then run the MSI installer manually, it works fine by actively scanning the process list and then kills any *.tmp processes so that the MSI can finish installing.
**********************
WaitTime = 60 'in seconds
EndTime = DateAdd("s",WaitTime, Now)
While EndTime > Now()
Set SWBemlocator = CreateObject("WbemScripting.SWbemLocator")
Set objWMIService = SWBemlocator.ConnectServer(".","root\CIMV2","","")
Set colItems = objWMIService.ExecQuery("Select * from Win32_Process WHERE Name Like '%.tmp'",,48)
For Each objItem In colItems
strString = "Win32_Process.Handle=" & objItem.ProcessID
Set objProcessToKill = objWMIService.Get(strString)
nResult=objItem.Terminate(0)
Next
Wend
**********************
Has anyone experienced this hanging issue before? If so, is there a better workaround than the one I'm working on?
Can anyone assist in helping me get the below script to run before the actual MSI runs? I'm currently using WISE, created new MST, and have added a custom action "Call VBScipt From Embedded Code" just above InstallFinalize on the Execute Immediate tab. If run msiexec and include the mst file, I get "Error 2762. Cannot write script record. Transaction not started." The sequence number for my custom action in the InstallExecuteSequence table is 69 when InstallFinalize is 70.
If I run this script manually, then run the MSI installer manually, it works fine by actively scanning the process list and then kills any *.tmp processes so that the MSI can finish installing.
**********************
WaitTime = 60 'in seconds
EndTime = DateAdd("s",WaitTime, Now)
While EndTime > Now()
Set SWBemlocator = CreateObject("WbemScripting.SWbemLocator")
Set objWMIService = SWBemlocator.ConnectServer(".","root\CIMV2","","")
Set colItems = objWMIService.ExecQuery("Select * from Win32_Process WHERE Name Like '%.tmp'",,48)
For Each objItem In colItems
strString = "Win32_Process.Handle=" & objItem.ProcessID
Set objProcessToKill = objWMIService.Get(strString)
nResult=objItem.Terminate(0)
Next
Wend
**********************
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
aogilmor
15 years ago
vbscript from embedded code has a character limit - I never use them for that reason (also it sucks to edit them). Put it in the binary table and see if that works. In Wise, that'd be vbscript from installation IIRC.
Personally though I've never seen this problem through multiple versions of Flash, so you may want to check out adobe's web site as well.
Good luck and let us know how it goes!
Personally though I've never seen this problem through multiple versions of Flash, so you may want to check out adobe's web site as well.
Good luck and let us know how it goes!
Posted by:
bearden3
15 years ago
Hi.
I didn't have that problem but know what you are talking about.
I don't know if this will help you but we use a wrapper here. I did the following for the package:
Created a text file named mms.cfg. In the text file I added the line "AutoUpdateDisable=1" and saved it to my network source folder where the install for Flash Player 10.0.22.87 is located. I then used the wrapper to:
1. call "Install Flash Player 10 ActiveX.exe" with a /s for silent (e.g. drive:\app\source\Install Flash Player 10 ActiveX.exe /s)
2. copy the mms.cfg file to C:\WINDOWS\system32\Macromed\Flash (this will disable the check of automatic updates)
The install also creates a log file that is put into c:\windows\system32\macromed\flash\install.log. Since we keep the installer log files, I also copied that file to an application log file folder.
Hope that helps.
-Lewis
I didn't have that problem but know what you are talking about.
I don't know if this will help you but we use a wrapper here. I did the following for the package:
Created a text file named mms.cfg. In the text file I added the line "AutoUpdateDisable=1" and saved it to my network source folder where the install for Flash Player 10.0.22.87 is located. I then used the wrapper to:
1. call "Install Flash Player 10 ActiveX.exe" with a /s for silent (e.g. drive:\app\source\Install Flash Player 10 ActiveX.exe /s)
2. copy the mms.cfg file to C:\WINDOWS\system32\Macromed\Flash (this will disable the check of automatic updates)
The install also creates a log file that is put into c:\windows\system32\macromed\flash\install.log. Since we keep the installer log files, I also copied that file to an application log file folder.
Hope that helps.
-Lewis
Posted by:
ef46@cornell.edu
15 years ago
Posted by:
anonymous_9363
15 years ago
If found that by killing the "ns452.tmp" process (numbers in process name are random) that the installation will finish successfully.When you find yourself faced with the front door of your house and unable to find your key straight away, is your solution to drive your car through the doorway? I suspect not. You might find it more sensible to spend some time looking for the key, right?
It would be so much more sensible to find out WHY that process is hanging, wouldn't it? My suspicion would be that it's trying to write or delete a file (or registry entry) to which the installing account has no rights, displaying once again Adobe's stunning grasp of error-trapping in its applications.
Posted by:
ef46@cornell.edu
15 years ago
Posted by:
deepak_2007
15 years ago
Posted by:
anonymous_9363
15 years ago
....and this has what to do with 'Scripting'? Please try and post in the appropriate forum. Then, you could go mad and try using Google. http://www.adobe.com/support/flashplayer/downloads.html
You'll probably find that the d/l is an EXe which extracts an executes an MSI so follow the usual practice for that type of installer.
You'll probably find that the d/l is an EXe which extracts an executes an MSI so follow the usual practice for that type of installer.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.