Mentioned
In
|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 946324 - Last Review: April 3, 2008 - Revision: 1.2 Exchange Server 2003 users cannot use the Exchange Server 2003 Connector for Lotus Notes to send e-mail messages to Domino recipients who have ANSI 1252 8-bit characters in their namesYou use Microsoft Exchange Server 2003 and a version of the Microsoft Exchange Server 2003
Connector for Lotus Notes that is between version 06.05.7233 and version
06.05.7974. In this situation, you cannot use an
Asian language version of the Exchange Server 2003 Connector for Lotus
Notes to send e-mail
messages to Lotus Domino recipients who have
ANSI
1252 8-bit characters
(such as "ç", "â" or "û") in their names.
For example, this problem occurs in the Chinese, Japanese, or Korean language
version of the Exchange Server 2003 Connector for Lotus Notes.
Additionally, you may receive a non-delivery report (NDR) message that
resembles the following: Your message did not reach some
or all of the intended recipients.
Subject: <subject
of the message> Sent:
<date> The following recipient(s) could
not be reached: <address of notes
user><date time> The
e-mail address could not be found. Perhaps the recipient moved to a different
e-mail organization, or there was a mistake in the address. Check the address
and try again. The Exchange Server 2003 Connector for Lotus
Notes
proxy address of the affected Domino recipients correctly contains
the ANSI 1252 8-bit
characters. However,
the Exchange Server 2003 transport
component converts the characters to question
marks in some language environments. Hotfix information A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. 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, contact 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: 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. PrerequisitesMicrosoft Exchange Server 2003 Service Pack 2 (SP2) and Lotus
Notes Client 6.x must be installed before you apply this hotfix. Restart requirementYou do
not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace a previously released
hotfix. 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 item in Control
Panel. Collapse this tableExpand this table | File name | File version | File
size | Date | Time | Platform |
|---|
| Exchmem.dll | 6.5.7991.0 | 160,768 | 07-Feb-2008 | 03:44 | x86 | | Notescondata.dll | 6.5.7991.0 | 1,320,960 | 07-Feb-2008 | 04:52 | x86 | | Pttrace.dll | 6.5.7991.0 | 16,384 | 06-Feb-2008 | 16:57 | x86 | | Exchmem.dll | 6.5.7991.0 | 160,768 | 07-Feb-2008 | 03:44 | x86 | | Notescup.dll | 6.5.7991.0 | 5,632 | 06-Feb-2008 | 16:55 | x86 | | Ntscupwp.dll | 6.5.7991.0 | 39,424 | 06-Feb-2008 | 16:55 | x86 | | Addxa.dll | 6.5.7991.0 | 565,760 | 06-Feb-2008 | 16:52 | x86 | | Aqadmcon.dll | 6.5.7991.0 | 44,544 | 06-Feb-2008 | 16:55 | x86 | | Ctreestd.dll | 6.5.7991.0 | 203,776 | 06-Feb-2008 | 16:51 | x86 | | Devcon.dll | 6.5.7991.0 | 6,144 | 06-Feb-2008 | 16:53 | x86 | | Dispatch.exe | 6.5.7991.0 | 37,888 | 06-Feb-2008 | 16:53 | x86 | | Dxamex.dll | 6.5.7991.0 | 36,864 | 06-Feb-2008 | 16:53 | x86 | | Dxanotes.dll | 6.5.7991.0 | 58,368 | 06-Feb-2008 | 16:54 | x86 | | Lscmd.exe | 6.5.7991.0 | 23,040 | 06-Feb-2008 | 16:53 | x86 | | Lscms.dll | 6.5.7991.0 | 157,184 | 06-Feb-2008 | 16:52 | x86 | | Lscntrl.exe | 6.5.7991.0 | 50,176 | 06-Feb-2008 | 16:53 | x86 | | Lscps.dll | 6.5.7991.0 | 339,456 | 06-Feb-2008 | 16:58 | x86 | | Lsctrl.exe | 6.5.7991.0 | 7,168 | 06-Feb-2008 | 16:53 | x86 | | Lsdevlog.dll | 6.5.7991.0 | 8,192 | 06-Feb-2008 | 16:53 | x86 | | Lsdevnt.dll | 6.5.7991.0 | 10,240 | 06-Feb-2008 | 16:53 | x86 | | Lsdevui.dll | 6.5.7991.0 | 7,680 | 06-Feb-2008 | 16:52 | x86 | | Lsdxa.exe | 6.5.7991.0 | 27,648 | 06-Feb-2008 | 16:53 | x86 | | Lsinst.dll | 6.5.7991.0 | 8,704 | 06-Feb-2008 | 16:54 | x86 | | Lslde.dll | 6.5.7991.0 | 66,048 | 06-Feb-2008 | 16:52 | x86 | | Lsldew.dll | 6.5.7991.0 | 16,896 | 06-Feb-2008 | 16:52 | x86 | | Lsmain.exe | 6.5.7991.0 | 41,472 | 06-Feb-2008 | 16:54 | x86 | | Lsmexhc.dll | 6.5.7991.0 | 128,512 | 06-Feb-2008 | 16:52 | x86 | | Lsmexif.dll | 6.5.7991.0 | 233,984 | 06-Feb-2008 | 16:52 | x86 | | Lsmexin.exe | 6.5.7991.0 | 11,776 | 06-Feb-2008 | 16:54 | x86 | | Lsmexnts.exe | 6.5.7991.0 | 34,816 | 06-Feb-2008 | 16:54 | x86 | | Lsmexout.exe | 6.5.7991.0 | 11,776 | 06-Feb-2008 | 16:54 | x86 | | Lsntshc.dll | 6.5.7991.0 | 218,624 | 06-Feb-2008 | 16:52 | x86 | | Lsntsmex.exe | 6.5.7991.0 | 46,080 | 06-Feb-2008 | 16:55 | x86 | | Lspa.exe | 6.5.7991.0 | 13,312 | 06-Feb-2008 | 16:55 | x86 | | Lspcta.dll | 6.5.7991.0 | 27,648 | 06-Feb-2008 | 16:52 | x86 | | Lsrcc.dll | 6.5.7991.0 | 7,168 | 06-Feb-2008 | 16:52 | x86 | | Lsrcs.dll | 6.5.7991.0 | 19,456 | 06-Feb-2008 | 16:52 | x86 | | Lsxfm.dll | 6.5.7991.0 | 43,008 | 06-Feb-2008 | 16:55 | x86 | | Mlmig32.dll | 6.5.7991.0 | 4,469,760 | 06-Feb-2008 | 16:50 | x86 | | Ntsperf.dll | 6.5.7991.0 | 19,968 | 06-Feb-2008 | 16:58 | x86 | | Adclog.dll | 6.5.7991.0 | 1,184,256 | 06-Feb-2008 | 16:56 | x86 | | Calconmsg.dll | 6.5.7991.0 | 262,656 | 06-Feb-2008 | 17:10 | x86 | | Exconmsg.dll | 6.5.7991.0 | 4,523,008 | 06-Feb-2008 | 16:58 | x86 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base: 824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates For more information about the
naming schema for Exchange Server software updates, click the following article
number to view the article in the Microsoft Knowledge Base: 817903Â
(http://kbalertz.com/Feedback.aspx?kbNumber=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, about the
performance or reliability of these products.
APPLIES TO- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
| kbautohotfix kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB946324 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
|
 |
 |
 |
 |
 |
 |
 |
| |