How to deal with self-blocking in 1C?

Question

System administration

1C-Enterprise is running on a remote terminal server Windows Server 2016 with MS SQL Server 2016
Less than half of the RAM is occupied, the processor is also not loaded, while different users from time to time have different documents blocked by them.
Some users have RemoteApp, some have a thin client on their computer, some via RDP.
The following happens, the user creates an order, closes it and signs, after some time (several minutes or more) opens to edit and sees the message "Object lock error. Object is already locked thin client"
Computer, user and session of the same user, other sessions i I don't see it in the console.
How to be? Where to look? What to read?

Answer 1

Most likely, the error is in the program code here:
On the "Order" object, in the process of executing this very "signature", the "Lock ()" method was called, but at the end of the operation, they forgot to call the "Unlock ()" method.
PS In any case, the claim should be addressed to the configuration developer. And even more precisely - to the one who made the "sign" function.

Answer 2

Try to completely abandon RemoteApp. There are always a lot of problems with him. The user may not even understand through what he opened 1C and tell you that one thing, although in reality everything is different, RemoteApp aggravates everything. For example, a user can open the same document through RemoteApp and a thick client and think that he actually works in the same window, but in fact he opened it through RemoteApp in the morning, and closed and opened the thick client in the afternoon and tries to enter the same order, which opened in the morning.
And the magic is that when you close RemoteApp, the 1C client does not close, and all open documents will also be open. And until you reboot the server to reset all sessions, and walk up to the user to see what he's doing, you won't understand what's wrong.
In general, my advice is to give up RemoteApp, restart the server and see what happens next on the ground.

Answer 3

How to be? Where to look? What to read?

I think it's worth looking away - he indulges in such RemoteApp.

Answer 4

Try reinstalling the update.
Precisely in the sessions do not hang hung? If configured incorrectly, the user may be kicked out of the current session, the worker hangs, the user logs in again, trying to edit what is already open in another worker process