The persistence provider was unable to reclaim the lock within the timeout provided. This may indicate a deadlock in the pattern of commands simultaneously being executed on different InstanceHandles owned by the same InstanceOwner. This can be alleviated by using multiple InstanceOwners or by ensuring that InstancePersistenceCommand.AutomaticallyAcquiringLock returns false for commands which do not potentially acquire a lock the instance.
The persistence provider implementation of InstanceStore in use is invalid. Its implementation of OnFreeInstanceHandle threw ...
The persistence provider implementation of InstanceStore in use is invalid. The {0} method can only be called during the ...
The persistence provider implementation of InstanceStore is invalid. It attempted to execute multiple nested commands concurrently. ...
The persistence provider implementation of InstanceStore successfully canceled the command. An orphaned lock was reclaimed ...
The persistence provider was unable to reclaim the lock within the timeout provided. This may indicate a deadlock in the ...
The persistence value named {0} is being provided as an initial metadata value, so it must have a valid InstanceValue other ...
The personal card that is used for authentication of the managed card cannot be found. If you have a backup file containing ...
The physical path of the application to be compiled. If -p is missing, the IIS metabase is used to locate the app. This switch ...
The picture file format for this file is an unknown or invalid file type. Select a different picture file. Supported picture ...