Sdílet prostřednictvím

  • Článek

Using the Logging Tool With Communicator Web Access

Topic Last Modified: 2009-02-27

If you encounter serious problems with Communicator Web Access, you might need to contact Microsoft Customer Service and Support. In turn, support personnel might ask you to gather additional information using the Office Communications Server 2007 R2 Logging Tool.

The information captured by the tool will probably not be very useful to most system administrators. For example, a typical log file will contain thousands of lines of text similar to the following:

TL_INFO(TF_COMPONENT) [0]1268.12D0::10/13/2008-18:12:05.173.00000008 (CWAAuth,CRequestState::Attach:state.cpp(134))( 000000001C2F1948 ) SF_NOTIFY_PREPROC_HEADERS event: CRequestState::Attach called. URL: /cwa/Client/3.5.6808.0506/ChatWindow.htm

TL_INFO(TF_COMPONENT) [0]1268.12D0::10/13/2008-18:12:05.189.00000009 (CWAAuth,PreProcessHeaders:authfilt.cpp(215))PreProcessHeaders - Connection ID# 20

TL_INFO(TF_COMPONENT) [0]1268.12D0::10/13/2008-18:12:05.189.0000000a (CWAAuth,PreProcessHeaders:authfilt.cpp(254))Requested Url: /cwa/client/3.5.6808.0506/chatwindow.htm

Logging is conducted on a per-server basis. If you need to run debug sessions on multiple computers, you need to use this procedure to start up the Logging Tool on each of the computers.

To start a debugging sessions using the Logging Tool

  1. Log on to the computer that is running the Communicator Web Access snap-in. You must log on as a member of the local Administrators group and the RTCUniversalServerAdmins group.

  2. Click Start, point to Administrative Tools, and then click Microsoft Office Communications Server 2007 R2, Communicator Web Access.

  3. In the scope pane, right-click Microsoft Office Communications Server 2007 R2, Communicator Web Access (the top node), and then click Load Logging Tool.

  4. Select the Communicator Web Access components that you want to log, and then click Start Logging.

  5. To stop a logging session, click Stop Logging.

    Note

    It is possible to continue a logging session even if the Logging Tool is no longer visible onscreen. For example, if you try to exit the program while a logging session is in progress, a dialog box appears asking you if you want to stop logging before you exit. If you click No, logging will continue even though the Logging Tool is no longer visible. To terminate the logging session, restart the Logging Tool, and then click Stop Logging.