Hello,

I have an executable I need to run after all my files are installed. This executable is within my .msi file and is installed into the c:\temp directory along with a couple of other files it needs. If I add the Execute Program from Installed Files after InstallFinalize the exe doesn't run (well it runs for a second, but not properly). I've also found that if I try to include a small setup.exe in my installation and try to execute it after the InstallFinalize, it just doesn't work. To go a step further, I created a WiseScript Executable which only launches that setup.exe file. If I put that WiseScript .exe file after the InstallFinalize as a custom action, it does not run (well runs for a second in task manager). After the msi is finished installing, I can then manually run the WiseScript and it works correctly!!!

What exactly is going on here? I just can't seem to successfully run my own .exe or other setup.exe files that I install with an msi. They just don't seem to run at all. Any help would be greatly appreciated. By the way, I'm using Wise Package Studio 5.52.

Thanks

W
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
Could it be because the files being installed are somehow locked, even though I'm putting the custom action after InstallFinalize???
Answered 08/05/2005 by: wiredg
Yellow Belt

Please log in to comment
0
Can you access to your CA Table and InstallExececuteSequence Table ?
Could you post here screenshot of them or describe it ?
Answered 08/05/2005 by: babric
Senior Purple Belt

Please log in to comment
0
CustomAction Table

"SetWizardProperty1","51","WiseCurrentWizard","Welcome_Dialog"
"SetWizardProperty","51","WiseCurrentWizard","Maintenance_Welcome_Dialog"
"SetPatchReinstallMode","51","REINSTALLMODE","omus"
"SetPatchMode","1","Callwisepatch","SetPatchProperties"
"SetARPINSTALLLOCATION","51","ARPINSTALLLOCATION","[INSTALLDIR]"
"WiseNextDlg","6","WiseDlgSequence","WiseNextDlg"
"WisePrevDlg","6","WiseDlgSequence","WisePrevDlg"
"InstallBB","18","setup.exe","/s"


InstallExecuteSequence Table

"AppSearch","","400"
"BindImage","","4346"
"CCPSearch","NOT Installed AND CCP_TEST","500"
"CostFinalize","","1000"
"CostInitialize","","800"
"FileCost","","900"
"LaunchConditions","","100"
"RMCCPSearch","NOT Installed AND CCP_TEST","600"
"ValidateProductID","","700"
"SetPatchReinstallMode","PATCH AND NOT REINSTALLMODE","325"
"SetPatchMode","PATCH","250"
"FindRelatedProducts","","362"
"IsolateComponents","","950"
"MigrateFeatureStates","","1200"
"AllocateRegistrySpace","NOT Installed","1550"
"CreateFolders","","3700"
"CreateShortcuts","","4466"
"DeleteServices","VersionNT","2000"
"DuplicateFiles","","4080"
"InstallFiles","","3968"
"InstallODBC","","5398"
"InstallServices","VersionNT","5798"
"InstallValidate","","1400"
"MoveFiles","","3850"
"PatchFiles","","4040"
"ProcessComponents","","1625"
"PublishComponents","","6161"
"PublishFeatures","","6318"
"PublishProduct","","6400"
"RegisterClassInfo","","4579"
"RegisterExtensionInfo","","4687"
"RegisterFonts","","5298"
"RegisterMIMEInfo","","4895"
"RegisterProduct","","6086"
"RegisterProgIdInfo","","4792"
"RegisterTypeLibraries","","5498"
"RegisterUser","","5998"
"RemoveDuplicateFiles","","3400"
"RemoveEnvironmentStrings","","3300"
"RemoveFiles","","3500"
"RemoveFolders","","3600"
"RemoveIniValues","","3100"
"RemoveODBC","","2400"
"RemoveRegistryValues","","2600"
"RemoveShortcuts","","3200"
"SelfRegModules","","5598"
"SelfUnregModules","","2200"
"SetODBCFolders","","1100"
"StartServices","VersionNT","5898"
"StopServices","VersionNT","1900"
"UnpublishComponents","","1687"
"UnpublishFeatures","","1821"
"UnregisterClassInfo","","2700"
"UnregisterExtensionInfo","","2800"
"UnregisterFonts","","2500"
"UnregisterMIMEInfo","","3000"
"UnregisterProgIdInfo","","2900"
"UnregisterTypeLibraries","","2300"
"WriteEnvironmentStrings","","5198"
"WriteIniValues","","5098"
"WriteRegistryValues","","4997"
"InstallFinalize","","6501"
"InstallInitialize","","1500"
"RemoveExistingProducts","","6700"
"MsiPublishAssemblies","","6239"
"RegisterComPlus","","5698"
"UnregisterComPlus","","2100"
"ScheduleReboot","Not Installed AND WISEDELAYEDREBOOT","6500"
"MsiUnpublishAssemblies","","1743"
"SetARPINSTALLLOCATION","","1300"
"InstallBB","Not Installed","6600"


Thanks,

(Let me know if that's too tough to read, the InstallExecuteSequence Table is too big for a screenshot, but I can take multiple if you need)

W
Answered 08/05/2005 by: wiredg
Yellow Belt

Please log in to comment
0
The funny thing about the setup.exe, if you run it without a command line option, it pops up with a gui (for the setup). If you run it with /s it runs for 2 seconds then disappears (doesn't install). If you run the setup.exe /s manually it works =/.
Answered 08/05/2005 by: wiredg
Yellow Belt

Please log in to comment
0
ORIGINAL: wiredg

The funny thing about the setup.exe, if you run it without a command line option, it pops up with a gui (for the setup). If you run it with /s it runs for 2 seconds then disappears (doesn't install). If you run the setup.exe /s manually it works =/.

If you just execute the setup.exe within the msi can you go finish the installation in GUI mode?
Some legacy installations may not run under the system account due to missing profile settings.
Answered 08/08/2005 by: AngelD
Red Belt

Please log in to comment
0
It's not running under "system" context because it's not deferred.

Try changing the "Type" column of the "CustomAction" table to 3090 (18 + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate) - that may solve the problem.

You'll also need to move the action before "InstallFinalize" ("sequence" 6500 should do it).
Answered 08/09/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Did you try to do the same thing using "stand-alone" .exe as "Notepad.exe".
It would be useful to know if the problem comes from the *.exe or the files installed. (even if you say that *.exe files can be used after the installation).

Then I suggest you to launch Notepad.exe with a *.txt file as parameter. A text file that is included in your package.

Try to work step by step, in order to understand the problem.

Hope that could help.
Answered 08/09/2005 by: babric
Senior Purple Belt

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