Summary

Error: 7570:The publisher ID XXXXXXX in the request is not supported by the FlexNet Operations On-Premises Server

Question

How to resolve the following error being displayed on FlexNet Operations On-Premises 2016 server when trying to activate an entitlement?

Error: 7570:The publisher ID XXXXXXX in the request is not supported by the FlexNet Operations Server.

Example:

Try to activate an entitlement after changing Publisher xml in following 4 locations:
Replace publishers xml with demo content with the actual publisher.xml files with and restart FNO.
Get the error message listed above:

Locations of 'demo' publisher.xml were:
E:\FlexNet\release\flexnet-data\site\bin
E:\FlexNet\release\flexnet.ear\flexnet-data\site\bin
E:\FlexNet\release\operations\bin
E:\FlexNet\components\wildfly\standalone\deployments\flexnet.ear\flexnet-data\site\bin

Answer

Publisher needs to place the publisher.xml file in the correct platform folder under the custom folder. the correct folder for x64 Windows is 'custom\x64_n6\bin\'

The steps are:

1. Create the E:\FlexNet\custom\x64_n6\bin\ folder if necessary.
2. Copy the publisher.xml file to E:\FlexNet\custom\x64_n6\bin\ folder.
3. Log into the FlexNet Setup site
4. Click the FlexNet Setup 'System Status' tab
5. Click 'Stop Server'
6. Click 'Undeploy All'
7. Click 'Deploy All'
8. Click 'Start Server'

Additional Information

On page 35 of FlexNetOperations_ImplementationGuide.pdf:

Put the main publisher.xml file in the "custom/bin" directory. Put any additional publisher.xml files in the custom/bin/activationsettings directory. Run FlexNet Setup to copy your files from the custom directory to the directories site/bin and site/bin/activationsettings. Never directly copy your activation settings files to site/bin or site/bin/activationsettings. Always use the FlexNet Setup process to copy these files from the custom directory to the correct locations. If you edit any of your activation settings files, put the edited versions in the custom/bin or custom/bin/activationsettings directories and run FlexNet Setup again.

NOTE: By default there is no "custom\bin" folder (it doesn?t get created when you install FNO). The customer or consultant creates it during the course of configuring FNO. On the Windows platform, the "custom\bin" folder would be found at: C:\Program Files\FlexNet Operations\custom\bin\
Based on the information that is in Question tab (example above , it looks like this location would be E:\FlexNet\custom\bin\ in this particular case. If that folder does not currently exist, it should be created.

NOTE: Undeploy all and deploy all is similar to what we do in flexnet site make