Unified Unity 4.0(3)SR1 with Lotus V5.12

[jocoates]

We are having a strange problem with our new installation of Unity Unified with Lotus. We can not access NEW messages via the phone. We can access new messages via the client with no problems. If we read the message in the client, we can go to "saved messages" on the phone we can listen to messages with no problem. The message we hear when trying to access new messages via the phone is "Sorry, you have no new receipts". TAC case is logged, but not having much luck there. SysCheck is fine, permissions fine, no errors in event viewer for applications etc etc etc. Anybody.... help..... please

[jocoates]

OK OK OK. The problem was the Lotus server was not set for Daylight Savings!!!! Lotus was 1 hour behind the Unity server.

It was trying to access voicemails that it thought were in the future. We set the time, restarted the Domino server and voila. It works.

Nice little gotcha. 3 days of effort. (Thanks Don in the TAC)

[kechambe]

For those who are wondering -- I used the Call Flow Diagnostics -> Conversation Flow Diagnostics macro trace to figure this one out.

Here is the snip of the traces:

//Here we are logging in and counting the number of messages and type of messages in the mailbox.

15:39:29:351 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Retrieving subscriber conv. props from DOH.

15:39:29:367 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Successfully retrieved subscriber conv. props from DOH.

15:39:29:368 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Counting subscriber messages in DOH.

15:39:29:414 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Subscriber has 2 InitialNewTotal messages

15:39:29:415 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Subscriber has new messages.

15:39:29:414 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Subscriber has 0 InitialNewUrgent messages

15:39:29:415 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Subscriber has 2 InitialOldTotal messages

15:39:29:601 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Succeeded counting subscriber messages.

15:39:29:602 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Sucessfully retrieved conv. props and counted messages.

//Here we are playing back messages.

15:39:35:632 (AvDiagnostics_MC,456,Subscriber Conversation,10) [Thread 2780] [Port 1] [Message sorting order = 0x00000000]

15:39:35:664 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message skipped. Arrived or modified last after message count.

15:39:35:665 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Messages last counted at: 2004-03-25 14:00:55

15:39:35:664 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message arrived at: 2004-03-25 14:34:17

15:39:35:665 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message last modified at: 2004-03-25 14:34:17

15:39:35:664 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Unity Current time at: 2004-03-25 15:39:35

15:39:35:665 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message skipped. Arrived or modified last after message count.

15:39:35:664 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Messages last counted at: 2004-03-25 14:00:55

15:39:35:665 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message arrived at: 2004-03-25 14:36:32

15:39:35:664 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Message last modified at: 2004-03-25 14:36:32

15:39:35:665 (AvDiagnostics_MC,457,Subscriber Conversation,10) [Thread 2780] [Port 1] Unity Current time at: 2004-03-25 15:39:35

As you can see -- Unity thinks that two of the messages arrived after we finished playing back the count. We skip playing back messages that arrive after the count to avoid user confusion. (Somebody might get confused if Unity tells them they have 2 new messages and then play back 3.) So Unity thinks that the last message was counted at 2004-03-25 14:00:55 however the time stamp on the line is 15:39:35:665. Odd right? Well a quick check of the source code revealed that the conversation gets the time from the Domino server, not from the OS. This explains why the clock being set wrong would impact the Unity conversation causing messages to be presented in message count portion of the conversation but not when it come to actually playing them back.

I think I am going to file a defect on this because we should be able to handle it a little nicer.

Anyway, back to whatever you were doing... :-)