MSI calls the setup.exe to be executed
When i double click on msi,It displays "Execute the setup.exe to be executed".
The source has a ISScript with it. I have tried installing the application after installing ISScript.msi, But even the main msi misses many features of the application (E.g Shortcuts, registry entries, etc.,)
And the setup capture also is not possible....
This also misses most of the features of the application.
Could any one help me to fix this issue?
Thanks,
Meil
The source has a ISScript with it. I have tried installing the application after installing ISScript.msi, But even the main msi misses many features of the application (E.g Shortcuts, registry entries, etc.,)
And the setup capture also is not possible....
This also misses most of the features of the application.
Could any one help me to fix this issue?
Thanks,
Meil
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Normally, you can prevent that message appearing by specifying the property ISSETUPDRIVEN with a value of '1'.
To test, do that using a command line and, if it's successful, create a transform for the MSI containing that property/value pair.
Example command line:
Example using your transform, once created:
(Note: 'TRANSFORMS', plural, not 'TRANSFORM')
BTW, this is the wrong forum for your post. This forum is concerned with errors returned from the Windows Installer engine. It really belongs in the 'Package Development' forum. A moderator may move it.
To test, do that using a command line and, if it's successful, create a transform for the MSI containing that property/value pair.
Example command line:
MSIExec /i [path_to_and_name_of_MSI] ISSETUPDRIVEN=1 [other_switches]Example using your transform, once created:
MSIExec /i [path_to_and_name_of_MSI] TRANSFORMS="[path_to_and_name_of_MST]" [other_switches](Note: 'TRANSFORMS', plural, not 'TRANSFORM')
BTW, this is the wrong forum for your post. This forum is concerned with errors returned from the Windows Installer engine. It really belongs in the 'Package Development' forum. A moderator may move it.
Posted by:
troy_in_wi
14 years ago
I tried using the command line that VBScab provided, but I still get the error message: "Please install Adobe Setup using setup.exe".
Any idea of other options? Maybe try using an MST or maybe crack open the MSI and see if it will let me edit it?
UPDATE: I could not edit and save the MSI using Wise Package Studio, so I edited it with Orca. I found the LaunchCondition table had a row for ADOBE_SETUP or UPGRADINGPRODUCTCODE with the Description was "Please install [ProductName] using Setup.exe". I deleted that row. The MSI would not give the error, but I still don't think it worked because the Log ended with: "Product: Adobe Setup -- Installation operation failed."
Any idea of other options? Maybe try using an MST or maybe crack open the MSI and see if it will let me edit it?
UPDATE: I could not edit and save the MSI using Wise Package Studio, so I edited it with Orca. I found the LaunchCondition table had a row for ADOBE_SETUP or UPGRADINGPRODUCTCODE with the Description was "Please install [ProductName] using Setup.exe". I deleted that row. The MSI would not give the error, but I still don't think it worked because the Log ended with: "Product: Adobe Setup -- Installation operation failed."
Posted by:
anonymous_9363
14 years ago
It would have helped to have specified that you're dealing with an Adobe product: you could have saved a shed-load of time.
Do not, not, NOT edit vendor MSIs, especially not Adobe's abortions. Adobe has available cusomisation tools for their products. Use the appropriate tool for whichever product it is and go from there.
As it sounds like you're trying to avoid running the set-up stub, I'll bet you're going to be deploying with Group Policy? Some of the CS4 products have a raft of MSIs which you need to deploy. Check out AppDeploy's 'Package KB' for any specific guidance on GP for your product.
I edited it with Orca.No, no, no, no, no, NO!
Do not, not, NOT edit vendor MSIs, especially not Adobe's abortions. Adobe has available cusomisation tools for their products. Use the appropriate tool for whichever product it is and go from there.
As it sounds like you're trying to avoid running the set-up stub, I'll bet you're going to be deploying with Group Policy? Some of the CS4 products have a raft of MSIs which you need to deploy. Check out AppDeploy's 'Package KB' for any specific guidance on GP for your product.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
