Known Issue: Agent policy download from beacon fails with HTTP 400 BAD REQUEST response unless machinename and ipaddress are both specified in the policy URL (IOK-995408)
Known Issue: Agent policy download from beacon fails with HTTP 400 BAD REQUEST response unless machinename and ipaddress are both specified in the policy URL (IOK-995408)
Summary
An attempt to download an agent policy .npl file from a beacon fails with an HTTP 400 BAD REQUEST response unless a value is specified for both machinename and ipaddress query parameters in the URL used for the .npl file.
Details
Logging in the agent’s installation.log file appears as follows when this issue occurs:
Logging is also generated in the beacon’s BeaconIIS.log (when using IIS) or BeaconEngine.log (when using a self-hosted web server) showing messages like the following:
2022-11-02 15:19:49,013 [ers.PoliciesController|Selfhost-118] [INFO ] Handling policy file request for machinename='', ipaddress='', full URL=http://beacon/ManageSoftDL/Policies/Merged/acme.com_domain/Machine/ltp101.npl
2022-11-02 15:19:49,013 [ers.PoliciesController|Selfhost-118] [ERROR] An exception has occurred while handling policy file request: 'Object reference not set to an instance of an object.'
at Flexera.Beacon.HostIndependentWebService.Controllers.PoliciesController.Get(String filename, String machinename, String ipaddress)
This issue affects beacon versions 18.3 (2022 R1.3) through 18.6 (2022 R1.6).
Workaround
If you are specifying a URL for downloading a policy .npl file for some operation, be sure to explicitly include values for the machinename and ipaddress query parameters in the policy URL.
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
