The device information or name for device %1 at %2 with device identifier %3 could not be processed because it affects one or more existing devices. Resolve the conflict manually by verifying the information for the devices corresponding to this name, device information, and device identifier.
The destination queue depth of all messagebox databases exceeds the threshold. If the host publishes to multiple queues, ...
The destination queue depth of all messagebox databases. If the host publishes to multiple hosts, the weighted average across ...
The device %1 might be in a bad state because an operation failed on the device while attempting to recover from a device ...
The device group information in the given .xml file is not valid. The root of the group hierarchy should be RootDeviceGroup. ...
The device information or name for device %1 at %2 with device identifier %3 could not be processed because it affects one ...
The device or process {0} is in a corrupted state in the RFID store. If this situation persists, delete and re-add the affected ...
The device {0} could not be deleted from the RFID store because of a database exception. For more information, look at the ...
The directory for the log file does not exist. Verify that the directory specified for the logfile in the rfid.config file ...
The disassembler cannot retrieve the document specification using this type: "%1". This is because the schema is not deployed ...