OL2002: The Exchange Client Extension "IExchExtCallBack::SetRecipients" Call Does Not Update the User Interface

View products that this article applies to.

This article was previously published under Q303975

Expand all | Collapse all

SYMPTOMS

When you use Microsoft Exchange Client Extensions with Outlook, the IExchExtCallBack::SetRecipients call does not display the recipients to the Outlook user interface. Recipients are set in the recipients list, and recipients receive their messages, but they are not displayed in recipient controls.

Back to the top

CAUSE

This problem can occur if Outlook does not update the recipients to the appropriate recipient controls (the To field, the Cc field, and the Bcc field).

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307841 (http://support.microsoft.com/kb/307841/EN-US/ ) OFFXP: How to Obtain the Latest Office XP Service Pack

The English version of this fix should have the following file attributes or later:

   Date        Time         Version       Size       File name    
   -------------------------------------------------------------
   7/6/2001    05:36:36 PM  10.0.3103.0   6,297,928  Outllib.dll

Back to the top

WORKAROUND

To work around this problem, use the Outlook object model. For additional information about how to use Outlook object model from Microsoft Visual C++, click the article number below to view the article in the Microsoft Knowledge Base:

259298 (http://support.microsoft.com/kb/259298/EN-US/ ) HOWTO: Use Microsoft Outlook Object Model From Visual C++ Through an #IMPORT Statement

286408 (http://support.microsoft.com/kb/286408/EN-US/ ) White Paper: Microsoft Outlook and Exchange Client Extensions

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office XP Service Pack 1.

Back to the top