Select the product you need help with
A message that is sent repeatedly through Exchange Connector for Lotus Notes develops text formatting problemsArticle ID: 829989 - View products that this article applies to. On This PageSYMPTOMSWhen a message is sent repeatedly through Microsoft Exchange
Connector for Lotus Notes, the message may develop text formatting problems.
Every time that the message is sent, the word-wrap and the left-indent
formatting may increase, until the message becomes almost unreadable.
RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for 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
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. Component: Exchange\Notesmc\Msg
Content
(http://support.microsoft.com/contactus/?ws=support)
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 item in Control Panel. Microsoft Exchange 2000 Server Date Time Version Size File name ---------------------------------------------------------- 24-Nov-2003 18:15 6.0.6540.0 40,960 Gw2mex.exe 24-Nov-2003 18:14 6.0.6540.0 110,592 Gwhc.dll 24-Nov-2003 18:18 6.0.6540.0 868,352 Lsadmin.exe 24-Nov-2003 18:10 6.0.6540.0 163,840 Lscms.dll 24-Nov-2003 18:10 6.0.6540.0 73,728 Lslde.dll 24-Nov-2003 18:10 6.0.6540.0 28,672 Lsldew.dll 24-Nov-2003 18:10 6.0.6540.0 139,264 Lsmexhc.dll 24-Nov-2003 18:10 6.0.6540.0 237,568 Lsmexif.dll 24-Nov-2003 18:13 6.0.6540.0 20,480 Lsmexin.exe 24-Nov-2003 18:13 6.0.6540.0 40,960 Lsmexnts.exe 24-Nov-2003 18:13 6.0.6540.0 20,480 Lsmexout.exe 24-Nov-2003 18:10 6.0.6540.0 118,784 Lsmmdodb.dll 24-Nov-2003 18:10 6.0.6540.0 200,704 Lsntshc.dll 24-Nov-2003 18:14 6.0.6540.0 49,152 Lsntsmex.exe 24-Nov-2003 18:14 6.0.6540.0 49,152 Lsxfm.dll 24-Nov-2003 18:15 6.0.6540.0 32,768 Mex2gw.exe 25-Nov-2003 08:58 6.0.6540.0 2,551,808 Mlmig32.dll 24-Nov-2003 17:56 6.0.6540.0 69,632 Mlmignts.dll Date Time Version Size File name ---------------------------------------------------------- 10-Jan-2005 04:23 6.5.7232.66 190,976 Lsntshc.dll For more information, click the following article number to view the article in the Microsoft Knowledge Base: 301378
(http://support.microsoft.com/kb/301378/
)
How to obtain the latest
Exchange 2000 Server service pack
MORE INFORMATIONAfter you install the hotfix, you must add a new entry in
the ..Exchsrvr\Bin\Exchconn.ini file. To do this, follow these
steps:
STATUSMicrosoft
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 Exchange Server 2003 Service Pack 2. PropertiesArticle ID: 829989 - Last Review: November 13, 2006 - Revision: 4.5 APPLIES TO
|



Back to the top








