Article ID: 166500 - Last Review: October 28, 2006 - Revision: 2.4 XCLN: Exchange 3.x Client Cannot Fully Display or Save Large Message BodiesThis article was previously published under Q166500 SYMPTOMS
The Microsoft Exchange Windows 3.x client cannot fully display, or save
to a disk file, messages containing large bodies of text. When you attempt
to read such a message, the following error message appears:
You've exceeded the maximum amount of text.
The object could not be inserted. The action could not be completed.
The object could not be inserted. The message body is full. To avoid overwriting the original text, the original message header may be only partially added. CAUSE
The Microsoft Exchange Windows 3.x client uses a 16-bit implementation of
the RichEdit control (Riched.dll) for manipulating the contents of the MAPI
property, PR_BODY, which includes the body text of the message. The Windows
3.x client RichEdit control has a limit of holding a maximum of 65,535 hard
line breaks.
WORKAROUND
To work around this problem, do one of the following:
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Windows
3.x client version 4.0. We are currently researching this problem and will
post more information here in the Microsoft Knowledge base as it becomes
available.
Microsoft has confirmed this to be a problem in Microsoft Exchange Windows 3.x client version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
With the fix applied, a modification is made to WMSUI.DLL so that it
reports the following error Microsoft when you a Save a message as text and
the message has a large text body that exceeds the RICHEDIT limit:
The item(s) could not be saved. You've exceeded the maximum amount of
text.
| Article Translations
|

Back to the top
