Export (0) Print
Expand All

Troubleshooting for Office Communications Server 2007 R2

Communications Server 2007 R2

Topic Last Modified: 2009-06-24

Office Communications Server 2007 R2 includes several logging and diagnostics tools that can help troubleshoot an Office Communications Server deployment. The tools include:

  • OCSLogger. Generates logs for different server components while the server is running.
  • Snooper. Protocol analysis tool designed to view logs generated by the OCSLogger tool; loads the supplied log file and shows the messages in its display. Snooper is part of Microsoft Office Communications Server 2007 R2 Resource Kit Tools. The Resource Kit includes documentation for using the tool.

Office Communications Server also includes ms-diagnostics headers that are error code extensions that solve the need for more granular SIP error codes to communicate diagnostic information through a new ms-diagnostics header. There are two purposes of these error code extensions:

  • Convey diagnostic information to help troubleshoot infrastructure (server) problems, misconfigurations, syntactical problems and other reasons for a non-successful SIP response.
  • Convey actionable error codes to the client, which can then be used by the client applications, such as the Live Meeting client and Office Communicator, to display appropriate errors to the user.

The error IDs and reason values for ms-diagnostic headers are documented in the “Appendix A: Diagnostics Header Error ID and Reason Values” section of the [MS-OCER]: Client Error Reporting Protocol Specification at http://go.microsoft.com/fwlink/?LinkId=144413.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft