|
What does the message mean: "Kform is locked by used Admin on computername"? |
|
|
|
This problem is caused by opportunistic locking. Microsoft defines opportunistic locking as follows:
"An opportunistic lock (also called an oplock) is a lock placed by a client on a file residing on a server. In most cases, a client requests an opportunistic lock so it can cache data locally, thus reducing network traffic and improving apparent response time. Opportunistic locks are used by network redirectors on clients with remote servers, as well as by client applications on local servers" and "Opportunistic locks are requests from the client to the server. From the point of view of the client, they are opportunistic. In other words, the server grants such locks whenever other factors make the locks possible".
Opportunistic locks increases performance for many file operations but may decrease performance in other operations because the server that grants the opportunistic lock must manage the breaking of that lock when another user requests access to the file.
Breaking an opportunistic lock is the process of degrading the lock that one client has on a file so that another client can open the file, with or without an opportunistic lock. When the other client requests the open operation, the server delays the open operation and notifies the client holding the opportunistic lock. The client holding the lock then takes actions appropriate to the type of lock, for example abandoning read buffers, closing the file, and so on. Only when the client holding the opportunistic lock notifies the server that it is done does the server open the file for the client requesting the open operation. Occasionally, the lock does completely release the file. One of the results of the incomplete break is the locking error message “Kform is locked by used Admin on computer name”. To remove Kform PM from the locked state, close the program on the workstation as specified in the error message computer name. If this does not release the lock, reboot the workstation. Persistent record lock errors can be handled by turning opportunistic locking off on the server and workstations. An explanation of opportunistic locking on Windows can be found at:
http://support.microsoft.com/kb/q129202/
|
