Symptoms
Consider the following scenario:
- You sign in to Microsoft Office Communicator 2007 R2, and then you enable logging.
- You install the cumulative update that is described in Microsoft Knowledge Base (KB) article 2291453.
- You restart the computer and then sign in to Office Communicator 2007 R2 again.
communicator.exe - Corrupt File
The file or directory <Device>:\Users\<AccountName>\tracing is corrupt and unreadable. Please run the Chkdsk utility.
Additionally, the following events are logged in the Application log: The file or directory <Device>:\Users\<AccountName>\tracing is corrupt and unreadable. Please run the Chkdsk utility.
- Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: <Date>
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: <User>
Computer: <ComputerName>
Description:
Session "Communicator" failed to start with the following error: 0xC0000035 - Log Name: System
Source: Ntfs
Date: <Date>
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume3.
Workaround
To work around this issue, disable the logging feature in Office Communicator 2007 R2. To do this, follow these steps:
- Click the Show Menu button in the upper-left corner of Office Communicator 2007 R2.
- Point to Tool, click Option, and then click General.
- Under logging, click to clear the Turn on logging in Communicator check box, and then click OK.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.