Annotated diagnostics for Single Inbox
This document contains annotated diagnostic files with the CsMbxSync macro diagnostic turned on.  All diagnostic lines for a particular action are included. In other words, none of the output caused by the action has been skipped over.  The contents of diag file are in courier font, annotations are in Arial, following the diagnostic file entry which they descibe.  

New Message Arrival on Connection

14:18:22.826 |7545,,,CsMbxSync,15,CCsMsCnxMailEventProvider::dispatching event: 2, msg id 
{a8380b99-2172-43f8-a12a-6c000071849a}, fld id {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, mbx id 
{c064974a-757d-4bda-879c-1a5ae4d9d6df}

For any diagnostic line, the first entry is the local time that the entry was made.  7545 is the thread number of thread that made the log entry.  CsMbxSync identifies the name of micro trace set to which this diagnostic belongs, 15 is the number of the micro trace, and the remainder of the line is contains diagnostic details. 

This is the first diagnostic that will indicate that a message change has occured on the Connection side. From this line, we see that an event of type 2 (new message) has been received by the syncer from connection for the message with Connection DB message id a8380b99-2172-43f8-a12a-6c000071849a, for folder id a16e1827-6d8a-418e-8e95-6b2b00381c4a,  and mailbox id c064974a-757d-4bda-879c-1a5ae4d9d6df.  These guids are the object ids of the rows in the connection database that represent this message.

14:18:22.826 |7545,,,CsMbxSync,15,CCsMsCnxMbx::DispatchEvent() Received msg notification for Cnx Msg Id: (Cnx Mbx Id: 
Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Msg Uid: {a8380b99-2172-43f8-a12a-6c000071849a})

This line indicates that the event has been dispatched to a particular mailbox.  Meaning that this is a mailbox that the syncer is actively syncing, and it has queued work for a worker thread to update the mailbox.

14:18:22.827 |7555,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() 
Beginning Sync For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, 
Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, 
Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, 
Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, 
Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, 
Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), 
Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, 
Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, 
SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

This diagnostic is the indication that a worker thread 7555, has picked up the queued work. The next part of the diagnostic 10.93.236.152, is known as the group id.  The group id is used to limit the number of threads that will hit a particular server simultaneously. In this case it is an IP address, but it can also be an FQDN depending on the configuration.  Following that is the subscriber oid (c4f2f0a5-15c7-4df4-bd15-e115b81ae74f) for the subscriber whose mailbox is being synced.  All worker threads will include this for the subscriber that they are operating on.  This makes it easier to figure out a particular thread of log entries for a given subscriber on a busy system.

The first diagnostic for a particular work item (in this case, the notification that the subscriber has a new a new message) will describe the work to be performed ("Beginning Sync For Mailbox",) and will list all of the data that the syncer keeps for that subscriber as Srvc Entry Data.  This data matches the data entered in the CUCA for the users External Service and Unified Messaging Account.  

The user's email address sibuser2@seacorp.ecsbu-lab-sea.cisco.com can be useful for determining which log entries correspond which diagnostic lines, once you've located this starting line for a given work item, you can get the user's subscriber OID, and search for the additional operations the worker thread performs for this user using that id.

14:18:23.469 |7555,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,15,CCsMsCnxMbx::GetQueuedMsgs() 
returning notification for msg Cnx Msg Id: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, 
Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
Msg Uid: {a8380b99-2172-43f8-a12a-6c000071849a})

This diagnostic indicates the list of messages that have been notified for the this connection mailbox.  In this case it is the single message that was notified above, though there can be multiple such lines if there are more messages with notifications that have not yet been acted upon. You can correlate this entry to the notification above via the Msg Uid a8380b99-2172-43f8-a12a-6c000071849a.

14:18:23.470 |7555,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,MAILBOX SYNCH  for mbx Cnx Mbx Id:
Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), syncing:  connection msg count 1, external msg count 0, 
connection hard delete count 0, external hard delete count 0, external outbox count 0

This diagnostic indicates that the syncer has finished gathering data from the Connection and Exchange side notification queues and lists the total count of messages that will be synchronized on this pass.

