How to Fix “Invalid Metadata” Errors in Geo SCADA
When upgrading a Geo SCADA system or restoring a database backup to a different server, you may encounter an “Invalid Metadata” error. This issue often forces the database into Configuration Error Mode, preventing normal system operation and requiring investigation before the system can be brought back online.
This article explains the causes of the error and provides a clear step-by-step approach to identifying and resolving it.
What Causes the Invalid Metadata Error?
The most common cause of this error is a conflict between metadata field names within the database.
In Geo SCADA, metadata fields must have unique names across the system. Conflicts occur when Custom metadata fields overlap with system or driver defined metadata.
Typical Scenario
For example:
- You install a driver that includes a metadata field named AssetID
- Your database already contains a custom metadata field also named AssetID
Since metadata names must be unique, Geo SCADA detects the duplication during startup and raises the Invalid Metadata error.
How to Identify the Conflicting Metadata
To resolve the issue, you first need to identify which metadata fields are duplicated.
Step 1: Check DBStartup Logs
Geo SCADA logs detailed startup information in the DBStartup log files, which are the primary source for diagnosing this issue.
Default Log Location
By default, logs are located in:
C:\ProgramData\Schneider Electric\ClearSCADA\Logs\DB (Look specifically for file called DBStartup.log.)
Step 2: Search for Metadata Errors
Here is an example that demonstrates an issue with the Trio Radio driver, where conflicting metadata definitions lead to duplicate field errors during runtime.
Open the log file and search for keywords such as: "Duplicate field name"
You will typically find entries similar to:
02-JUN-2026 21:53:30.225 1384 [ERR] Duplicate field name 'RadioType' in classes 'CDBObject' and 'CTrioDiagAdvRadio'
These entries clearly indicate a duplicate field name 'RadioType' between the Trio Radio driver and custom field metadata. To resolve this, uninstall the Trio Radio module (if it is not needed and was accidentally added during the upgrade or database migration).