System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Important This article contains information about how to modify the
registry. Make sure that you back up the registry before you modify it. Make
sure that you know how to restore the registry if a problem occurs. For more
information about how to back up, restore, and modify the registry, click the
following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry
You have a mixed Microsoft Exchange Server 2003 and Microsoft Exchange Server 2007 or Exchange Server 2010 mail environment.
The Disclaimer rule is enabled on the Exchange 2007 or Exchange 2010 server.
An e-mail message that is generated from Microsoft Office Outlook Web Access on Exchange 2003 is routed by using an Exchange 2007 or Exchange 2010 Server.
In this scenario, the e-mail message is corrupted. When this
problem occurs, the e-mail message is shown as the following HTML format.
< h t m l >
< h e a d >
< m e t a h t t p - e q u i v = " C o n t e n t - T y p e " c o n t e n t = " t e x t / h t m l ; c h a r s e t = u t f - 1 6 " >
< / h e a d >
< b o d y >
<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.3790.2858" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#000000 size=2>aaaa</FONT></DIV></BODY></HTML< b r >
< h r >
< f o n t f a c e = " A r i a l " c o l o r = " G r a y " s i z e = " & # 4 3 ; 0 " > M y D i s c l a i m e r < b r >
< / f o n t >
< / b o d y >
< / h t m l >
This problem occurs because Outlook Web Access for Exchange 2003 sets an e-mail message to an incorrect character set. When the message is routed by the Exchange 2007 or 2010 server that has the Disclaimer rule enabled, the e-mail message is converted to incorrect HTML
tagging based on the incorrect character set. Then, the message is corrupted by
the incorrect tagging.
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.
Prerequisites
This hotfix requires Microsoft Exchange Server 2003 Service Pack
2 to be installed on the server because of file dependencies. 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
Restart requirement
You have to
restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
hotfix.
Post-installation information
Warning Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These problems
might require that you reinstall the operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own
risk. After you install the hotfix, you must create the DisableUnicodePrefix registry entry in order to enable the hotfix. To do this, follow
these steps:
Click Start, click Run,
type Regedit , and then click OK.
On the Edit menu, point to
New, and then click DWORD Value.
In the details pane, type
DisableUnicodePrefix for the new value, and then press
ENTER.
Right-click DisableUnicodePrefix, and then
click Modify.
In the Edit DWORD Value dialog box, click
Decimal under Base.
In the Value data box, type
1, and then click OK.
Exit Registry Editor.
If
you are using a Non-English version server, you must extract the hotfix that is
mentioned in KB 942919 and then replace
“Microsoft.Exchange.OMA.UserInterface.dll component manually after you install
the hotfix. To do this, follow these steps:
Downalod the hotfix in KB 942919 and unzip the hotfix to
“Exchange2003-KB942919-x86.exe”
Run the following command in a command window to extract
the Microsoft.Exchange.OMA.UserInterface.dll file.
Exchange2003-KB942919-x86.exe /x
Replace the new “Microsoft.Exchange.OMA.UserInterface.dll”
into the “..\Exchsrvr\OMA\browse\bin” folder.
Restart the computer.
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.
Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
