OM 3433 and OM.UI 2203 plus "Failed to display the mess

[deyjvu]

With the SWA these two errors and "Failed to display the messages for folder INBOX" are occurring on many users mailboxes. Some of these users use both Outlook and the SWA.

I've found suggestions to clear the imap-cache but that didn't resolve these users problems in the SWA. However, the fix didn't indicate if you needed to restart any of the processes like scalix-tomcat for this to work effectively. Could only test without it being restarted and that did not fix the issue.

Another suggestion was to run an 'omscan -AvxU "user name" ' and for some this worked.

Another suggestion is to use sxmboxexp of the Inbox (including folders if appropriate) then omtidyu the inbox to remove all messages, sxmboximp (make sure all subfolders are deleted or they will be duplicated).

Could be a fix for this issue as these users have large numbers of messages in their inboxes, I'll test and update this if it does.

However, in the error messages:

ERROR IMAP Server Da(IMAP Server Pr) 04.01.08 08:11:28
[OM 3433] The open container reference provided is invalid.
File Name: /var/opt/scalix/wx/s/data/0000009/00f0um2
User Name: Mr UserWC / scalix/CN=Mr UserWC
Current errno value: 9
Last Msg Id: 006501c825c3(036)cd97b0a0(036)73c7c7c7(a)WHPL.LOCAL
Last Msg DirectRef: 000ee5c3b85de724
-> msl_load272
-> msl_getObjectFile
-> ct_OpenCtner
-> im_OpenItem
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
-> sfl_OpenSfl
-> im_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- /build/11.3.0/src/lib/ombase/os/os_open.c:120[1,2]
<- /build/11.3.0/src/lib/ombase/sfl/sfl_base.c:369[1,2]
<- /build/11.3.0/src/lib/ct/ct_open.c:882[1,2]
-> ct_CloseCtner 25880
<- /build/11.3.0/src/lib/ct/ct_octner.c:64[3,3433]


ERROR IMAP Server Da(IMAP Server Pr) 04.01.08 08:11:28
[OM.UI 2203] MSL problem - item MIME structure not produced - see error log
File Name: /var/opt/scalix/wx/s/data/0000009/00f0um2
User Name: Mr UserWC / scalix/CN=Mr UserWC
Current errno value: 9
Last Msg Id: 006501c825c3(036)cd97b0a0(036)73c7c7c7(a)WHPL.LOCAL
Last Msg DirectRef: 000ee5c3b85de724
-> ct_OpenCtner
-> im_OpenItem
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
-> sfl_OpenSfl
-> im_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- /build/11.3.0/src/lib/ombase/os/os_open.c:120[1,2]
<- /build/11.3.0/src/lib/ombase/sfl/sfl_base.c:369[1,2]
<- /build/11.3.0/src/lib/ct/ct_open.c:882[1,2]
-> ct_CloseCtner 25880
<- /build/11.3.0/src/lib/ct/ct_octner.c:64[3,3433]
<- msl_readContainerOpenedParent
<- /build/11.3.0/src/bin/imap41/imap41_mime.c:166[101,2203]

If I do an omdref on the message direct ref in these errors it indicates what the subject is of the message indicated here as 000ee5c3b85de724. The question is, is this the problem message or possibly the message just before the problem message. What does the "Last Msg DirectRef" refer to as in what is meant by the "Last Msg", the last one opened or the one trying to be opened when the problem occurs?

If we can find this information then it maybe possible to track down what message is causing these errors and not require a full sxmboxexp/imp?

[deyjvu]

Looks like I jumped to a wrong conclusion as initially the users with the "failed to display the messages in the Inbox folder" were also see the OM 3433 and UI 2203 errors but now I have one user who only has the "Failed to display..." error message on the client and no OM errors in the fatal file for that user.

We have now found that doing:

1. Getting users to logoff and stay off
2. Doing omscan -AvxU
3. Deleting the files in the imap-cache for each user.

This has stopped the "failed to display the messages in the Inbox Folder" and the OM 3433 UI 2203 errors for those users as well as the user who was only getting the error on the client.

Possibly why the fix didn't work initially was that the users may not have stayed out of their accounts whilst the omscan was trying to run. This time it was ensured that users did not access their account and the problem was resolved.