TD14SP1: How to generate a list of OOTB files in preparation for upgrade diffing?

Hi all. I understand a key task in upgrading is diffing the as-configured version of the file and the OOTB version of the file. In case we are unable to find OOTB files, I believe they can be regenerated by running ..\__InstallTool\InstallTool.exe using the installer account with parameter values 4 / 1 / 0 / relpath to installplan.xml / relpath to inputparameters.xml / outputlocation:

Screenshot of Trados Studio InstallTool.exe console with options to choose actions such as Maintenance, Install, Uninstall, and Backup. Install plan and input parameters locations are specified as relative paths.

Upon starting, I can't tell if the yellow text represents one error or two independent ones.

Error message in Trados Studio InstallTool.exe indicating 'The path is not of a legal form.' and 'InputParameter 'connectionstring' is invalid'. Access to the path 'C:Program FilesWindows Defender Advanced Threat ProtectionClassificationConfiguration' is denied.

I've tried various combinations, e.g.

Install Plan Location

Input Parameters Location

Backup Location

<enter>

<enter>

<enter>

.\installplan.xml (which is true)

.\inputparameters.xml (also true)

<enter>

<enter>

<enter>

D:\

<enter>

<enter>

D:\mybackup.zip

.\installplan.xml

.\inputparameters.xml

D:\mybackup.zip

D:\SDL\20191206.CD.InfoShare.14.0.3606.1.Trisoft-DITA-OT\__InstallTool\installplan.xml

D:\SDL\20191206.CD.InfoShare.14.0.3606.1.Trisoft-DITA-OT\__InstallTool\inputparameters.xml

D:\mybackup.zip

D:\SDL\20191206.CD.InfoShare.14.0.3606.1.Trisoft-DITA-OT\__InstallTool\installplan.xml

D:\SDL\20191206.CD.InfoShare.14.0.3606.1.Trisoft-DITA-OT\__InstallTool\inputparameters.xml

D:\

They all fail in a manner identical to above. The Documentation Center article is… sparse.

  1. Am I on the right track to generate a set of OOTB files?
  2. What am I doing wrong? What path is the executable telling me is wrong?


Generated Image Alt-Text
[edited by: Trados AI at 6:41 AM (GMT 0) on 5 Mar 2024]
emoji
Parents
  • Hi Syed,

    On the "The path is not of legal form", we noticed that Microsoft rolled out some more "strict" security thing that blocks us from probing your AntennaHouse location in your C:\Program Files folder. As the probing passes "C:\Program Files\Windows Defender Advanced Threat Protection\Classification\Configuration" where InstallTool gets a security exception in turn resulting in your visible error messages.

    The simple workaround is to bypass the probe by offering a ps_fo_processor parameter entry in the inputparameters.xml file you are using.

    [...]
    <param name="ps_fo_processor">
    <currentvalue>C:\Program Files\Antenna House\AHFormatterV70\AHFCmd.exe</currentvalue>
    <defaultvalue>C:\Program Files\Antenna House\AHFormatterV6\AHFCmd.exe</defaultvalue>
    <description>The full file path to an xsl fo processor which uses the same command line options as AntennaHouse XSLFormatter. This allows you to indicate your path and possibly switch between compatible versions. Note: do not use environment variables or quote your file path.</description>
    <validate>filepath</validate>
    </param>
    [...]

    -Dave

    SRQ-13760

  • Hi Dave. I've asked, and we don't use FO or AntennaHouse. If we implement this, but aren't using either, will it work? I can't experiment too much as it's a client-owned machine. :-) FYI.

Reply Children
No Data