IT - LM09112601 -License Server - Query for Licensing Details

• Document Version: 001
• Applies to Version(s): 4.x

Description  

This document explains the utility of raw API output retrieved from an AVEVA License Server.

Solution Steps:

In a web browser you can use “Localhost” on the License Server or you can use the name of the server.

http://localhost:55559/api/1.0/features?size=100&page=0

http://nameofserver:55559/api/1.0/features?size=100&page=0

There may be multiple pages depending on the number of licenses and features. 

Replace the 0 at the end with a 1 and keep adding numbers until you reach the end of the license information.

This data provides a comprehensive snapshot of the license environment, essential for
identifying and resolving licensing bottlenecks in production systems.

Key Information Contained in the Diagnostic Dump:

1. Feature Identity: featureName, featureVersion, and featureId allow for precise mapping of
licensed capabilities to specific software modules.
 

2. Usage Metrics: featureCount (total capacity), used (current consumption), and reserved
(currently locked licenses) enable real-time analysis of license utilization.
 

3. License Integrity: expiry, issuer, and vendorString (containing PN, AID, and Serial Number)
provide validation of the license validity period and entitlement details.
 

4. Configuration Flags: Metadata such as concurrent, metered, and uncappedOverdraft
clarifies how the license server handles connection requests.
 

Troubleshooting Applications

1. Identifying License Exhaustion
By comparing used against featureCount, administrators can determine if a "Feature Not Available"
error is due to reaching the maximum concurrency limit or an actual server-side configuration error.

2. Validating Expiry and Entitlement
Review the expiry and vendorString for critical features. This helps confirm whether a production
outage is caused by an expired demonstration/consignation license (e.g., 2026-06-30) vs. a permanent
license.

3. Version Mismatch Diagnostics
Verify that the featureVersion matches the installed AVEVA software version. Discrepancies here
often manifest as silent failures where the license server rejects requests due to incompatibility.

_____________________________________________________________________________________________________