The problem is: When the wrun32 application is crashed or closed by the task manager a part of wrun32.exe is still running. (64-bit W2008-R2)
Normally causes a crashed runtimer no problem, because the user starts a new one, but a crashed runtimer in a lock situation will result in a read-lock error (status 99) for all users !!!!!!
In a terminal server environment it is hard to determine which wrun32 causes a lock-situation when the user did not report a crash. In this case the customer has 25 users and at least the same amount of wrun32 processes.
The Help-desk could not help me with this MICROSOFT problem,
Who can help me with a solution for this problem ?