Hi,

Please check below point

1:- Check if URL is getting resolve in DNS

2:- Telnet port 443 status from agent to beacon

3:- TLS setting at server level where agent has been deployed

According to the 'tracker.log'-file that you provided.:

• The agent first tries to upload the inventory data (NDI file) to a Beacon 'PSRVWINF3718.tdk.dk'. This fails with a HTTP 500 error on the server, which indicates something with the (IIS-) configuration on this Beacon is not correct.
• After the attempt to upload to the first Beacon failed, the agent uploads the inventory data to the 'JH-FLEXERA-01.jumphost.netdesign.dk' Beacon successfully.

You should check on the second Beacon 'JH-FLEXERA-01.jumphost.netdesign.dk' if the NDI data have been forwarded to the next level (next Beacon or to the FNMS Inventory server.

And you should check the configuration on the first Beacon. Often re-initializing IIS from the Beacon console will help.

Remember that after data have been uploaded to the FNMS Inventory server, data will be visible in the FNMS User Interface ('Flexera console') only after the next full compliance import has been completed. By default, the Windows 'Task Scheduler' will trigger the compliance import at 02:00 AM in the morning, so you may have to wait until the next day.

Hello @Rahul08  , for HTTP 500 internal server errors, please make sure you have IIS configured and have all the right roles installed on your Beacon server.

Please refer to the link below and look for Roles to see a list of IIS roles needed: