Inventory beacon get response from endpoint TLS check may report error

Inventory beacon get response from endpoint TLS check may report error

Symptoms:

This bug is causing Beacon UI extremely unstable and un-usable for BAS development.
The following error might be logged:

2020-11-04 07:38:01,126 [Common.BeaconConfig |discoexport] [DEBUG] TempNewContent Path: C:\ProgramData\Flexera Software\Beacon\mauflt1n.tmp
2020-11-04 07:38:01,126 [Common.BeaconConfig |discoexport] [DEBUG] TempOldContent Path: pbx2gw02.tmp
2020-11-04 07:38:24,264 [tionProtocolIdentifier|policy] [DEBUG] Error while identifying the protocol used for communication. Unable to connect to the remote server
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 3.125.248.62:443
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Flexera.SaaS.Transport.Core.CommunicationProtocolIdentifier.GetProtocol(Uri endPointUri, ICredentials credentials)
2020-11-04 07:38:24,264 [Services.PolicyService|policy] [INFO ] TLS version used:
2020-11-04 07:38:27,530 [Rules.PolicyClient |policy] [INFO ] Downloading rules using URI 'https://beacon.flexnetmanager.eu/inventory-beacons/api/policy/?tenantUid=T22GG9964L3HTX9L&BeaconUID={CE500637-6CA6-4FB1-8A47-8CBD80106D55}'.
2020-11-04 07:38:27,530 [Rules.PolicyClient |policy] [DEBUG] Setting IfNoneMatch header to '739'.

Diagnosis:

The existing method GetLauncherProxyFor is used to get value from the below registry and its also used by beacon to get policy files.

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Launcher\CurrentVersion]

Solution:

This bug has been fixed in 2020 R2.1 / Feb 2021 (Cloud), 2021 R1 (On Premises)

Labels (3)
Was this article helpful? Yes No
No ratings
Version history
Revision #:
2 of 2
Last update:
‎Jun 22, 2021 02:25 AM
Updated by:
 
Contributors