Server-side synchronization: Mailbox keeps getting disabled

(0) Share

Report

Posted on by MarekOcenas

Hello everyone,

I have encountered a problem with CRM mailboxes getting constantly disabled without any error message I could find.
In our company we use CRM 2016 on-premises and have set up server-side synchronization with Exchange. For most users everything runs just fine but a few mailboxes keeps getting disabled just after enabling them.

Whenever I click "Test and Enable mailbox" button, the test proceeds and 3 informative alerts are generated (success of incoming, outgoing e-mails and ATC), bunch of e-mails are saved to CRM but then synchronization stops working. When I click "Test and Enable mailbox" button again, some new e-mails are saved, assuming there are any new in Exchange and again synchronization stops.
I have found out that every time PostponeMailboxProcessingUntil attribute of Mailbox record is set to 9999-12-31 unlike other working mailboxes which are set to next synchronization time a few minutes after last one. Apart

from this, no other setting is changed on the mailbox record and no errors or alerts for that mailbox are

generated.
Can you please help me to find out what could be the reason why the mailbox gets disabled?

Thanks,
Marek

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Zohaib Uddin Khan 2,822 on at

Like (0)

Report

Hi,

Kindly go through Troubleshooting and monitoring server-side synchronization and verify it for the single mailbox which is getting disabled repeatedly.

thanks.

Was this reply helpful? Yes No
MarekOcenas on at

Like (0)

Report

Hello,

thanks for suggestion, I tried using The Server-Side Synchronization Performance dashboard once more and find any mailbox related messages, but I found none in CRM. No mailbox having issues is displayed in the dashboard.

The problem is, according to CRM application the mailbox is not shown as disabled, yet still does not proces emails. Only value I found is PostponeMailboxProcessingUntil which is being constantly set to 9999-12-31 after first email synchronization.

Unfortunately I did not find any clues abount postponing mailbox processing.

Marek

Was this reply helpful? Yes No
Paul Reitmeyer xRM 40 on at

Like (0)

Report

Marek,

Did you ever make progress on this? I have a similar situation I've encountered and even updating the postponemailboxprocessinguntil value to be GETUTCDATE() only provides a temporary fix. Please let me know,

-Paul

Was this reply helpful? Yes No
MarekOcenas on at

Like (0)

Report

Hello Paul,

No, unfortunately, I have not.

After some time (and probably some updates via Windows update) all mailboxes suddenly start working properly. But I have never found out what was the original problem.

Marek

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello everyone,

Does someone made progress on this?

I have an user with the same problem:

Mailbox Async Processing State
mailboxid : f4591fb6-873a-e511-80df-005056ae4b6d
hostid: Null
processingstatecode : 0
processinglastattemptedon : 13/02/2017 14:46:05

Mailbox Synchronization Methods (2 is server-side sync or email router, 1 is Outlook sync, 0 is none)
incomingemaildeliverymethod : EmailRouter
outgoingemaildeliverymethod : EmailRouter
actdeliverymethod : OutlookClient

Mailbox Enabled State
enabledforincomingemail : True
enabledforoutgoingemail : True
enabledforact : True

Mailbox Idle State (shows how many times the mailbox was processed with no email items or Appointments, Contacts and Tasks to synchronize)
noemailcount : 0
noactcount : 0

Mailbox Backoff Parameters (shows when the mailbox is scheduled to process next time)
postponemailboxprocessinguntil : 31/12/9999 23:59:59
postponesendinguntil : 13/02/2017 14:46:05
receivingpostponeduntil : 13/02/2017 14:51:08
receivingpostponeduntilforact : 13/02/2017 14:36:24

Mailbox Test and Enable Parameters
testemailconfigurationscheduled : False
testemailconfigurationretrycount : 0
testmailboxaccesscompletedon : 13/02/2017 14:46:06
postponetestemailconfigurationuntil : 13/02/2017 14:51:06

Mailbox Last Sync Cycle Information
lastsuccessfulsynccompletedon : 13/02/2017 14:46:08
lastsyncerror : T:120
>Exception : Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: subscriptionclients with clientid edb84472-30c0-e511-80c7-005056ae80bd doesn't existDetail: <OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts"> <ErrorCode>-2147204845</ErrorCode> <ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>subscriptionclients with clientid edb84472-30c0-e511-80c7-005056ae80bd doesn't exist</Message> <Timestamp>2016-08-01T12:14:49.5791916Z</Timestamp> <InnerFault> <ErrorCode>-2147204845</ErrorCode> <ErrorDetails xmlns:d3p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>subscriptionclients with clientid edb84472-30c0-e511-80c7-005056ae80bd doesn't exist</Message> <Timestamp>2016-08-...
lastsyncerrorcode : 121
lastsyncerrorcount : 8
lastsyncerroroccurredon : 01/08/2016 12:14:49
lastsyncerrormachinename : MNTCPSMSRV135
itemsprocessedforlastsync : 45
itemsfailedforlastsync : 0

Was this reply helpful? Yes No
Suggested answer

PS 23,577 on at

Like (0)

Report

Try the solution suggested by Rob in the following post

community.dynamics.com/.../115946

Was this reply helpful? Yes No
Suggested answer

Paul Reitmeyer xRM 40 on at

Like (0)

Report

Yes, we were able to get a resolution on this issue. It involved first updating to CRM 2016 SP1 and then on the mailboxes affected with this issue you set the mailbox settings to use Microsoft Outlook Client for everything, then Test & Enable, then set them to Server Side Synch and Test & Enable again. Might have to do it two or three times before it fixes, but that resolved our 60 or so mailboxes that weren't working.

Was this reply helpful? Yes No