Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
The Windows Redirector May Cancel a Session During a Long Locking Operation
Article ID: 320310 - View products that this article applies to.
This article was previously published under Q320310
The Windows redirector may incorrectly cancel a session during long-lasting locking operations. This problem may occur in the following scenario:
If the LOCKFILE_FAIL_IMMEDIATELY flag in the LockFileEx function is not set, the server returns only when the file has been successfully locked. This is by design. If this takes longer than the client-side session time-out, the client's redirector cancels the connection.
Windows 2000To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Date Time Version Size File name --------------------------------------------------------- 11-Mar-2002 13:14:40 5.0.2195.5059 370,480 Mrxsmb.sys 07-Mar-2002 13:16:30 5.0.2195.5042 131,920 Rdbss.sys
The fix is to treat the SMB Lock & X command as a long-standing SMB. This makes the command exempt from the Sesstimeout timer. The redirector will wait as long as it must.
Windows XPTo resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/EN-US/ )How to Obtain the Latest Windows XP Service Pack
To work around this problem, use LockFileEx(,,LOCKFILE_FAIL_IMMEDIATELY) instead of LOCKFILE_EXCLUSIVE_LOCK. The LOCKFILE_FAIL_IMMEDIATELY flag returns with an appropriate error if the file is already in use. The program can programmatically try to lock the file again later.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3 (SP3) and Microsoft Windows XP Service Pack 1 (SP1).
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/EN-US/ )The Datacenter Program and Windows 2000 Datacenter Server Product
(http://support.microsoft.com/kb/296861/EN-US/ )Use QChain.exe to Install Multiple Hotfixes with One Reboot
Article ID: 320310 - Last Review: February 22, 2007 - Revision: 3.3