I've been using installshield tuner to create a mst file for acrobat 7 pro. This works if I install the package using the setup.exe. When distributing this package using sms, the setup.exe is launching the msi file, and then terminates the setup.exe. This causes SMS to think that the installation is finished and sms disconnects the distribution share, and the msi install fails.

I've tried to execute the msi directly, but this gives me a LICENSE number error. Is there any workaround for this?

Why do Installshield create custom tasks in the setup.exe file? Why can't they create true msi files?
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
Hi Magnarj:

if you try to run the MSI directly then it wont read the setup.ini file provided with the setup. Since MSI's cannot read ini or text files at the time of their execution for parameters, thats why a setup.exe has been created that would read the ini and would then run the installation(that is MSI). However in case you want to run the MSI thru the command line silently without it asking you the license number, follow the steps:

1. go to the setup folder
2. open the setup.ini file or abcpy.ini and copy this line ISX_SERIALNUMBER=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
3. type in msiexec /i abc.msi ISX_SERIALNUMBER=your serial number that you copied

Now it will not ask you to enter license number, try this one in case doesnt work leave a msg.

Take Care.




Edited to remove serial number: do not post serial numbers! - Bob Kelly
Answered 08/23/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Hi Bob:

I am sorry to post that serial number but in any case that was a tryout product serial number and was not a production one. I will still make it a point not to do this in future.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Thanks for the answer, i'll try it. I think I did this on the Acrobat 6, package. Strange how I could forget about this. I thought the MST file would include this property.
Answered 08/29/2005 by: magnarj
Senior Yellow Belt

Please log in to comment
0
i'm having the same issue in wise package studio... does this command work as well?
Answered 08/29/2005 by: joshrys
Yellow Belt

Please log in to comment
0
ok i tried this just now and i still get the error. I am using this command:

C:\WINNT\system32\MSIEXEC.EXE TRANSFORMS="\\server\share\Wise Share Point\Projects\Adobe reader\AcroStan.mst" /i "\\server\share\Wise Share Point\Projects\Adobe reader\AcroStan.msi" ISX_SERIALNUMBER=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx /qb+

also tried putting the serial # into the ini file, no workie.
Answered 08/29/2005 by: joshrys
Yellow Belt

Please log in to comment
0
that would be because adobe pro doesnt like being hidden
you cant use any /qb or qr switches or similar, its a known adobe problem as pointed out here
the only way i have deployed this is with an adobe progress screen visible
Answered 08/29/2005 by: ictu packager
Orange Belt

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