You receive a "WMS idle: lsmexout.exe - application error" error message, and the Exchange Connector for Lotus Notes unexpectedly quits in Exchange Server 5.5 or in Exchange Server 2003

Article translations Article translations
Article ID: 889316 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page


On a computer that is running Microsoft Exchange Server 5.5 or Microsoft Exchange Server 2003, and where you have installed the Microsoft Exchange Connector for Lotus Notes, you may experience all the following symptoms:
  • The Microsoft Exchange Connector for Lotus Notes service unexpectedly quits.
  • You receive the following error message:
    WMS Idle: lsmexout.exe - Application Error

    The instruction at "0x780104ac" referenced memory at "0x010d1000". The memory could not be "read".
  • The Microsoft Exchange Information Store service (Store.exe) process consumes up to 100 percent of CPU usage. In this scenario, the Microsoft Exchange Information Store service may stop responding.
  • Log files from the Microsoft Exchange Connector for Lotus Notes may contain event ID 31202 messages with unreadable event descriptions. For example, event ID 31202 may be logged with a description that is similar to the following:



This problem occurs because of a code defect in the Exchange Server Linkage Message Exchange (Lsmexif.dll ) library.


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 How to obtain the latest service packs for Exchange Server 2003

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:
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.


Because of file dependencies, you must be running Exchange Server 5.5 Service Pack 4 (SP4) to install this hotfix. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 How to obtain the latest Exchange Server 5.5 service pack

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, the Exchange Notes Connector and the Microsoft Exchange Calendar Connector are automatically stopped and then restarted when 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 file attributes) 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
   01-Dec-2004  22:05  5.5.2658.26       214,800  Lsntshc.dll      
   01-Dec-2004  22:05  5.5.2658.26       208,144  Ctreestd.dll     
   01-Dec-2004  22:06  5.5.2658.26        44,816  Dispatch.exe     
   01-Dec-2004  22:08  5.5.2658.26       106,256  Dxagwise.dll     
   01-Dec-2004  22:07  5.5.2658.26        59,152  Dxamex.dll       
   01-Dec-2004  22:07  5.5.2658.26        72,464  Dxanotes.dll     
   01-Dec-2004  22:17  5.5.2658.26        49,936  Dxasnads.dll     
   01-Oct-2002  22:57                  2,930,240  Eab.dxa
   01-Dec-2004  22:06  5.5.2658.26       285,456  Exconmsg.dll     
   01-Dec-2004  22:08  5.5.2658.26        42,256  Gw2mex.exe       
   01-Dec-2004  22:08  5.5.2658.26       125,200  Gwhc.dll         
   02-Dec-2004  00:13  5.5.2658.26       400,144  Gwrouter.exe     
   01-Dec-2004  22:05  5.5.2658.26       178,448  Lscms.dll        
   01-Dec-2004  22:13  5.5.2658.26        19,216  Lsdiajcl.exe     
   01-Dec-2004  22:14  5.5.2658.26        68,880  Lsdiamex.exe     
   01-Dec-2004  22:14  5.5.2658.26        57,616  Lsdiavm.exe      
   01-Dec-2004  22:07  5.5.2658.26        32,016  Lsdxa.exe        
   01-Dec-2004  22:05  5.5.2658.26        22,800  Lsldew.dll       
   01-Dec-2004  22:14  5.5.2658.26        72,464  Lsmexdia.exe     
   01-Dec-2004  22:05  5.5.2658.26       153,360  Lsmexhc.dll      
   01-Dec-2004  22:05  5.5.2658.26       281,360  Lsmexif.dll      
   01-Dec-2004  22:07  5.5.2658.26        14,608  Lsmexin.exe      
   01-Dec-2004  22:07  5.5.2658.26        37,648  Lsmexnts.exe     
   01-Dec-2004  22:05  5.5.2658.26       214,800  Lsntshc.dll      
   01-Dec-2004  22:08  5.5.2658.26        48,912  Lsntsmex.exe     
   01-Dec-2004  22:11  5.5.2658.26        96,528  Lsqview.dll      
   01-Dec-2004  22:14  5.5.2658.26        22,800  Lsvmdia.exe      
   01-Dec-2004  22:13  5.5.2658.26       140,048  Lsvmhc.dll       
   01-Dec-2004  22:08  5.5.2658.26        52,496  Lsxfm.dll        
   01-Dec-2004  22:08  5.5.2658.26        34,064  Mex2gw.exe       
   02-Dec-2004  00:35  5.5.2658.26        72,976  Mlmignts.dll     
   01-Dec-2004  22:07  5.5.2658.26        15,120  Ntsperf.dll      
   01-Dec-2004  22:05  5.5.2658.26        16,656  Ntspxgen.dll     
   01-Oct-2002  22:57                  2,928,160  Psab.dxa


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.

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 New naming schema for Exchange Server software update packages

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.


Article ID: 889316 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Exchange Server 5.5 Standard Edition
kbnosurvey kbarchive kbexchange550presp5fix kbbug kbfix kbqfe kbhotfixserver KB889316

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from