/build/static/layout/Breadcrumb_cap_w.png

Prob with a MST file and Silent installation mode

Hi,

I create a MST file with the serial number of my application.
It's work in normal installation mode (Next, Next, Next ...)
But i receive a error message when i try in silent mode (the serial number is not valid)
Could you help me?

Thanks in advance

0 Comments   [ + ] Show comments

Answers (11)

Posted by: yshariff 16 years ago
Orange Senior Belt
0
Pass the property PIDKEY="License Key"....... in the property section..
Posted by: jcb0203 16 years ago
Senior Yellow Belt
0
I don't have a PIDKEY.
I just have a ISX_SERIALNUM key.
It's the same?
Posted by: yshariff 16 years ago
Orange Senior Belt
0
Yes its the same and PIDKEY is the Property that is passed along with the values. ie your serial number.

For example.

In Property tab enter the propert name as PIDKEY
and in the value tab enter the value as in your serial number ( Note: serial number entered should be without spaces of dashes).

Hope it helps you install silently.[:)]
Posted by: jcb0203 16 years ago
Senior Yellow Belt
0
I create the ISX_SERIALNUM property with the good serial number.
If a launch the test without argument (like msiexec /i XXXX.msi TRANSFORMS=xxxx.mst), the serial number field is correct and i can click on the next button and install my application without any problems.
But when i try whit MSIEXEC /i XXX.msi TRANSFORMS=XXX.mst /qb or /qn, i have a error message (the serial number is not valid or somthing like that)

I don't understant why

Have you an idea?

Thanks
Posted by: yshariff 16 years ago
Orange Senior Belt
0
I am not sure why are you getting a wiered error. Try only /q instead of /qn or /qb . and also try to use /v to pass these command lines to the WI.
Posted by: cbohs 16 years ago
Senior Yellow Belt
0
Is the application Adobe professional or standard? If so then you need to use the Adobe Configuration Wizard to create the mst. You can get this utility from the adobe web site.
Posted by: jcb0203 16 years ago
Senior Yellow Belt
0
That's a application to convert in pdf format but that's not acrobat.
It's PDF Convertor Professional 5.

I try with only /q but that's the same probleme.

Thnks
Posted by: anonymous_9363 16 years ago
Red Belt
0
Yes its the same and PIDKEY is the Property that is passed along with the values. ie your serial number What gives you that idea?!? JCB, ignore that advice.

Try only /q instead of /qn or /qb
The /Q switch requires a following character (an 'n', 'b', 'r' or 'f'). The entire command line is ignored without it.

Now, to the problem...

Almost without question, there is a Custom Action which sets the property for the serial number. That CA is probably set to only execute in the User Interface sequence. Naturally, when you use the '/Qx' switch, there is no user interface and therefore no CAs which atre unique to that sequence get executed. You need to change the CA so that is executed at least once during an install. How you do that depends on what tool you're using to edit your transform.
Posted by: jcb0203 16 years ago
Senior Yellow Belt
0
Hi,

I create my mst with the Tuner of admin Studio 8.6 and i edit this with installshield.
What can i do to change the custom action?

Thanks
Posted by: yshariff 16 years ago
Orange Senior Belt
0
[font="courier new"]Try This command Line it may help you.[:)]
[font="courier new"]
[font="courier new"]APP.msi /qn /L*v c:\fcinstall.log ISX_LICENSE=1234567890abc
[font="courier new"]
Posted by: jcb0203 16 years ago
Senior Yellow Belt
0
Hi,

I changed the sequence in the CA who check serial number and now it's working.

Thanks a lot all for your help

JCB
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