The information in this article applies to:
SYMPTOMSManually compressing the Offline Files cache\database (the %SystemRoot%\CSC folder) works, and files currently stored in the cache are compressed, but newly cached files are not stored in compressed format and previously compressed files become uncompressed after synchronization. CAUSEOffline file compression is not directly supported by Offline Files. Windows 2000 writes files in uncompressed format even if the folder is marked for compression. This ensures that a deadlock situation does not occur. Marking the CSC (Client Side Caching) folder to be compressed and leaving it this way can cause a variety of complications ranging from caching update problems to Windows 2000 not responding (hanging) while attempting to access files residing within the cache. RESOLUTIONTo prevent this problem from occurring, do not compress the Offline Files cache/database (the CSC folder). STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. MORE INFORMATION
If the CSC folder is specifically marked to be compressed, file system calls are made by CSC to ensure that the files get marked as uncompressed. This is done each time a file is accessed within the database. Q230738 How to Restart the Offline Files Cache/DatabaseUnder typical conditions, a file that currently resides within the cache as compressed is uncompressed after a synchronization update if the file has changes that are written back to the cache. The most common issue that results from compressing the CSC folder is a client computer hanging while attempting to access a cached document while offline. Additional query words:
Keywords : kbenv kbtool |
Last Reviewed: December 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |