Known Issues - Add-in License Support/Issue
Q1: Unable to connect to the Floating License Server and EASaaS shows no available keys when trying to login
Description
After entering the Shared Keystore credentials and clicking OK button, the following error message is displayed.
The keys are fetched from a client machine but it’s not working in the server machine where the PCS and FLS are hosted.
Possible Reason
- On checking the floating license group, the default configuration settings were used which are actually for example purposes. The Group Configuration must be configured properly to match the requirements.
- The “Admin” user is for the purpose of allowing connections from the Floating License Configuration Client and cannot be used by Enterprise Architect to obtain a license. It’s possible that this error might occur when the admin account is used for login in multiple machines (or) incorrect information in the Group Configuration.
When all keys have been retrieved and there are no keys left for the next user, it results in a 'no available key' issue. If keys are theoretically available, yet the problem persists, restarting the service may resolve the issue.
Work Around
- The default configuration was updated by removing the sample user groups and adding new users.
- When logging in with the new users, the Enterprise Architect was able to fetch the licenses from the Floating License Server.
- Need to increase the lease expiry date for the key if the issue occurring repeatedly when he have available keys.
Reference
- Documentation on FLS user group management.
- Ticket ID: #2188
Subject: Key Authorization issue
Department: Prolaborate Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/prolaborate-support/tickets/details/75941300000847206 - Ticket ID: #6517
Subject: Huntington - EA Users Prompted for Key at Start Up
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000024467230
Related Articles
Known Issue - Floating License Server
Q1: Failure to Launch EA Due to FLS Keys Limit Exceeded FLS connection indicates "Provided Credentials have exceeded the key limits for this key type" Description The customer has informed us that upon launching EA, an error message appears stating, ...
Known Issues - Migration
Q1: "Invalid License" or "License Missing" error after migrating Prolaborate to a new server Description The Prolaborate and Pro Cloud Server is migrated to a new Server setup. After logging into Prolaborate, an error message appears saying "Invalid ...
Known Issues - EA Connection error.
Error in Could not connect to the Sparx Systems Floating License Description: The Customer encounters an error as follows when accessing the servers from our client computers. Workaround: To conduct a browser test to ensure everything is functioning ...
Known Issue-Model Connection
Encountering an "XML incomplete error" when attempting to connect to the model in EA. Description: When attempting to connect to the model in EA, users encounter an error message stating "XML incomplete error." Any attempts to modify the repository ...
Know Issue - Connectivity Issues
Q1:Issue with Model cloud connection in EA. Description: The customer faced an error while connecting the model via connection. Model connection failure (Pro Cloud Server: The HTTP connection reported the following error: 12002) 1. The customer is ...