14:18:23.521 |7555,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,10,MAILBOX UPDATE - CREATE EXTERNAL 
MSG For mbx Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: 
{a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
msg MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com creating in external store, data 
Msg Data: (Sync Data: Msg Sync Data: (Is Read: 0, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), Priority: 0), 
Internet Msg Id: MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com, 
Internet Msg Id Hash: c2d9595a59047dd2a82f5d3290396504, Cnx Db Msg Id: {a8380b99-2172-43f8-a12a-6c000071849a}, 
Date: 22:18:21 11/15/10, Msg Type: 2, Sensitivity: 0, Is Secure: 0, Date Sent: 22:18:21 11/15/10, 
Date Received: 22:18:22 11/15/10, Is Read Recpt Req: 0, Is Delivery Recpt Req: 0)

Here, the syncer is indicating that it needs to create a message on the external (Exchange) side.  The update diagnostic will show the data the syncer uses for this message.  The Internet Msg Id is used by the syncer to correlate messages between Exchange and Connection.

14:18:23.748 |7555,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() Finished Sync
The final diagnostic indicates that the worker thread has finished this work item.

Shortly after the message has been created in exchange as a result of the syncer pushing the message, the syncer is notified by Exchange that the message has been created.  This is expected.

14:18:25.994 |7546,,,CsMbxSync,14,CCsMsExchMailEventProvider::DispatchEvent() message event received: 
subid 5efa4a3a-6b40-4ea4-9cf6-11493ace5534, exchmsgid AAMkAGIxZ ... DxvIm6xHdTR4n1osHeDELJAAAA0B6HAAA=, 
action created

14:18:25.994 |7546,,,CsMbxSync,14,CCsMsEwsMbxEventAdapter::DispatchEvent() called for Exch Msg Id: 
(Exchange Id: AAMkAGIxZ ... DxvIm6xHdTR4n1osHeDELJAAAA0B6HAAA=)

These diagnostics indicate that a message notification has arrived from Exchange.

14:18:25.995 |7554,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() 
Beginning Sync For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, 
Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, 
Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, 
Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, 
Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, 
Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), 
Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, Subscriber Oid: 
{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

Similar to the Connection side notification, this diagnostic indicates that a worker thread has picked up the work item created by the notification.

14:18:26.157 |7554,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,14,CCsMsEwsMbxEventAdapter::GetNotifiedMessages()
adding msg Msg Data: (Sync Data: Msg Sync Data: (Is Read: 0, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), Priority: 0), 
Internet Msg Id: MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com, 
Internet Msg Id Hash: c2d9595a59047dd2a82f5d3290396504, Cnx Db Msg Id: {a8380b99-2172-43f8-a12a-6c000071849a}, 
Date: 06:15:13 11/16/10, Msg Type: 2, Sensitivity: 0, Is Secure: 0, Date Sent: 06:18:21 11/16/10, 
Date Received: 00:00:00 01/00/00, Is Read Recpt Req: 0, Is Delivery Recpt Req: 0)

14:18:26.202 |7554,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,MAILBOX SYNCH  for mbx Cnx Mbx Id: 
(Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), syncing:  connection msg count 0, external msg count 1, 
connection hard delete count 0, external hard delete count 0, external outbox count 0

14:18:26.225 |7554,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,10,MAILBOX UPDATE - UPDATE CACHE 
For mbx Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
msg MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com messages are identical, but no cached exchange state, 
updating connnection cache, data Msg Sync Data: (Is Read: 0, Is Deleted: 0, Subject: 
CCsMsSubjectData: (m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), 
Priority: 0)

In this case the syncer sees that the message data for Connection and Exchange are identical, but that there is not yet any cached data for the last known Exchange state, due to the fact that this message has just been created.  The syncer updates the message cache with the Exchange side data, so it can be used to determine how a message has changed when further notifications are received for this message.

14:18:26.248 |7554,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() Finished Sync

The worker thread reports that it is done with this work item.

Message marked Read on Connection
The following is the set of diagnostic messages that will be associated with an update of a message.  In this case, the message has been marked read on connection via the TUI.

