Microsoft KB Archive/257839

= CSC Does Not Synchronize Files But Reports That Synchronization Was Successful =

Article ID: 257839

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q257839



SYMPTOMS
Users may experience a problem when they attempt to synchronize changes made to files while working offline. Synchronization Manager reports that the synchronization finished successfully, but the files on the server do not reflect the changes made. If a user views the files in the Offline Files Folder on the workstation, the files no longer reflect the changes. The Synchronization Manager icon on the taskbar continues to report that changes made while offline have not been synchronized. If the user goes offline, the changes made to the files reappear when viewed from the Offline Files Folder.



CAUSE
During the synchronization process, a temporary file gets generated. If the drive is formatted with the NTFS file system, the user who is running the synchronization must have modify permission to the location where the temporary file is created. The synchronization process looks for a temporary folder in the root of the drive that holds the CSC folder. If a temporary folder does not exist, the synchronization process writes the temporary file in the root of the drive itself.

For example, by default the CSC folder is located in the %SystemRoot% folder. If the %SystemRoot% folder is located on drive C, the CSC cache is in the C:\Winnt\CSC folder. The synchronization process then looks for a C:\Temp folder to write the temporary file into during the synchronization. If the CSC folder is moved to another partition by using the Cachemov.exe utility, the synchronization process looks at that drive for the temporary folder. If the temporary folder does not exist, it then writes the temporary file to the root of that drive.

This can be a problem if users are not given NTFS permissions to write to the root of a drive. If the temporary file cannot be created, the modified files never get synchronized with the server.



WORKAROUND
A workaround is to create a temporary folder in the root of the drive that contains the CSC folder. On this temporary folder, assign the users the NTFS Modify or Full Control permission.

Additional query words: csc client side caching,

Keywords: kbprb KB257839

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.