IT - MES - 26051811 - Middleware License Acquisition Failures

• Document Version: 001
• Applies to Version(s): MES 2023 R2

Description  

This guide addresses common configuration-related issues that prevent the AVEVA MES Middleware from correctly acquiring license features. When these issues occur, the system may report exceptions during the license acquisition or release process, and nodes may fail to obtain a valid license status

Core Problem: Syntax and Naming Inconsistency

A primary cause of license failure is a mismatch between how the database server is identified in the AVEVA Configurator and how it is recognized by the License Server.

For counted MES features (such as Operations or Performance), the License Server identifies the consuming node using a specific format:

MESDB_server_name_MESDB_Name.

To ensure successful license acquisition, follow these critical configuration rules:

Exact Matching: Every MES node connecting to the license server must use the EXACT same server and database name syntax within the Configurator (specifically under the MES DB/MW Communication section on the Production tab).

Naming Conventions: The system is sensitive to naming formats; for example, using a Fully Qualified Domain Name (FQDN) in one area and a short name in another will cause a connection failure.

Consistency with Custom Ports: If your SQL Server name is configured using a custom port number, that exact syntax (including the port) must be applied consistently across all references in the Configurator.

Advanced Configurations

Managing Multiple Database Connections

If your environment requires one license server to support multiple combinations of MES database servers and database names, you must use License Reservations.

Reservations must be created for each unique dbserver_dbname combination.

This ensures that counted licenses are correctly split and allocated between the different databases.

For detailed setup instructions, refer to the MES License Reservation Product Help (https://docs.aveva.com/bundle/manufacturing-execution-system/page/539863.html)

MES Connector (Work Tasks) Synchronization

The MES Connector may also fail to acquire licenses if its internal references to the MES database are incorrect. If you encounter errors here, reconfigure all connector associations to match the validated database server name format used by the rest of the system.

Solution Steps:

Summary of Corrective Actions

Verify Syntax: Audit all machines to ensure the database server name format is identical across the entire landscape.

Reconfigure Middleware: Update the middleware settings on all affected nodes to match the validated syntax.

Service Restart: After correcting the naming syntax, restart the MES Service to allow the system to successfully re-attempt license acquisition.

 _____________________________________________________________________________________________________