Geo SCADA "Invalid Metadata" Error After Downgrading from Geo SCADA 2025 to Geo SCADA 2023
During a downgrade from Geo SCADA 2025 to Geo SCADA 2023, the server failed to start and entered a Configuration Problem state with an Invalid Metadata error:
Geo SCADA stores database metadata in: C:\ProgramData\Schneider Electric\ClearSCADA\Database\ClearSCADAMetadata.xml
During startup, the server validates the metadata version stored in this file.
The file contained:
<Metadata version="6" ClearSCADA_Version="6.87.$$$$.1"/>
Metadata version 6 corresponds to the newer metadata schema used by Geo SCADA 2025.
When Geo SCADA 2025 is downgraded to Geo SCADA 2023, the Geo SCADA 2023 server attempts to open the existing database. However, the database metadata has already been upgraded to version 6. Since Geo SCADA 2023 only supports metadata version 5, it cannot interpret the newer metadata format. As a result, the server rejects the database metadata and enters the Invalid Metadata state.
Database upgrades are generally designed to be forward-compatible, not backward-compatible. When a database is opened by a newer version of Geo SCADA, the internal metadata may be updated to support new features and schema changes.
As a workaround, it is possible to modify the ClearSCADAMetadata.xml file and change the metadata version to 5.
- Stop the Geo SCADA server.
- Open: C:\ProgramData\Schneider Electric\ClearSCADA\Database\ClearSCADAMetadata.xml
- Modify the metadata entry:
Before
<Metadata version="6" ClearSCADA_Version="6.87.$$$$.1"/>
After
<Metadata version="5" ClearSCADA_Version="6.86.$$$$.1"/>
(Note: replace $$$$ with the actual build number - as found in the Server status | General | Information dialog)
- Save the file.
- Start the Geo SCADA server.
The server should then successfully pass metadata validation and complete startup.
Important note: This workaround should only be considered when downgrading between Geo SCADA versions and after appropriate backups have been taken. The preferred downgrade method is to restore a backup created prior to the upgrade whenever possible.