I recently had a customer report an issue that CRM e-mails were failing to send out of Microsoft CRM. We were able to isolate the issue down to an Exchange issue by using the “Test Access” button in the E-mail Router Configuration Manager. The Exchange Admin fixed the issue and then we were able to successfully “Test Access” and new e-mails were sending out of CRM successfully again. The outstanding problem was that there were 700+ e-mails that had went to a Failed status because they had reached the re-try limits to send e-mails out of Microsoft CRM. You could go into each e-mail individually and click “Send” and it would go back into a Pending Send status and the e-mail router would pick it up and send [...]
About Hasret SmajlovicThis author has not yet filled in any details.
So far Hasret Smajlovic has created 51 blog entries.
Have you tried to locate the Active Directory security groups that belong to your Dynamics CRM deployment only to find results like this? First off, why would you ever get results like this? Dynamics CRM 2011 installs 4 Active Directory Security Groups (PrivReportingGroup, SQLAccessGroup, ReportingGroup and PrivUserGroup) by default per deployment. Some people think this is per organization, but that is not correct. No matter how many organizations you have in a CRM deployment, you will only have 4 security groups per deployment in CRM 2011. So, you could have this many groups because you have several CRM deployments installed in this domain. CRM 4.0 also used similar AD security group names, so there may be some left over from old 4.0 deployments or even failed CRM server [...]
The Microsoft Dynamics CRM team has been testing the performance of Microsoft Dynamics CRM 2016 Service Pack 1 (SP1) (version 8.1) hosted on Microsoft Azure Virtual Machines. The goal is to establish a baseline for performance on CRM 2016 SP1, using Azure IaaS infrastructure with premium storage. The scenarios we have targeted involve thousands of users accessing their environment concurrently, every few minutes, with various workloads designed to simulate production environment. In this new baseline, we are testing performance against a SQL DB running on VM (Azure GS5 SKU). The detailed configuration, topology, optimizations, data profile, and test workload as well as lessons we learnt along the way on how to really get your Microsoft Dynamics CRM deployment tuned, will be published soon. The upcoming publication will also [...]
After the update of CRM2015 7.1.2 Did you notice your phone number fields with are now displaied as “”> prefixed?Hasret Smajlovic 2016-08-28T17:54:48+00:00
After the update of CRM2015 7.1.2 Did you notice your phone number fields with are now displaied as ""> prefixed?On a Dynamics CRM 2015 Online Organization if you are expering out-of-the-box phone numbers fields with ' ""> ' prefixed.(This label does not show up on the form edit window.)This is BUG done by Microsoft update 7.1.2 for CRM2015.To solve this go to costumization -> click on the filed that has ""> prefixed. go to details and edit. -> remove ""> from description. Save and publish the changes.This is really an strange one, but according to Microsoft, there is nothing they can do right now, maybe it will get fixed in the next release of updates. (This is however fixed in CRM2016)
I came across an issue with emails generated through workflows in Microsoft Dynamics CRM 2013. The status Pending Send was the trigger to have a look at the email activities. I noticed the message on top of the form “This message has not yet been submitted for delivery”, and I had no idea why. Until now.The problemIn the environment we successfully installed and tested the Email Router for CRM 2013. I had some custom workflows set up that created email messages to inform our users about important changes to their records. However, these messages never delivered. I assumed that the Email Router would process all email activities with status ‘Pending Send’, but it didn’t. The error message: “This message has not yet been submitted for delivery. For [...]