14:31:37.872 |7545,,,CsMbxSync,15,CCsMsCnxMailEventProvider::dispatching event: 3, 
msg id {a8380b99-2172-43f8-a12a-6c000071849a}, fld id {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
mbx id {c064974a-757d-4bda-879c-1a5ae4d9d6df}

This diagnostic is similar to the new message notification above with the exception that event 3 here indicates that a msg read notification from connection.

14:31:37.872 |7545,,,CsMbxSync,15,CCsMsCnxMbx::DispatchEvent() Received msg notification for Cnx Msg Id: 
(Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: 
{a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
Msg Uid: {a8380b99-2172-43f8-a12a-6c000071849a})

14:31:37.873 |7561,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() 
Beginning Sync For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: 
(Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Srvc Data: External Srvc Data: 
(Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, Auth Scheme: 2, Is Enabled: 1, 
Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, Security Transport Type: 1, 
Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, Service Type: 4, 
Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, 
Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), 
Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, 
Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, 
SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

14:31:37.992 |7561,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,15,CCsMsCnxMbx::GetQueuedMsgs() 
returning notification for msg Cnx Msg Id: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, 
Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
Msg Uid: {a8380b99-2172-43f8-a12a-6c000071849a})

14:31:37.992 |7561,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,MAILBOX SYNCH  for mbx 
Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, 
Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), syncing:  connection msg count 1, external msg count 0, 
connection hard delete count 0, external hard delete count 0, external outbox count 0

The preceding lines essentially match the new message notification from Connection.  See above for a more detailed explanation.

14:31:38.030 |7561,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,10,MAILBOX UPDATE - UPDATE MSGS 
For mbx Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, 
Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), 
msg MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com - messages are different, updating messages - 
old cnx data Msg Sync Data: (Is Read: 1, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), Priority: 0), 
old cnx cache data Msg Sync Data: (Is Read: 0, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: , m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), Priority: 0), 
old external data Msg Sync Data: (Is Read: 0, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), 
Priority: 0), new data Msg Sync Data: (Is Read: 1, Is Deleted: 0, Subject: CCsMsSubjectData: 
(m_strSubject: Message from Sib User1 (2142), m_strSubjectHash: 112cc58dba78c9eccff8154794f965b1), 
Priority: 0)

For an updated message, the diagnostic will show the old cnx data, the old cnx cached data, and the old external data for the message, as well as the new data for the message that it pushes to both sides and the connection cache.  Here, the connection state before syncing contains "Read: 1", while the cached and external data contain "Read: 0".  The syncer concludes that this represents a change on the connection side for Read: 0 to Read: 1, and pushes new data with Read: 1 to the connection db, the cache, and the external server (Exchange)

14:31:38.126 |7561,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::ClientWork() Finished Sync

As with the new message example, this line indicates that the worker thread is finished with the message.

Pressing the Reset Button for a Subscriber
The following is the set of diagnostic traces that occur after an administrator presses the reset button for a subscriber.  The button forces the user to be recreated, to resubscribe for Exchange and Connection message notifications, and to synchronize all messages in the subscribers mailbox.

17:58:07.234 |7552,,,CsMbxSync,20,Processing Reset request for Subscriber Oid {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}

This diagnostic shows the syncer picking up the request to reset the subscriber.  This diagnostic is created by the Directory update thread.

17:58:07.243 |7552,,,CsMbxSync,20,Removed {8cec28d5-62ae-40d1-9802-14f471fc4986} from Sesm Entry Map as a result of subscriber reset request
17:58:07.243 |7552,,,CsMbxSync,20,Adding {8cec28d5-62ae-40d1-9802-14f471fc4986} to Sesm Entry updates as a result of subscriber update/reset request

Here, the Sesm entry (which is identified by the row id of the tbl_SubscriberExternalServiceMap from the connection database) is removed from the map of currently synchronizing mailboxes, then readded.  These are also made on the directory update thread.

17:58:07.243 |7573,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Kill() Beginning Kill For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

This is the indication from the worker thread that the Kill work item has been picked up.  The data that the syncer has is logged out as as with a notification request described above.

17:58:07.243 |7552,,,CsMbxSync,20,Processing updates for 1 SESM entries

This diagnostic indicates we are back on the Directory update thread, and indicates the total number of updates the thread is currently processing, currently 1.

17:58:07.243 |7552,,,CsMbxSync,20,Processing update for SESM entry {8cec28d5-62ae-40d1-9802-14f471fc4986}

This diag indicates the SESM table row that is currently being processed.  There can be more than one of these if there are multiple updates.

17:58:07.255 |7573,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,15,CCsMsCnxMailEventProvider::UnRegister() Unregistering subscription for mbx id {c064974a-757d-4bda-879c-1a5ae4d9d6df}

More diagnostics from the worker thread indicating that it is Unregistering the mailbox from Connection notifications.  (Note that the unregistration process for exchange notifications, which is carried out along with the Connection notification unregstration will only be logged if there is an error.)

