Managing Floating Licenses in EA: Addressing Keystore Configuration Challenges

Introduction

Floating licenses are a cost-effective and flexible way to manage multiple users of Sparx Enterprise Architect (EA) across teams and departments. By using a centralized Keystore server, organizations can distribute a limited number of licenses dynamically. However, managing these licenses efficiently requires proper setup and maintenance of the Keystore system. Misconfigurations, access problems, and connection failures can all disrupt productivity and cause user frustration.

This article explores the most common challenges encountered when configuring and maintaining the Sparx EA Keystore for floating licenses, and offers practical solutions for resolving them.

1. Overview of the EA Keystore System

The Keystore is Sparx’s licensing system that allows floating licenses to be checked out by users. It typically runs on a shared server and is accessed by EA clients via a UNC path or HTTP endpoint. Key components include:

  • SSKeyStore.exe: The admin tool for managing the license file and user access
  • SSKeyStoreService.exe: The Windows service providing access to the Keystore
  • SSKeys.dat: The license file containing all the floating licenses

2. Common Configuration Issues

Connection Refused or Timeout Errors

  • Cause: Incorrect server path, network restrictions, or firewall blocks
  • Solution: Ensure the port (usually 7770) is open and accessible; validate the license path in EA’s licensing dialog

SSKeyStore Not Starting

  • Cause: Missing permissions, corrupted license file, or port conflict
  • Solution: Run the Keystore as administrator, check logs, and ensure SSKeys.dat is intact and licensed

User Can’t Check Out License

  • Cause: User not in allowed group, license already checked out, or file lock conflict
  • Solution: Verify user list in SSKeyStore, release old locks, and update access rules

3. Best Practices for Keystore Management

  • Install the Keystore on a reliable server with backups of the SSKeys.dat file
  • Use the HTTP or HTTPS-based Keystore service instead of network shares for better reliability
  • Configure IP-based or Active Directory group restrictions in SSKeyStore.exe
  • Enable license check-out time limits to prevent indefinite holds

4. Security Considerations

Protect your Keystore deployment by:

  • Running the service under a dedicated system account with limited privileges
  • Restricting access to configuration tools to authorized admins only
  • Encrypting license data and using HTTPS endpoints for remote access

5. Troubleshooting Workflow

  1. Check the EA client configuration (License Management tab)
  2. Ping the Keystore server to confirm network access
  3. Review the Keystore log files (usually found in the install directory)
  4. Restart the SSKeyStoreService if no new connections are being accepted
  5. Check for software updates or changes that might affect connectivity (e.g., firewall rules)

6. Licensing in Hybrid Environments

In environments where some users are remote or cloud-based, EA's Pro Cloud Server and floating license integration may require more complex firewall and HTTPS configuration. Be sure to:

  • Enable HTTPS in PCS for license delivery
  • Allow outbound connections from remote users to port 7770 or your custom configured port
  • Consider separate Keystore instances for internal and external users to isolate access

Conclusion

Floating licenses with EA offer scalability, but only if the Keystore system is properly configured and maintained. With the right setup and proactive monitoring, organizations can prevent access failures and make licensing administration seamless for IT and users alike.

Related Posts

Keywords

Enterprise Architect, Sparx EA, Floating License, Keystore Server, SSKeyStore, License Management, EA Licensing Issues, License Checkout Failure, Keystore Configuration, License Port 7770, EA Licensing Best Practices, License Service