Flexnet beacon connection fails.

[AditiA]

Hi All,

We upgrade the FNMS  2023 R2, FlexNet Beacon connection with Application Server failed with the following message

FNMP connection failed: Test connection failed (Response status code does not indicate success: 503 (Service Unavailable).)

 -Test connection failed (Response status code does not indicate success: 503 (Service Unavailable).)

-Response status code does not indicate success: 503 (Service Unavailable).

[mfeinman]

I'd start by making sure that FNMS itself was up and running.  Check that the batch processor services are running, and then check the FNMS logs for possible issues with the server.

If you open a browser to samdna-test.kpn.org/Suite, do you see the Flexera Management Dashboard?

--Mark

[AditiA]

Hii @mfeinman,

After opening a browser to samdna-test.kpn.org/Suite, yes  Flexera Management Dashboard is showing.

After test connection all status showing failed.

What will be the solution for this error?

H

[mfeinman]

You'll have to examine the beacon logs for an error message that provides clues to this issue.  We can't really help just seeing the generic UI message that something happened.

I also should have been more specific when I suggested a browser test.  If you open a browser on the beacon itself to samdna-test.kpn.org/Suite, do you see the Flexera Management Dashboard? That would determine if the issue is a connection failure.

--Mark

--Mark

[Resh_wabtec]

It's worth checking inventory beacon test connection settings under IIS manager

[adrian_ritz1]

Hello @AditiA ,

Usually 503 error indicate internal server error, on the uploading server. So you need to investigate the connections

did you install the .net and configured the iis on uploading server (samdna-test.kpn.org) according to WI

Check again the roles:

• Web Server > Application Development > .NET Extensibility
• Web Server > Application Development > ASP.NET
• Web Server > Application Development > CGI
• Web Server > Application Development > ISAPI Extensions
• Web Server > Application Development > ISAPI Filters
• Web Server > Common HTTP Features > Default Document
• Web Server > Common HTTP Features > Directory Browsing
• Web Server > Common HTTP Features > HTTP Errors
• Web Server > Common HTTP Features > HTTP Redirection
• Web Server > Common HTTP Features > Static Content
• Web Server > Health and Diagnostics > HTTP Logging
• Web Server > Performance > Dynamic Content Compression
• Web Server > Performance > Static Content Compression
• Web Server > Security > Basic Authentication
• Web Server > Security > Request Filtering
• Web Server > Security > Windows Authentication

and configure the .net

dism /online /enable-feature /featurename:IIS-ApplicationDevelopment
dism /online /enable-feature /featurename:IIS-ISAPIFilter
dism /online /enable-feature /featurename:IIS-ISAPIExtensions
dism /online /enable-feature /featurename:IIS-NetFxExtensibility45
dism /online /enable-feature /featurename:IIS-ASPNET45

[mschwach]

Hi, Please check your TLS settings on your Beacon

https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Transport-Layer-Security-TLS-configuration/ta-p/2250

[AditiA]

Hii all,

This issue has been solved. Thanks for your fabulous opinion. 

[mschwach]

what was the solution?

[adrian_ritz1]

Hello @AditiA ,

May be you can tell us what was the issue 🙂

[Big_Kev]

I had the same issue lately after moving system to a new OS & SQL DB. From the troubleshooting that log from C:\ProgramData\Flexera Software\Compliance\Logging\InventoryBeacons  folder, the log indicates the service account used by Application Pool - Flexera Beacon has issue login to new SQL Server. Solved once the AD group where the service account located being added into SQL Login. 

Not sure the same issue though . But what had learnt is when seeing Beacon 503 , the log from above folder will be a good start of investigation.

Cheers

Kev