17:58:07.255 |7573,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Kill() Finished Kill

This line indicates that the worker thread is finished removing the mailbox from the sync.

17:58:07.274 |7552,,,CsMbxSync,19,CCsMsRetryQueue::RemoveRetry() retry for SESM oid {8cec28d5-62ae-40d1-9802-14f471fc4986} not found

Here the directory update thread is indicating that there are no pending retries for this user.

17:58:07.274 |7552,,,CsMbxSync,20,Created Service Entry Handler with retry count 0 for Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

This diagnostic indicates the directory update thread load the users mailbox for sync, and lists the data it has pulled from the connection database for the user.

17:58:07.274 |7552,,,CsMbxSync,20,DB thread done processing requests. 1 Adds/Resets, 0 Update Checks, 0 Resyncs, 0 Skipped Resyncs, 1 Removed

The indication that the directory update thread is done processing it's notifications.

17:58:07.330 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Init() Beginning Init For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

A worker thread has picked up the work for synchronizing the mailbox.  In this case it is a different worker thread than handled removing the old data from the set of syncing mailboxes.

17:58:07.702 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,13,CCsMsEwsPushMailEventProvider::Register() Registered SESM OID {8cec28d5-62ae-40d1-9802-14f471fc4986} to subscription id {5fe5baba-4983-43ed-885e-95cc9c0237b7}

This diag is the indication that the worker thread has successfully registered the mailbox for exchange notifications.

17:58:07.834 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,15,CCsMsCnxMailEventProvider::Register() Registering subscription for mbx id {c064974a-757d-4bda-879c-1a5ae4d9d6df}

This diag indicates successful registration for Connection notifications.

17:58:07.834 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Init() Finished Init

Diagnostic that shows the init task is finished.  After the Init, a Resync task will be performed.

17:58:07.835 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Resync() Beginning Resync For Mailbox Srvc Entry Data: (Cnx Mbx Id: Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), Srvc Data: External Srvc Data: (Ext Srvc Oid: {6ddb2c1a-6c3e-42cb-9994-97739ce1c3ab}, Display Name: Ex 2010, Auth Scheme: 2, Is Enabled: 1, Srvc Supports Sync: 1 , Exch Do Auto Discover: 0, Exch Do Auto Discover 2003: 0, Security Transport Type: 1, Server: 10.93.236.152, Service Account: seacorp\jamilkssrvc, Service Password: XXXXXXXXX, Service Type: 4, Exch Service Type: 1, Trust Cert Dir: /usr/local/platform/.security/tomcat/trust-certs/, Ldap Security Transport Type: 0, Ldap Validate Server Certificate: 0, Validate Server Certificate: 0), Mbx Data: Mbx Data: (Email Addr: sibuser2@seacorp.ecsbu-lab-sea.cisco.com, Subscriber Oid: {c4f2f0a5-15c7-4df4-bd15-e115b81ae74f}, Sync Enabled: 1, SESM Oid: {8cec28d5-62ae-40d1-9802-14f471fc4986}))

The worker thread is now performing a resync for the mailbox.  Resync means that every message in the mailbox will be looked at and synced.

17:58:07.988 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,MAILBOX SYNCH  for mbx Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), syncing:  connection msg count 1, external msg count 1, connection hard delete count 0, external hard delete count 0, external outbox count 0

The syncer has queried both sides for the list of voice messages.  In this case there is one message on each side to be synchronized.

17:58:07.988 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,MAILBOX SYNCH For mbx Cnx Mbx Id: (Mbx Uid: {c064974a-757d-4bda-879c-1a5ae4d9d6df}, Inbox Folder Uid: {a16e1827-6d8a-418e-8e95-6b2b00381c4a}, Mail Store: UnityMbxDb1, Inbox Folder Name: inbox), msg MAL.a24c5f64-0357-48e9-82ab-63dc83544@cuc-install-31.cisco.com messages are identical, skipping update

In this case there is just on message that is already syncronized, but there can be many MAILBOX SYNCH and MAILBOX UPDATE diagnostics for a given resync operation.

17:58:07.988 |7574,10.93.236.152,{c4f2f0a5-15c7-4df4-bd15-e115b81ae74f},CsMbxSync,11,CCsMsMbxLink::Resync() Finished Resync

The worker thread has indicated that it is done with the resync operation.