I have a user getting an odd popup when they try to open existing To Do notes.
The popup says nothing more than ‘#3A:F2’. No information or anything.
The user cannot open the To Do in order to mark it complete or change any details.
I have tried rebuilding the index and views, I have run compact and fixup. The popup still keeps coming back.
Subject: Weird Pop Ups Under To Dos
Please review:Lotus Software Knowledge Base Document
Title: Error #3A:F2 received when opening e-mail and Calendar entries
Doc #: 1258359
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21258359
Here are some other things to try:
-
Run updall -R against that view. Run fixup against that database (it might delete that To Do if that To Do is corrupted).
-
Create a new replica of that mail database. Does the problem still occur?
-
Create a new copy of that mail database. Does the problem still occur?
-
Cut that To Do and paste it back in the view. Can you open it without receiving the error?
-
Cut that To Do and paste it in a database created from the blank template. Update that view, ctrl/shift/F9. Update the original To Do view as well or run updall -R against that view. Paste that To Do back in the view. Can you open it without receiving the error?
Subject: I have seen this with mixed MIME_PART and COMPOSITE body elements
I expect that your developer has added a MIME_PART field named ‘body’ to a message that already has a body element of type Composite. I have in fact had the same problem today, banging my head in frustration at Domino. There is an amazing lack of documentation on MIME in all releases prior to v8.0 (C API) but I finally tracked this strong hint:
SPR# OBRD58CLBT - This fix prevents messages with mixed “Body” item data types from causing a FETCH 3A:F2 error in IMAP, which made subsequent messages unretrievable. This issue was seen when an application was causing messages to have both TYPE_TEXT and TYPE_MIME_PART body items.
I would dearly love someone knowledgeable with Domino internals to explain how to create a robust MIME_PART additional body field (think: Disclaimer) using the pre-8.0 C API, viz an existing Body element that is Composite.
Regards,
Ken Gartner
Subject: Response from IBM
I recieved a response from IBM on this issue after raising a PMR.
‘No intention to fix ever’
lovely.