Building of the Production FNP Licensing Toolkit for Trusted Storage may result in the error: Trusted config processing failed : 'publisher\DemoTrustedConfigOut.xml : PublisherId in trusted config does not match that in activation settings

Building of the Production FNP Licensing Toolkit for Trusted Storage may result in the error: Trusted config processing failed : 'publisher\DemoTrustedConfigOut.xml : PublisherId in trusted config does not match that in activation settings

Symptoms:

Building of the Production FNP Licensing Toolkit with the default makefile.act for Trusted Storage may result in the error:

 

.\preptool.exe -v ..\machind\activation\prep_xml\tsactdiag_app.xml
Trusted config procesing failed : 'publisher\DemoTrustedConfigOut.xml : PublisherId in trusted config does not match that in activation settings
XML FATAL ERROR: parsing aborted at line 4
XML parse of configuration file failed.
NMAKE : fatal error U1077: '.\preptool.exe' : return code '0x1'

 

Diagnosis: 

The reason for this error is because the Trusted Configuration files mentioned in the FlexNet Publisher Development Environment Guide provide the steps to create/edit your publisher-specific vendor version of the Trusted Configuration files.  However, it did not include any highlights for prepping for a publisher-specific tsactdiags utility.  

 

 

Solution: 

More information can be found on the FlexNet Publisher Programming Reference for Trusted Storage-Based Licensing Documentation.

 

To address this, you can

 

Option 1:

Remove the following lines on the default makefile.act file so that tsactdiag_app and tsactdiag_svr executables are not prepped.

 

$(PREPTOOL) -v $(APREPXMLDIR)\tsactdiag_app.xml

$(PREPTOOL) -v $(APREPXMLDIR)\tsactdiag_svr.xml

 

Option 2:

1) Update the x64_n6-11.19.0.0_v6\x64_n6\publisher\tsactdiagTrustedConfigIn.xml to match your PublisherID.

 ie. Snippet of the change 

<?xml version="1.0" encoding="utf-8" ?> 

<TrustedConfigInformation xmlns="FLEXnetPublisher_01EFFF13-92D7-469e-B7CC-35E13C2E8D4A">

            <VersionNumber>6</VersionNumber>

            <PublisherId>xxxxx</PublisherId>

            <Id>127</Id>

            <Revision>tsactdiag</Revision>

            <Seeds>

                 <SeedPart>129C6257</SeedPart>

                <SeedPart>94724A4C</SeedPart>

                <SeedPart>A2C5E526</SeedPart>

                <SeedPart>A6AD539B</SeedPart>

                <SeedPart>39C3EAA0</SeedPart>

                <SeedPart>195B47EA</SeedPart>

                <SeedPart>AA11C2B3</SeedPart>

                <SeedPart>A4E93C2C</SeedPart>

            </Seeds>

 

 2) Encrypt the tsactdiagTrustedConfigIn.xml file

\x64_n6-11.19.0.0_v6\x64_n6\publisher>tcencrypt.exe -i tsactdiagTrustedConfigIn.xml -o tsactdiagTrustedConfigOut.xml

Processing complete, config output written to file tsactdiagTrustedConfigOut.xml

 

3) Sign the tsactdiagTrustedConfigOut.xml file

\x64_n6-11.19.0.0_v6\x64_n6\publisher>xmlsign.exe -a ..\ActivationSettings\publisher.xml -i tsactdiagTrustedConfigOut.xml -o tsactdiagTrustedConfigOut.xml

tsactdiagTrustedConfigOut.xml signed..

 

4) Perform your Production build of your FNP toolkit.

 

nmake -f makefile.act clean

nmake -f makefile.act

 

 

 

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Apr 01, 2022 12:13 PM
Updated by:
Revenera
Contributors