Behavior:
The following bugs known to IBM (SPRs) in Lotus Notes impede or prevent document archiving via CONNECT to Notes.
- XZWG7MLAX5: Get error "Not enough memory" when opening an rtf file which exports richtext items using _XRTF dll.
- WMUH7BMKYQ: LNRichText: Export to Microsoft Word has considerable fidelity loss in format or cannot be opened with MS Word.
The following documents are affected by this:
The cause of this problem, according to IBM, apparently lies with certain e-mail senders who use a Microsoft Exchange Server. Microsoft Exchange Server does not – according to IBM – use the standards-compliant Rich Text format, which means that IBM Lotus Domino Server is forced to convert the document on receiving an e-mail in this format. This conversion in turn is done in all current Domino Server versions in a format that means it may not be possible to export the affected documents properly via Lotus Notes C-API.
These potentially problematic Lotus Notes documents can be recognized because they have a field named $NoteHasNativeMIME with the value "1". The mere existence of this field however, does not necessarily mean that the document in question is affected by this error.
The error is a result of a series of several problems, however according to IBM the bugs are now detected in the Lotus Notes C-API.
DocuWare CONNECT to Notes uses the Lotus Notes C-API.
However, the particular effect of this bug is the random result of the faulty document export.
In the best case, the whole export procedure is aborted. This abort can be intercepted by CONNECT to Notes and the archiving is stopped with an error message.
In the case that the C-API export is aborted, CONNECT to Notes outputs an OLE error when the document tries to export.
In the worst case, the RTF document produced by the export is inconsistent with itself, but the C-API does not output an error message. This result cannot be intercepted by CONNECT to Notes and results in a document archived in DocuWare, which cannot be viewed in any text viewer.
Solution:
Currently no solution from IBM (as of 04/2009).
In rare cases, it is possible to archive a document successfully by inserting a space at the end of the body text of such a document on the Notes Client before archiving and then saving the document again. However, this does not always help and cannot therefore be considered as a consistent workaround. For documents with graphic elements (such as HTML e-mails), this change can lead to the loss of the original document layout. This procedure must therefore be tested thoroughly before it is used!
If the test is successful and the result is usable, the document can also be modified using an internally developed LotusScript program. This makes batch processing possible.
Note: From DocuWare 5.1b Service Pack 2 CONNECT to Notes ignores all documents with a $NoteHasNativeMIME field with the value "1" for security reasons and displays a corresponding error message.