Last Updated: June 1, 2011

Outlook 2003 Connector

The Outlook 2003 Connector for Microsoft® Online Services (BPOS-S) is used to provide additional functionality to users with Outlook 2003. The tool provides Free/Busy services and Offline Address Book functionality to clients who would otherwise not have those features available to them. MOSDAL collects the verbose logs and registry keys associated with the Outlook 2003 Connector, in addition to a script that enables verbose logging. The logs and registry settings are saved to: MOSDALReports > Outlook > Outlook2003Connector.

The Outlook 2003 Connector works by intercepting all Free/Busy and OAB requests from Outlook and proxies these requests to the Exchange 2007 Web Service. The program looks at each new process to determine if it is Outlook, and if Outlook is launched, the Outlook 2003 Connector hooks into all PF MAPI requests to trap the PF calls and proxy to the Web Service.

Enabling Verbose Logging for the Outlook 2003 Connector

The log files are named according to the following schema:  OUTLOOK[year-month-day]T[hours-minutes-seconds].[milliseconds].log. Each Outlook 2003 Connector  log line contains the following components: <date and time>,<loglevel>,<log id>,<native thread id>,<module>, <log message> An example of an Outlook 2003 Connector log line is:

Analyzing Outlook 2003 Connector Data

There are two main components for the Outlook 2003 Connector; a .NET component and a native component. When reviewing the verbose logs collected by MOSDAL, .NET errors can be found by searching for the keyword Exception. Examples of the verbose logs appears below (the keyword has been highlighted in this example for quick identification):

2009-11-19T14:35:01.980,3,0,[05c8],EWSAutodiscover.AutodiscoverFromFile,Exception:

 Message: The process cannot access the file 'C:\Documents and Settings\contoso1\Local Settings\Application Data\Microsoft\Sign In\Config\user@contoso1.microsoftonline.com\outlook-autodiscovery.xml' because it is being used by another process.

 StackTrace:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)

   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)

   at System.IO.FileStream..ctor(String path, FileMode mode)

   at Microsoft.ExchangeOnlineConnector.EWSAutodiscover.AutodiscoverFromFile(String emailAddress, String filePath, String& ASUrl, String& OABUrl) in P:\MSOLConnector\MSOLAddinUtil\EWSAutodiscover.cs:line 47

Errors from the native component can be found by searching for HRESULT 0x8 and should look something like:

2009-11-19T14:35:02.027,3,0,[05c8],BposRedirector::GetAutodiscoverUrls,AutodiscoverFromFile failed with HRESULT 0x80070020

After locating an exception hex code value, utilize the Error Code Lookup Tool (err.exe), which provides hex code parsing and output across multiple operating systems and applications. Users should specifically look at the MAPI hex code errors for this component, using the hex code identified in the log files.

Common Support Scenarios

  1. The Outlook 2003 Connector is unable to initialize.
  1. The Outlook 2003 Connector is started on a computer that does not have the Sign In Client is not installed.
  1. The Outlook 2003 Connector is loaded onto the computer, but the user is unable to access Free/Busy.
  1. An OAB manual download error appears when the user does has not selected the Download Address Book checkbox in the Outlook 2003 Send/Receive Settings section.
  2. The Outlook 2003 Connector is loaded, but the user cannot download the OAB.