It means that the openHistorian has encountered two separate devices with the acronym
WAMS!PRRP#225 when attempting to synchronize its metadata with the remote system. I would say that the most likely cause is that the
PRRP#225 on the
WAMS system was modified after the device’s metadata had been synchronized with the openHistorian. This could happen if you deleted the
PRRP#225 device on the server and then recreated it while the openHistorian was offline or otherwise unable to receive configuration change notifications. Note that this would also change all the
SignalIDs of the measurements.
The easiest solution in this case would be to delete the
WAMS device and recreate it, though you said you don’t want to do that. You can also just delete the
WAMS!PRRP#225 device, and any other offending devices. The extent to which this issue occurred is currently unknown and you’d have to work through it device by device. After each deletion, let the system resynchronize to get the configuration back. Unfortunately, you would lose the past data for any of the deleted devices.
The best solution to prevent data loss would be to manually synchronize the
UniqueID field for your devices AND the
SignalID field for your measurements between the two systems.
UniqueID can be synchronized by
Acronym. I’m thinking that the best way to synchronize
SignalID is probably by