Hello Community,
we have installed agents on windows server 2019 .
communication from devices to beacon server is open (telnet sucessfull, ping - good)
yet we are getting error while agent trying to connect with beacon.
so far we have installed agents in 15 devices , not even one reporting
‎Jan 31, 2022 07:19 AM
‎Jan 31, 2022 07:34 AM
In addition to the recommendations from mfranz, did you correctly configure the MGSSETUP.INI file with your Beacon URL and include this in your install package?
‎Jan 31, 2022 08:21 AM
yes we configured correctly DNS ,TNC working good
‎Jan 31, 2022 08:24 AM
Please use FQDN of your beacon in mgssetup.ini file for Deploy URL. Please ensure 443 port must be open from agent to beacon.
‎Jan 31, 2022 08:40 AM
Good afternoon all,
I don't believe the Beacon was correctly configured in your mgssetup.ini file.
Note the following from our Installation.log:
[1/21/2022 1:41:23 PM (N, 0)] {14072} Downloading “http://Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-sap-jmp05.npl?machinename=nf-ne-sap-jmp05&ipaddress=172.18.2.13” to “C:\Windows\TEMP\NDL23359.npl”[1/21/2022 1:41:26 PM (G, 0)] {14072} Download failure: Error 0xE0500005: Host name lookup failed
[1/21/2022 1:41:26 PM (N, 0)] {14072} Download FAILED for “http://Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-sap-jmp05.npl?machinename=nf-ne-sap-jmp05&ipaddress=172.18.2.13”
[1/21/2022 1:41:26 PM (N, 0)] {14072} Downloading “http://Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-sap-jmp05.npl?machinename=nf-ne-sap-jmp05&ipaddress=172.18.2.13” to “C:\Windows\TEMP\NDL23359.npl”
[1/21/2022 1:41:26 PM (G, 0)] {14072} Download failure: Error 0xE0500005: Host name lookup failed
[1/21/2022 1:41:26 PM (U, 0)] {14072} ERROR: Error (s107m858)
[1/21/2022 1:41:26 PM (U, 0)] {14072} ----------------
[1/21/2022 1:41:26 PM (U, 0)] {14072} The following network error occurred while retrieving the application:Error 0xE0500005: Host name lookup failed
In our installation.log, we'd normally expect to see the Beacon name, then the download subsite.
So, more like:
http://BeaconName/ManageSoftDL/Policies/Merged...
(as an example)
If this hasn't been entered into your mgssetup.ini, you could manually set this in the Registry, here:
You'd normally expect to see a section in DownloadSettings per Beacon your agent could report to.
If you add a sub-key called 'Bootstrap Server 1', then enter your Beacon's details following my linked format, you should see your devices reporting in.
I'd go back to your mgssetup.ini in the meantime and confirm this is being placed in the correct location, as the agent doesn't appear to be picking it up.
I hope that helps! Let us know if not.
Best,
Jack
Flexera Support
‎Jan 31, 2022 10:58 AM
after configuring mgssetup file and making changes in the regedit , got another error stating:Could not establish HTTPS session
[2/1/2022 7:45:17 AM (G, 1)] {61692} Base URL “https://NF-NE-FLEXP-APP.beig.birdseyeiglo.com/ManageSoftDL/” will be used
[2/1/2022 7:45:17 AM (N, 0)] {61692} Downloading “https://NF-NE-FLEXP-APP.beig.birdseyeiglo.com/ManageSoftDL/Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-tstjmb01.npl?machinename=nf-ne-tstjmb01&ipaddress=172.18.2.4” to “C:\Windows\TEMP\NDL9770.npl”
[2/1/2022 7:45:17 AM (G, 0)] {61692} Download failure: Error 0xE0500021: Could not establish HTTPS session
[2/1/2022 7:45:17 AM (N, 0)] {61692} Download FAILED for “https://NF-NE-FLEXP-APP.beig.birdseyeiglo.com/ManageSoftDL/Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-tstjmb01.npl?machinename=nf-ne-tstjmb01&ipaddress=172.18.2.4”
[2/1/2022 7:45:17 AM (N, 0)] {61692} Downloading “https://NF-NE-FLEXP-APP.beig.birdseyeiglo.com/ManageSoftDL/Policies/Merged/beig.birdseyeiglo.com_domain/Machine/nf-ne-tstjmb01.npl?machinename=nf-ne-tstjmb01&ipaddress=172.18.2.4” to “C:\Windows\TEMP\NDL9770.npl”
[2/1/2022 7:45:17 AM (G, 0)] {61692} Download failure: Error 0xE0500021: Could not establish HTTPS session
[2/1/2022 7:45:17 AM (U, 0)] {61692} ERROR: Error (s107m858)
[2/1/2022 7:45:17 AM (U, 0)] {61692} ----------------
[2/1/2022 7:45:17 AM (U, 0)] {61692} The following network error occurred while retrieving the application:
Error 0xE0500021: Could not establish HTTPS session
‎Feb 01, 2022 04:44 AM
Good afternoon, I hope you're well?
Excellent -- I can see we've got the correct Beacon name populated in our logs, which is a good start.
From our impacted device, what happens if you head to:
https://nf-ne-flexp-app.beig.birdseyeiglo.com/ManageSoftDL/Test
in the browser?
Do we also see HTTPS errors (i.e. the 'lock' icon in Chrome reporting an insecure connection) ?
Usually, this error suggests an issue with the HTTPS configuration - our Agent not having the correct root or self-signed certificate in place as our Beacon uses - or an issue with TLS configuration.
The following Knowledge-Base articles outline the steps to take to ensure our HTTPS and TLS configuration looks good:
(I'd refer to the Agents section of the above)
‎Feb 01, 2022 06:10 AM