Microsoft Knowledge Base Email Alertz

KBAlertz.com: The contents of attachments are changed to match the contents of the first attachment in Exchange Server 2003 when an e-mail message contains multiple attachments that have DBCS characters in their file names

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 2.0 Web Hosting with SQL 2005: Click Here!
Discount ASP.NET Hosting


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




The contents of attachments are changed to match the contents of the first attachment in Exchange Server 2003 when an e-mail message contains multiple attachments that have DBCS characters in their file names

Article ID:946055
Last Review:April 2, 2008
Revision:1.1
On This Page

SYMPTOMS

You send an e-mail message that contains multiple attachments from a server that is running Lotus Notes server to a server that is running Microsoft Exchange Server 2003. If the attachments have similar double-byte character set (DBCS) characters in their file names, all the contents of the attachments are changed to match the contents of the first attachment. However, the file names are not changed.

For example, if you send attachments that have similar DBCS characters in their file names as in the following example, all the contents of the attachments are changed to match the contents of the first attachment:
<DBCS>1.txt
<DBCS>2.txt
<DBCS>3.txt
Note The <DBCS> placeholder represents the same DBCS characters.

Back to the top

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support (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.

Prerequisites

You must have Microsoft Exchange Server 2003 Service Pack 2 (SP2) and Lotus Notes Client 6.x installed before you apply this hotfix.

Restart requirement

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

Hotfix replacement information

This 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.
File nameFile versionFile sizeDateTimePlatform
Exchmem.dll6.5.7991.0160,76807-Feb-200803:44x86
Notescondata.dll6.5.7991.01,320,96007-Feb-200804:52x86
Pttrace.dll6.5.7991.016,38406-Feb-200816:57x86
Exchmem.dll6.5.7991.0160,76807-Feb-200803:44x86
Notescup.dll6.5.7991.05,63206-Feb-200816:55x86
Ntscupwp.dll6.5.7991.039,42406-Feb-200816:55x86
Addxa.dll6.5.7991.0565,76006-Feb-200816:52x86
Aqadmcon.dll6.5.7991.044,54406-Feb-200816:55x86
Ctreestd.dll6.5.7991.0203,77606-Feb-200816:51x86
Devcon.dll6.5.7991.06,14406-Feb-200816:53x86
Dispatch.exe6.5.7991.037,88806-Feb-200816:53x86
Dxamex.dll6.5.7991.036,86406-Feb-200816:53x86
Dxanotes.dll6.5.7991.058,36806-Feb-200816:54x86
Lscmd.exe6.5.7991.023,04006-Feb-200816:53x86
Lscms.dll6.5.7991.0157,18406-Feb-200816:52x86
Lscntrl.exe6.5.7991.050,17606-Feb-200816:53x86
Lscps.dll6.5.7991.0339,45606-Feb-200816:58x86
Lsctrl.exe6.5.7991.07,16806-Feb-200816:53x86
Lsdevlog.dll6.5.7991.08,19206-Feb-200816:53x86
Lsdevnt.dll6.5.7991.010,24006-Feb-200816:53x86
Lsdevui.dll6.5.7991.07,68006-Feb-200816:52x86
Lsdxa.exe6.5.7991.027,64806-Feb-200816:53x86
Lsinst.dll6.5.7991.08,70406-Feb-200816:54x86
Lslde.dll6.5.7991.066,04806-Feb-200816:52x86
Lsldew.dll6.5.7991.016,89606-Feb-200816:52x86
Lsmain.exe6.5.7991.041,47206-Feb-200816:54x86
Lsmexhc.dll6.5.7991.0128,51206-Feb-200816:52x86
Lsmexif.dll6.5.7991.0233,98406-Feb-200816:52x86
Lsmexin.exe6.5.7991.011,77606-Feb-200816:54x86
Lsmexnts.exe6.5.7991.034,81606-Feb-200816:54x86
Lsmexout.exe6.5.7991.011,77606-Feb-200816:54x86
Lsntshc.dll6.5.7991.0218,62406-Feb-200816:52x86
Lsntsmex.exe6.5.7991.046,08006-Feb-200816:55x86
Lspa.exe6.5.7991.013,31206-Feb-200816:55x86
Lspcta.dll6.5.7991.027,64806-Feb-200816:52x86
Lsrcc.dll6.5.7991.07,16806-Feb-200816:52x86
Lsrcs.dll6.5.7991.019,45606-Feb-200816:52x86
Lsxfm.dll6.5.7991.043,00806-Feb-200816:55x86
Mlmig32.dll6.5.7991.04,469,76006-Feb-200816:50x86
Ntsperf.dll6.5.7991.019,96806-Feb-200816:58x86
Adclog.dll6.5.7991.01,184,25606-Feb-200816:56x86
Calconmsg.dll6.5.7991.0262,65606-Feb-200817:10x86
Exconmsg.dll6.5.7991.04,523,00806-Feb-200816:58x86

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.

Back to the top

MORE INFORMATION

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.

Back to the top


APPLIES TO
Microsoft Exchange Server 2003 Standard Edition
Microsoft Exchange Server 2003 Enterprise Edition

Back to the top

Keywords: 
kbautohotfix kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB946055

Back to the top

       

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