TN - LM - 26051509 Resolving Corrupt Aveva Licensing Files
Last updated: May 15th, 2026Description
- Author: Ernest Lee
- Published: May 15th, 2026
Details:
- Document Version: 001
- Applies to Version(s): 4.1 and 4.2.1

Description
This document outlines the procedure for resolving issues with AVEVA Enterprise Licensing when data files have become damaged or corrupted
Pre-Maintenance Precautions
Last Resort: This cleanup should only be performed after all other troubleshooting methods have failed
Redundancy: If your environment uses Redundant License Servers, you must follow these steps on both machines
Preparation: Before starting, document every entitlement currently in your License Manager and ensure you have the corresponding XML files ready for re-activation
Solution Details
Solution Steps:
Step 1: Software Preparation
Visit the Global Customer Support (GCS) site at softwaresupportsp.aveva.com
Download the most recent version of AVEVA Enterprise Licensing (such as version 4.2.1)
Unblock the downloaded file and complete the installation
Step 2: Database Management
Navigate to: C:\ProgramData\AVEVA\Licensing License Manager\Data\
Create a backup copy of the License ManagerData.db file, then delete the original from this folder
Obtain a fresh, blank version of the database file from the framework directory
For v.4.1.0 or older: C:\Program Files (x86)\Common Files\ArchestrA\Licensing Framework\License Manager\License ManagerDb.db
For v.4.2.1 or newer: C:\Program Files\Common Files\ArchestrA\Licensing Framework\License Manager\License ManagerDb.db
Step 3: Service Reset Sequence
You must stop and then restart the four primary licensing services. The naming conventions vary depending on your software version
A. Stop Services (In Order)
Order |
v.4.1.0 and Older |
v.4.2.1 and Newer |
|---|---|---|
1 |
License Manager Web Service
|
AEL Manager Service (LMWebService)
|
2 |
License Server Agent
|
AEL Agent Service
|
3 |
License Server Core
|
AEL Core Service
|
4 |
License Server Sam Service
|
AEL Product Service
|
B. Replace Database
Place the blank copy of the database you obtained in Step 2 into the active data folder: C:\ProgramData\Aveva\Licensing License Manager\Data\License ManagerData.db
C. Start Services (In Reverse Order)
Order |
v.4.1.0 and Older |
v.4.2.1 and Newer |
|---|---|---|
1 |
License Server Sam Service
|
AEL Product Service
|
2 |
License Server Core
|
AEL Core Service
|
3 |
License Server Agent
|
AEL Agent Service
|
4 |
License Manager Web Service
|
AEL Manager Service (LMWebService)
|
Step 4: Restoration
If you are using a redundant setup, re-pair your servers now
Import the entitlement XML files you gathered during preparation back into the License Manager
Re-activate all required licenses
________________________________________________________________________________________________________


Recommended articles
[ISS Support Case] InTouch License Acquisition Failure
Client reached out as when user was attempting to start InTouch they were receiving a license acquisition failure message.
Read More[ISS Support Case] InTouch License Acquisition Failure
Client reached out due to receiving failure to acquire license when attempting to start WindowViewer.
Read More[ISS Support Case] InTouch License Acquisition Failure
Client called in because when trying to open Windowmaker received error message: "Exceeded maximum number of windows allowed (32)" After clicking okay user would be presented with failure to launch message.
Read More