/build/static/layout/Breadcrumb_cap_w.png

Problem with MST File

Hi,

I'm using Wise to create a transform file for Business Objects 6.1. This is my first real transform file (besides off2k). I deselect the features I don't want installed, but when the install runs, all other custom settings stick except for the features list. I'm using WISE to create the MST File.

Any thoughts?

Chris.

0 Comments   [ + ] Show comments

Answers (10)

Posted by: bkelly 20 years ago
Red Belt
2
Hi Chris,

Are you using the InstallTailor tool to answer the installation choices you wish or are you creating a MST in the Editor directly? I recommend the former. Also, by what means are you calling the installation with the MST? If by command line, please post the command line you are using and remember: the property for specifying MST files is TRANSFORMS="MySettings.mst" (plural and in CAPS)
Posted by: jdelgadillo 20 years ago
Senior Yellow Belt
1
Good Morning Chris,

Just an FYI, I have had some exp. with B.O. 5.x so let me know if you have any questions. Also, what ver. / product are you using from WISE?

Jeff
Posted by: usachrisk 20 years ago
Purple Belt
1
It was a big pain in the butt, but I did figure it out. It's been a while, but what I did was use the MST file as well as the ADDLOCAL= option. My command line looked like this:

setup.exe /w /s /v"/QN /L*v c:\temp\bo6inst.log REBOOT=Supress ADDLOCAL=bo.AccessPacks,bo.rdbms,bo.rdbms.Oracle,bo.rdbms.OracleClient,bo.rdbms.Microsoft,bo.rdbms.MSAccessODBC,bo.rdbms.MSSQLServerODBC,bo.rdbms.IBMDB2,bo.rdbms.IBMDB2Client,bo.rdbms.IBMDB2ODBC,bo.rdbms.ODBC,bo.rdbms.ODBC2,bo.rdbms.ODBC3,bo.3TierBusinessObjects,bo.BusinessObjectsHelp,bo.BusinessObjectsDoc,bo.Demos,bo.DemoKit,bo.QuickTour,bo.BusinessObjectsReporter,bo.BusinessObjectsExplorer TRANSFORMS=\MSTs\BO6STD.MST "

The space before the last quote was required. I got the list of things to include after ADDLOCAL= by looking at the MSI in Wise.
Posted by: Wozik 20 years ago
Orange Belt
1
I think that CAPS isn't needed in this case. Transforms works without CAPS as well.

Wozik
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
1
Actually I think you do need the caps to declare the public properties correctly. Windows Installer will see they are declared public properties and treat them as such.
Posted by: Wozik 20 years ago
Orange Belt
1
OK, could you explain me the difference between public property and the second one that I don't know its name?

Wozik
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
1
Public properties are properties which can be placed in the msi and then altered or redefined in the command line installation. Not all properties can be altered from the command line.
Posted by: FunnyName 19 years ago
Senior Yellow Belt
1
setup.exe /w /s /v"/QN /L*v c:\temp\bo6inst.log REBOOT=Supress ADDLOCAL=bo.AccessPacks,bo.rdbms,bo.rdbms.Oracle,bo.rdbms.OracleClient,bo.rdbms.Microsoft,bo.rdbms.MSAccessODBC,bo.rdbms.MSSQLServerODBC,bo.rdbms.IBMDB2,bo.rdbms.IBMDB2Client,bo.rdbms.IBMDB2ODBC,bo.rdbms.ODBC,bo.rdbms.ODBC2,bo.rdbms.ODBC3,bo.3TierBusinessObjects,bo.BusinessObjectsHelp,bo.BusinessObjectsDoc,bo.Demos,bo.DemoKit,bo.QuickTour,bo.BusinessObjectsReporter,bo.BusinessObjectsExplorer TRANSFORMS=\MSTs\BO6STD.MST "

I think you mis a quote, try the following CMD-Line:

setup.exe /w /s /v"/QN /L*v c:\temp\bo6inst.log REBOOT=Supress ADDLOCAL=bo.AccessPacks,bo.rdbms,bo.rdbms.Oracle,bo.rdbms.OracleClient,bo.rdbms.Microsoft,bo.rdbms.MSAccessODBC,bo.rdbms.MSSQLServerODBC,bo.rdbms.IBMDB2,bo.rdbms.IBMDB2Client,bo.rdbms.IBMDB2ODBC,bo.rdbms.ODBC,bo.rdbms.ODBC2,bo.rdbms.ODBC3,bo.3TierBusinessObjects,bo.BusinessObjectsHelp,bo.BusinessObjectsDoc,bo.Demos,bo.DemoKit,bo.QuickTour,bo.BusinessObjectsReporter,bo.BusinessObjectsExplorer TRANSFORMS="\MSTs\BO6STD.MST "
Posted by: usachrisk 19 years ago
Purple Belt
1
I think you mis a quote, try the following CMD-Line:

setup.exe /w /s /v"/QN /L*v c:\temp\bo6inst.log REBOOT=Supress ADDLOCAL=bo.AccessPacks,bo.rdbms,bo.rdbms.Oracle,bo.rdbms.OracleClient,bo.rdbms.Microsoft,bo.rdbms.MSAccessODBC,bo.rdbms.MSSQLServerODBC,bo.rdbms.IBMDB2,bo.rdbms.IBMDB2Client,bo.rdbms.IBMDB2ODBC,bo.rdbms.ODBC,bo.rdbms.ODBC2,bo.rdbms.ODBC3,bo.3TierBusinessObjects,bo.BusinessObjectsHelp,bo.BusinessObjectsDoc,bo.Demos,bo.DemoKit,bo.QuickTour,bo.BusinessObjectsReporter,bo.BusinessObjectsExplorer TRANSFORMS="\MSTs\BO6STD.MST "


It worked fine for me, and it now would appear you have mismatched quotes. Once after /v, once after TRANSFORMS= and one at the end. Three quotes will likely error out.
Posted by: MSIMaker 19 years ago
2nd Degree Black Belt
1
Now my wish list extends to Active Directory allowing the use of commandline options for msi installs.....of course it wont happen but its a nice wish.
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