We started getting a HTTP401 error from one of the Beacons to the App Server. We have other beacons that are not doing this and this particular beacon was working fine for months before this started happening. Any ideas?
Thank you
‎Dec 16, 2019 11:40 AM
Hi,
A http 401 error is essentially an unauthorized error suggesting the account the beacon is presenting itself is disallowed by the FNMS server. Is it possible that the credentials configured for your beacon to use for uploads/downloads has become invalid (password expired for example)?
If you are using FNMS cloud too it might be that someone has inadvertently clicked on the button to download a configuration for the beacon without then importing it into the beacon ui. Every time you press that button it generates new settings making the old configuration invalid.
regards,
Murray
‎Dec 16, 2019 03:50 PM
‎Dec 17, 2019 02:28 PM
Has the child beacon been configured to use Basic Authentication? In the beacon UI, under the Parent Connection settings, can you see any difference on that beacon compared with the working beacons?
For On-Premises, those are where I'd start.
‎Dec 18, 2019 12:31 PM
I compared the Beacon that is getting the error against others that are not getting the error but all appears the same between them.
‎Dec 18, 2019 04:43 PM
Hi @rclark0 ,
Please verify the Beacon engine logs and the inventory beacon logs and you might get some idea. Please verify the IIS logs as well and check if there were any issues with the IIS settings as well.
Regards,
‎Dec 19, 2019 03:01 AM