Diagnosis
The locks for the transaction data are managed in the shared objectsmemory with area name CL_RSPLS_ENQ_AREA. So that user &V2& canrequest a lock, area instance '&V1&' has to be accessed (this is alsothe name of the basis InfoProvider).However, the area instance isinconsistent. The locks in this instance are managed, but have beenchanged by a patch data structure in class CL_RSPLS_ENQ_AREA.
If no active locks exist, the system builds the area instance againautomatically. However, locks do still exist (users have active locks onthe transaction data for InfoProvider '&V1&'), or the automatic rebuildof the area instance failed.

System Response
The lock server cannot be accessed.

Procedure
Inform the system administrator. The system administrator can usetransaction SM12 to see which active users have set locks and ifnecessary, can delete the area instance manually using transactionSHMA. The area instance is then rebuilt automatically when thenext lock is requested on the lock server.

Procedure for System Administration
You can see if active locks are still in place for the transaction datausing transaction SM12. Use table name RSPLS_S_LOCK_SYNC. Leavethe lock arguement and user name fields empty.