A communication exception of this type currently exists. | Link | No | |
An Exception occurred as the timeout has been reached and the transaction has been rolled back. | Link | No | |
Communication exception from date must be after %1s start date - %2d. | Link | No | |
Communication exception from date must be before %1s end date - %2d. | Link | No | |
Communication exception from date must be entered. | Link | No | |
Communication exception method must be entered. | Link | No | |
Communication exception reason must be entered. | Link | No | |
Communication exception to date must be before %1s end date - %2d. | Link | No | |
From date must not be later than the to date. | Link | No | |
New communication exception details cannot be added for a client that is currently marked as a duplicate. | Link | No | |
No security implementation is supported for this transaction type. Please contact an Administrator. | Link | No | |
The Key Server cache and the Key Server database values are out of sync and therefore this record cannot be inserted. | Link | No | |