Book a Demo

Author Topic: Sparx EA v16 and the Floating license server  (Read 3237 times)

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1173
  • Karma: +30/-8
    • View Profile
Sparx EA v16 and the Floating license server
« on: October 27, 2022, 10:42:42 pm »
I am having trouble configuring PCS and Sparx EA v16 to use the new Floating License Server. When using the Floating License Client to link to an existing configuration, the v15/PCS v4.x, results on the following message:

"Could not connect to the Sparx Systems Floating License Server at https://[fully qualified server name]:443
Http Status Code: 403 Forbidden - White List".

or the same error minus the "White List" part after adding the server's IP address to the Admin White List of PCS.

Any help will be greatly appreciated.

timoc

  • EA User
  • **
  • Posts: 201
  • Karma: +14/-0
    • View Profile
Re: Sparx EA v16 and the Floating license server
« Reply #1 on: October 27, 2022, 11:14:55 pm »
This may be of use for reference purposes:
https://github.com/IDI-Systems/SSProCloud-Docker

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1173
  • Karma: +30/-8
    • View Profile
Re: Sparx EA v16 and the Floating license server
« Reply #2 on: October 28, 2022, 02:07:25 am »
After an installation repair and some serious head scratching, we found out the following:

1) The Pro Cloud Floating License Server Config Client when installed on the same machine as Pro Cloud Server does not accept the fully qualified server name as the server address. It only takes IP addresses or localhost.
2) As soon as, we installed the Pro Cloud Floating License Server Config Client in a different machine, we managed to configure the Floating License Server using the fully qualified server name as the server address without experiencing any errors.

I will report it as a bug to Sparx Systems.


Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1173
  • Karma: +30/-8
    • View Profile
Re: Sparx EA v16 and the Floating license server
« Reply #3 on: November 01, 2022, 11:37:55 pm »
I have reported this as a bug, and I hope they investigate it and address it.