Briefcase Item Needs to Be Synchronized Twice

This article was previously published under Q190812
This article has been archived. It is offered "as is" and will no longer be updated.
You have a Briefcase folder, and a file in it has the synchronized copy ona Windows NT network share.

When you modify the file in the local folder, and synchronize it with theserver copy, the synchronization status still shows, "Needs updating." Whenyou synchronize it again, Briefcase offers to copy the file from the remotelocation, although the file time stamp is identical.

After Briefcase copies the file from the remote location, thesynchronization status is correctly set to "Up-to-date."
After Briefcase copies the file to the server during the first update, ituses FindFirstFile to read back the file information. In some cases, theLAN Manager redirector runs this API before the file is closed. If thishappens, the file size of the remote file is not correct and thesynchronization status is not set correctly.

In a network trace, you can see a frame sequence like this between theclient and server:

   SMB       C write, FID = 0x9804, Write 0x0 at 0x0000020E   SMB       R write, Wrote 0x0   SMB       C transact2 Set file info, FID = 0x9804   SMB       R transact2 Set file info (response)   SMB       C transact2 Findfirst, File = \Text2.txt   SMB       R transact2 Findfirst (response)   SMB       C close file, FID = 0x9804   SMB       R close file				

In response to the Findfirst server message block (SMB), you will see anincorrect file size.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.

Article ID: 190812 - Last Review: 11/02/2013 17:55:00 - Revision: 3.0

Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB190812