I am creating an MSI to execute the silent install command.
When executing the silent install command, from a DOS-prompt, the installation is fine.
When executing the silent install command from the MSI, the installation stops with Exit Code 7.
The install-log reveals the following:

*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= *=*=*
UninstallBootstrapperOperation: Changed working directory to C:\
Uninstalling bootstrapper
[ 840] Wed Apr 15 11:46:52 2009 INFO
Checking bootstrapper progress
[ 840] Wed Apr 15 11:46:52 2009 FATAL
Exception: JavaScript Support file could not be loaded: ReferenceError: systemCheck_wp is undefined
Exit code: 7
[ 840] Wed Apr 15 11:46:52 2009 INFO
-----------------------------------------------------------------
------------------ END Silent Installer Session -----------------
My installscript-code is:

#include "ifx.h"
HWND hMSI;
export prototype Install_CS4(HWND);
// Global variables
function Install_CS4(hMSI)
STRING Source, InstComm, InstOpt;
NUMBER nReturn, MaxSize;
begin
MsiGetProperty(hMSI, "SrcDir", Source, MaxSize);
InstComm = Source ^ 'Setup.exe" --mode=Silent --DeploymentFile="' + Source ^ 'Install.xml';
LongPathToQuote(InstComm, TRUE);
MessageBox("InstComm is:" + InstComm, INFORMATION);
MaxSize = 255;
nReturn = LaunchAppAndWait(InstComm,"", LAAW_OPTION_WAIT);
MessageBox("Afsluttet, nReturn = ", INFORMATION);
end;
The MSI is located in the same folder as the sourcefiles.
Is there anyone who have tried the to install it a similar way.
I have tried to install it from a Batch file as well. When it is run by hand, the installation completes ok. When called from the MSI, same problem (Exit Code 7, same entries in the install.log).
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
Why complicate things by trying to run an MSI from within an MSI (the CS apps all extract and use MSIs)?

Use the appropriate Adobe customisation tool to create a transform, having noted and executed any necessary changes detailed in AppDeploy's 'Package KB' and many, many posts about these apps.
Answered 04/16/2009 by: VBScab
Red Belt

Please log in to comment
0
Take my suggestion,now when you are member of Appdeploy whenevr you work on package customization at initial tech review phase only check for KB article for same on the Appdeploy link.
You will get right direction to proceed while creating package out of it.
As suggested by Ian extract MSI from source and use Adobe customization tool,you will be able to create package smoothly.
Answered 04/16/2009 by: raviray
Orange Belt

Please log in to comment
0
Thank you, for your answers, both of you.

The reason why I try to create the MSI, is that I the DeploymentTool we are using for now (sniik), does not wait for the Setup.exe to finish, before it goes on to the next package in line.
Therefore there is a risk, that the next package requires a reboot, and will do so during the Adobe CS4 installation.

It will wait for MSI-files to finish.
I haven't been able to find a way to solve my problem using Google.
Answered 04/16/2009 by: Cool1_dk
Yellow Belt

Please log in to comment
0
Hi RRay.

In regards to the first link, it seems that CS4 does not create a SuiteInstaller.log.
The second link is how I created the install files in the first place.

I do not understand why I it does not install correct when initiated from an msi, when the same command run by hand installs correct.

Anyways, thank you once again for your help.
/Cool1_Dk
Answered 04/17/2009 by: Cool1_dk
Yellow Belt

Please log in to comment
0
Where a vendor uses a set-up stub to launch an MSI, I *always* :

- install my MSI/MST
- start a lightweight snapshot tool (e.g. In Control, InstallWatch) and take a 'Before' snap
- rename the ProductCode key in the registry's 'Uninstall' branch (to fool the WI engine into re-installing, rather than offering the Repair/Modify/Remove option)
- run the stub, making sure you complete all dialogs the same as when creating the MST
- take an 'After' snapshot.
- add any relevant changes to my MST

It never ceases to amaze me how many vendors include stuff in their stubs which really ought to be in the MSI.
Answered 04/17/2009 by: VBScab
Red Belt

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