XFOR: PROFS: LME-PROFS-DIAMEX Fails to Process the Incoming Message from OV/VM

ID: Q216065

The information in this article applies to:

SYMPTOMS

When Microsoft Exchange Connector (PROFS) process an incoming Mail message, the following messages can be found in the Microsoft Exchange Connector Administrator's log viewer:

1998/10/15 08:46:27- LME-PROFS-DIAMEX(017b) 1 31000:Resource error:
Corrupted RTF Object [{Invalid syntax}]
>> mexe(14607)
1998/10/15 08:46:27- LME-PROFS-DIAMEX(017b) 1 56119:{Invalid syntax}:
Could not write file 'q\OBJECTS\26d6b61c.tmp' to Exchange message body
>> dia2mex(4171)


CAUSE

The problem occurs when the size of the RTF stream in lpRTFBody (which contains the original message body from the host and the RTF specific header and keywords) is a multiple of 4K, for example, 4096, 8192, and so forth. This problem was consistently reproduced by using different font settings, as long as the size is 4096 or 8192. The return code when the call fails is actually ERROR_INVALID_PARAMETER.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Component: MAPI

File name Version
Mapi32.dll 5.5.2540.0



NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.

Additional query words: 


Keywords          : 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 3, 1999