How can we help you today?

CM (Configuration Manager) Tool 2.0.0 - ION_Data archive is failing when historical data is selected

Issue:

When using Configuration Manager Tool 2.0.x, the Save to Archive process fails if Historical Data is included, resulting in a “Save to Archive was cancelled” message.

Image

Product Line:

Power Monitoring Expert 9.0

Power Monitoring Expert 2020

Power Monitoring Expert 2021

Power Monitoring Expert 2022

Power Monitoring Expert 2023

Power Monitoring Expert 2024

Environment:

Configuration Manager (CM) Tool 2.0.x

Cause:

This issue may occur due to one or more of the following conditions:

  • The SQL Server service account does not have sufficient write permissions on the selected archive output directory.
  • There is insufficient free disk space on the output drive to store the archive, including the ION_Data historical database.

When Historical Data is selected, the CM tool attempts to generate a database backup. If permissions or disk space are insufficient, the operation is canceled and no archive is created.

Resolution:

Warning
Take backups of any files before making changes. Ensure backups are stored in a safe location (for example, the Desktop).

Verify permissions and disk space

  1. Verify that the SQL Server service account has write access to the Configuration Manager archive output directory.
  2. Run the Configuration Manager Tool as Administrator.
  3. Confirm that the destination drive has sufficient free disk space to store the archive, including the ION_Data historical data.

If the issue persists after completing the checks above, the archive can be created manually using the workaround below.

Manual archive creation workaround

  1. Create the archive without selecting Historical Data.
  2. Unzip the generated archive to a known location.
  3. Open ComponentCollection.json (located in the root directory of the unzipped archive) using a text editor.
  4. Add the following JSON fragment:

{
"OperationType": 23,
"Processed": 1,
"Count": 1,
"Type": "Historical Data",
"ComponentItems": [
{
"Processed": true,
"Name": "ION_Data",
"DisplayName": "ION_Data",
"Attributes": [
{ "Name": "DatabaseName", "Value": "ION_Data" },
{ "Name": "Size", "Value": "316669952" },
{ "Name": "BackupSize", "Value": "227540992" },
{ "Name": "StartDate", "Value": "2015-11-19T16:00:00.0000000" },
{ "Name": "EndDate", "Value": "2016-06-22T03:45:00.0000000" }
]
}
]
}

5. Copy the ION_Data.bak database backup file into the following directory within the unzipped archive:

    • ...\Database_Backups

6. Re‑zip the archive, ensuring it includes:

    • The updated ComponentCollection.json
    • The ION_Data.bak file

7. Launch the Configuration Manager Tool and perform Load from Archive to confirm that the ION_Data metadata (start date, end date, etc.) is visible.

The metadata values do not need to exactly match the data range contained in the backup file.

Recommendation:

If you are using an older version of PME, consider upgrading to the latest version for improved protocol support and security. For assistance with integration or upgrades, contact Schneider Electric Technical Support at: pmo-psup@se.com

Support information

Schneider Electric United Arab Emirates

Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.
  • Products Documentation
  • Software Downloads
  • Product Selector
  • Product Substitution and Replacement
  • Help and Contact Centre
  • Find our Offices
  • Get a Quote
  • Where to buy
  • Schneider Electric Community
  • Careers
  • Company Profile
  • Report a misconduct
  • Accessibility
  • Newsroom
  • Investors
  • EcoStruxure
  • Job Search
  • Blog
  • Privacy Policy
  • Cookie Notice
  • Change your cookie settings