I am using 6.0.2 CF1 and processing thousands of Lotus Notes Documents through an XSL Transformer. Most of the time it works great but there are occasional documents where the transformer fails.
I decided to start at the root and simply conver those documents to straight DXL. When I open them up in an XML Editor, they fail validation because of an unclosed tag in the rich text field. It is either or or tag which is not closed properly, but it is not consistent between documents. If I open the document and resave it in my 6.02 client, and export it again, the DXL is fine.
Our environment is currently mixed and has been mostly R5. Is it probably that the R5 client is doing something wrong in the actual rich text field and that is causing the problem for the DXL output? Any known issues on this?
Subject: DXL / XML issue with rich text fields <bug ?>
Hi Terry
Something new about this problem ?
I’m facing the same one, trying to export documents with richtext fields, it works for some and for others I only get a this error in the dxlexporter log :
Subject: RE: DXL / XML issue with rich text fields <bug ?>
I’ve received “invalid arguments” errors using NotesDXLExporter process methods (in 6.5.4) as a result of some images in the body of memos I am exporting. I’ve found this to be odd, since I have been unable to find any corruption in the image causing the problem, but for some reason, when the messages were generated by a particular user, and they had a particular embedded image from their hard drive, the export would fail. Other users using the same embedded image would have no problems. The implication is that there is some corruption in the memo/embedded image (in the rich text Body field) that is causing the process to fail. Copying the message or even only the image from the failed entry, and processing a new memo with that copy also failed. Yet the same source image from my system or others have no issues and are processed by the exporter without errors. Notes Client releases are the same. So there has to be something about the problem user’s source file that is slightly different when added to the memo, even though there are no other signs to suggest that there is any related corruption with that image.