Using Event Logs

Office Communications Server has always provided event logs to help identify problems and point out irregularities in the system. In Office Communications Server 2007 R2, there is even a filtered view of server warnings and errors that is presented in the MMC snap-in as a tabbed overview for each server. Office Communicator 2007 R2 can create event logs that you can enable by clicking Tools, clicking Options, and then on the General tab, selecting Turn On Windows Event Logging For Communicator, as shown in Figure 20-1. When issues arise, the event log is the first place to look for high-level guidance on problems that the server or client might already have identified. In general, warnings and errors will be of interest, but informational event logs will not.

Enabling Windows Event Logging For Communicator in Office Communicator

Figure 20-1. Enabling Windows Event Logging For Communicator in Office Communicator

Because the event log has the capability to filter and sort itself, it is not necessary to spend time searching the Application Event Log. All events the client logs show up in the Application Event Log, and all events from servers show up in the Office Communications Server Event Log. The View menu enables you to filter by event source; therefore, filtering for Office Communicator events or a particular server role is possible, as is filtering for only warnings and errors.

Usage Example: Using Event Logs

If event logs are enabled in Office Communicator, Office Communicator will create various event log entries, some informational and some that indicate issues. When an issue occurs, these entries are useful for diagnosing the root cause of the problem. The following example explains the problem, identifies data that is related to the problem, and explains the steps involved for solving the problem.

In the following example, event log message 1007 occurs because Office Communicator is configured with an invalid server name, IConfiguredAnInvalidServerName.litwareinc.com. The message explains that Office Communicator cannot find a server with that name when attempting to resolve the host name specified using the DNS. As is typical for most events, the actions to be taken next are explained in the event log Resolution.

Type: Error EventID: 1007 Source: Communicator
Description:
Communicator was unable to resolve the DNS hostname of the login server
IConfiguredAnInvalidServerName.litwareinc.com.

Resolution:
If you are using manual configuration for Communicator, please check that
the server name is typed correctly and in full. If you are using automatic
configuration, the network administrator will need to double-check the DNS
A record configuration for IConfiguredAnInvalidServerName.litwareinc.com
because it could not be resolved.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.144.40.212