Issue
Users encounter the following error when launching Device Administrator:
“The following error(s) occurred while reading the server list file:
- The site-specific server password could not be loaded. It will be set to the default password ‘admin’.
- One or more SSH public keys are invalid.”
Additionally, devices may show:
- “SSH public key fingerprint changed!”
- “Wrong logon” errors for connected Servers
Product Line
EcoStruxure Building Operation
Environment
- EcoStruxure Building Operation Device Administrator
- Access Method: Remote Desktop
- Multiple Windows user accounts or sessions
Warning
Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.
Cause
This issue is caused by shared use of a single server list file across multiple Windows user accounts or sessions. When another user opens Device Administrator—even without modifying or saving the server list—the SSH keys become invalid due to security hardening measures.
This behavior is by design to prevent unauthorized access and is part of Schneider Electric’s cybersecurity strategy.
Resolution
Recommended Workflow
- Create and Save the server list on the original user account or PC.
- Export the server list using the built-in export feature in Device Administrator.
- Import the server list on the target user account or PC.
⚠️ Do not copy the XML file manually between users or systems.
This will invalidate SSH keys and passwords due to security restrictions.
Best Practices
- Use unique filenames when exporting server lists (e.g., include user initials).
- Avoid using shared server list files across users or sessions.
- If the server list becomes corrupted or invalid:
- Re-import the previously exported working server list.
- If unavailable, recreate the list and export it immediately for future use.
Additional Notes
- This issue can occur even if only one user accesses the system, especially if the server is accessed via Remote Desktop and multiple sessions are involved.
- The server list file (
Servers.xml) should always be managed through the export/import functionality to preserve encryption and key integrity. - Affected devices may require re-authentication or re-adding if the server list is corrupted and cannot be recovered.
