ZCS Connector How to report errors: Difference between revisions

No edit summary
No edit summary
Line 1: Line 1:
If you run into issues with the outlook connector, provide us with as much information as possible to help us quickly and efficiently identify the root cause. Some information that helps us:
If you run into issues with the outlook connector, provide us with as much information as possible to help us quickly and efficiently identify the root cause. Some information that helps us:


# System Information - provide us with as much system information as possible. The easiest way to get the most comprehensive system information is to export the data from msinfo32.exe. You can find out more about msinfo32.exe here.
#System Information - provide us with as much system information as possible. The easiest way to get the most comprehensive system information is to export the data from msinfo32.exe. You can find out more about msinfo32.exe here.


# Debug logs - the connector spews mountains of debug data to the debug stream. You can use tools like DebugView (free from sysinternals) to capture/view debug output. This will help us track down whats going on.
#Debug logs - the connector spews mountains of debug data to the debug stream. You can use tools like DebugView (free from sysinternals) to capture/view debug output. This will help us track down whats going on.


# Rpc tracing - the connector uses WinHttp like the migration wizard. Refer to this post on how to setup tracing for WinHttp.
#Rpc tracing - the connector uses WinHttp like the migration wizard. Refer to this post on how to setup tracing for WinHttp.
# Server version - let us know which ZCS version you are running against.
#Server version - let us know which ZCS version you are running against.


# A comprehensive description of the issue
#A comprehensive description of the issue

Revision as of 21:28, 17 December 2006

If you run into issues with the outlook connector, provide us with as much information as possible to help us quickly and efficiently identify the root cause. Some information that helps us:

  1. System Information - provide us with as much system information as possible. The easiest way to get the most comprehensive system information is to export the data from msinfo32.exe. You can find out more about msinfo32.exe here.
  1. Debug logs - the connector spews mountains of debug data to the debug stream. You can use tools like DebugView (free from sysinternals) to capture/view debug output. This will help us track down whats going on.
  1. Rpc tracing - the connector uses WinHttp like the migration wizard. Refer to this post on how to setup tracing for WinHttp.
  2. Server version - let us know which ZCS version you are running against.
  1. A comprehensive description of the issue
Jump to: navigation, search