Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XIMS: Chat Transcription Logs Are Not Created in Correct Location


View products that this article applies to.

This article was previously published under Q242106

↑ Back to the top


Symptoms

If you enable the transcription capabilities of the Microsoft Chat service for a channel, you may not be able to find the transcription logs. The Chat service for Exchange Server version 5.5 may write the log information to the wrong location.

↑ Back to the top


Cause

This problem can occur because the Chat service in Exchange Server 5.5 writes its log information to the following folder by default
X:\InetPub\Chat\Transcripts\channel_name
where channel_name is the name of the channel for which transcription capabilities are enabled.

Different transcription paths are used where X is one of the following:
  • Blank. Transcription logs are created and stored in the rootdrive\channel_name folder, where rootdrive is the drive letter chosen as the root drive.
  • " \ " (without the quotation marks). Transcription logs are not created and there is an approximately 2 second delay for client channel entry.
  • "Path" (without the quotation marks). Transcription logs are created and stored in the windir\System32\channel_name folder, where windir is the folder in which Windows is installed.

↑ Back to the top


Resolution

To resolve this problem, make sure that you define the full path to the folder that you want to use for transcript storage. To define the transcription logging path on a Chat server:
  1. Click the Start button, point to Programs, and then click Exchange Chat Manager MMC.
  2. On the Extensions menu, click Tscript.
  3. In the Default Location box, edit the path as appropriate.
  4. Click Apply, and then click OK.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

↑ Back to the top


Keywords: KB242106, kbnofix, kbbug

↑ Back to the top

Article Info
Article ID : 242106
Revision : 7
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 224