Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have a successfully fully functioning CRM 2013 installation using server side sync with Outlook on Office 365. What I have been noticing since we've set this up months ago is that on an almost daily basis, one of our admins needs to go in to CRM->Settings->Email Configuration->Active Mailboxes view and select all mailboxes and then click on Test & Enable. For some reason we have multiple mailboxes (usually all of them) that reset the "Enabled for Incoming Mail" column to No. We are always receiving the mailbox warnings/alerts when we log in to CRM but the logs are inconclusive.
Is anyone else experiencing the same issue? If so, is there a way to automate this?
We are having the same issue. Have you been able to find a fix for this?
What we have done doing temporarily is checking the bit on the database level every 15 minutes and if it is 0, we flip it to 1. While this works, it isn't the best solution.
No, no response and nothing on the web I can find for it. Please let me know if you find anything.
Seeing the same problem here - Every day!! We use CRM Online so don't have the option of updating the database field - anyone get any resolution?
I've had a lot of trouble with this over the past few months and have some successful calls with Microsoft to bring us back into line with expectations of using Server Side Sync.
First and foremost, for all configurations listed here I'd recommend people raise a support ticket with Microsoft. There are a number of defined "hard errors" which can cause the synchronisation to actively disable itself as the system's expectations are different to the reality.
In your case specifically bjvista, at the time you were using CRM 2013 - does this imply that you are on-premise? Or did you schedule the 2015 update for later than January?
If you're on-premise, this configuration is unsupported by Microsoft (see link: https://technet.microsoft.com/en-us/library/dn531050.aspx), however, if you're online this is good news as Microsoft should be able to narrow down what type of "hard error" is stopping the synchronisation.
Hope that helps!
Business Applications communities