The Microsoft Exchange Connector for Lotus Notes service stops functioning when you send an e-mail message that has a linked object in Exchange 5.5 or in Exchange 2003

View products that this article applies to.

SYMPTOMS

If you use Microsoft Exchange Client with WordMail to create an e-mail message that has a linked object attachment, and you send the e-mail message to a Lotus Notes recipient, the Microsoft Exchange Connector for Lotus Notes service may stop functioning.

Back to the top

CAUSE

This problem may occur if the following conditions are true:

You use Exchange Client with WordMail to create an e-mail message.
The e-mail message contains a linked attachment that you created by using the Link to File command.

You access the Link to File command by clicking the Insert menu, clicking File, and then clicking Link to File.
The mail is sent by using the Microsoft Exchange Connector for Lotus Notes.

Back to the top

RESOLUTION

Exchange Server 2003

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 (http://support.microsoft.com/kb/836993/ ) How to obtain the latest service packs for Exchange Server 2003

Back to the top

Exchange Server 5.5

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

Exchange Server 5.5 Service Pack 4 must be installed on your computer before you install this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Date         Time   Version            Size    File name
--------------------------------------------------------------
08-Jun-2004  20:47  5.5.2658.11       208,144  Ctreestd.dll     
08-Jun-2004  20:51  5.5.2658.11        44,816  Dispatch.exe     
08-Jun-2004  20:55  5.5.2658.11       106,256  Dxagwise.dll     
08-Jun-2004  20:52  5.5.2658.11        59,152  Dxamex.dll       
08-Jun-2004  20:52  5.5.2658.11        72,464  Dxanotes.dll     
08-Jun-2004  21:14  5.5.2658.11        49,936  Dxasnads.dll     
08-Jun-2004  20:51  5.5.2658.11       285,456  Exconmsg.dll     
08-Jun-2004  20:56  5.5.2658.11        42,256  Gw2mex.exe       
08-Jun-2004  20:55  5.5.2658.11       125,200  Gwhc.dll         
08-Jun-2004  23:28  5.5.2658.11       400,144  Gwrouter.exe     
08-Jun-2004  20:49  5.5.2658.11       178,448  Lscms.dll        
08-Jun-2004  21:08  5.5.2658.11        19,216  Lsdiajcl.exe     
08-Jun-2004  21:09  5.5.2658.11        68,880  Lsdiamex.exe     
08-Jun-2004  21:08  5.5.2658.11        57,616  Lsdiavm.exe      
08-Jun-2004  20:52  5.5.2658.11        31,504  Lsdxa.exe        
08-Jun-2004  20:49  5.5.2658.11        22,800  Lsldew.dll       
08-Jun-2004  21:09  5.5.2658.11        72,464  Lsmexdia.exe     
08-Jun-2004  20:49  5.5.2658.11       153,360  Lsmexhc.dll      
08-Jun-2004  20:49  5.5.2658.11       281,360  Lsmexif.dll      
08-Jun-2004  20:53  5.5.2658.11        14,608  Lsmexin.exe      
08-Jun-2004  20:54  5.5.2658.11        37,648  Lsmexnts.exe     
08-Jun-2004  20:49  5.5.2658.11       214,800  Lsntshc.dll      
08-Jun-2004  20:55  5.5.2658.11        48,912  Lsntsmex.exe     
08-Jun-2004  21:03  5.5.2658.11        96,528  Lsqview.dll      
08-Jun-2004  21:08  5.5.2658.11        22,800  Lsvmdia.exe      
08-Jun-2004  21:06  5.5.2658.11       140,048  Lsvmhc.dll       
08-Jun-2004  20:55  5.5.2658.11        52,496  Lsxfm.dll        
08-Jun-2004  20:56  5.5.2658.11        34,064  Mex2gw.exe       
08-Jun-2004  23:28  5.5.2658.11        72,976  Mlmignts.dll     
08-Jun-2004  20:54  5.5.2658.11        15,120  Ntsperf.dll      
08-Jun-2004  20:47  5.5.2658.11        16,656  Ntspxgen.dll

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.

Back to the top

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

817903 (http://support.microsoft.com/kb/817903/ ) New naming schema for Exchange Server software update packages

Back to the top