Beacon Upgrade failed || Download failed: Invalid URI : The URI is empty

[ReshmaB]

Hi Forum,

Greetings!!

I was observed that after Flexera One Upgrade. We are have encountered with beacon issue Saying "Download Failed: Invalid URL".

In beacon properties - upgrade showing as failed & Beacon app I can see a warning message "The beacon control file(Policy ) is missing, or doesn't contain license information".

I have seen this behaviour is not just with our customer for other accounts also same.

Kindly let me know if there are any fix or work around for this issue.

Regards

Reshma B

[tblock1012]

Hello, yes we experienced this issue in our UAT environment after this upgrade:
Flexera One - IT Asset Management North America: UAT Release 2023 R1.2

Our Beacon was upgraded from 20.2 to 20.3 and is getting an error message as you described.

I have an open case for the issue.

[durgeshsingh]

Try to rerun task scheduler job for beacon upload task. 

[tblock1012]

The task has run a few times after the upgrade, getting the same message each time.

The error in the log seems to be related to getting key/certificate for policy:

System.Security.Cryptography.CryptographicException: The system cannot find the file specified.

[raviladhawala]

Hi @tblock1012 , Have you got any solution ?

[tblock1012]

Yes, the solution by ReshmaB worked for me. I unchecked the proxy setting on the Beacon parent connection and updated the registry as suggested.

[mfranz]

I had an issue with my UAT Beacon on Monday and I followed the workaround mentioned here: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Beacon-control-file-policy-missing-or-does-not-contain-license/ta-p/147761

[ReshmaB]

I tried re-running Task Scheduler.

Workaround mentioned in article - Sadly both didn't work for me.   

[tblock1012]

I also tried the workaround without success, still failing to download policy. I added notes to my case and will update this discussion with any comments from the engineer.

Thanks

[tblock1012]

For search purposes related to this issue, the problem for me is with the URI or Uniform Resource Identifier.

Beacon Policy Downloader failed to download policy with exception message: Invalid URI: The URI is empty.

[musmanjavaid]

After the recent upgrade applied by Flexera we are also getting the same issue in our EU instance of FlexeraOne. 

1. On the beacon Server the error msgs are "Download Failed: Invalid URI: The URI is empty", AND "The beacon control file(Policy ) is missing, or doesn't contain license information"
2. And on the web Ui we are getting "Failed to import downloaded rules and settings. Check the log file on the beacon server."

[ChrisG]

This error message may be shown after installing/upgrade the beacon to version 20.3 when using Internet Explorer proxy settings.

Try either of the following steps to remediate the issue:

Option 1: In the Beacon UI, go to the Beacon configuration tab. Click the Enter proxy details button, and ensure the the Proxy Server URL starts with "http://".

Option 2: Ensure the value of the following registry entry starts with "http://":  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\ProxySettings\ProxyServerUrl

[ReshmaB]

I have unchecked the Proxy settings from Beacon, It got resolved for one of the beacon, another one has same issue.

[bvikas]

Hi Chris,

but It's doesn't worked for me i have tried both the options as this is an issue from Flexera end 

Can you please help me with the RCA and fix this issue ASAP

[ChrisG]

The root cause of the issue that is remediated by the steps I described is that there is some logic in the beacon installer that can result in the beacon's web proxy URL registry configuration setting being set to a value that doesn't have the "http://" scheme specified at the start of the URL.

If fixing the web proxy URL configuration doesn't help in your situation then it sounds like you are being affected by something else. I can't think of anything else specific that is likely to cause the particular error being discussed in this thread sorry, but maybe other people in the Community here will have some other ideas.

[tblock1012]

Thanks, I unchecked the proxy setting on the Beacon parent connection and got a successful connection.

It appears the Beacon reverted back to 20.2 and the dropdown for current version in the UI also rolled back to 20.2

[justinwade4090]

I'm having the same issue on the child beacon and vendor took me to this KBA.

I was going to apply fix on Option 2

Option 2: Ensure the value of the following registry entry starts with "http://":  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\ProxySettings\ProxyServerUrl

But I don't see any ProxySettings\ProxyServerURL path in the child beacon registry.

But I do see that we have created a https_proxy key to configure a proxy server with http in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\ on our parent beacon. Do we need to configure this proxy with http on our child beacon as well?

[justinwade4090]

This issue has been resolved, we had to configure the FQDN for our host for the bindings in IIS and we were able to download the inventory and connect to parent beacon.

[ReshmaB · Accepted solution]

You can follow below steps to resolve issue. Once it's done you beacon will revert to n-1 version.

1. Disabling beacon proxy configuration.
2. Removing CertificateFile registry key found at HLKM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\
3. Restart the Beacon Engine