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 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
When clicking on "Set Regarding" the CRM window pops up but freezes.
Steps taken to resolve:
-Cleanly uninstalled and reinstalled CRM Plugin
-Removed COM Add-in (As Admin, re-added)
-Full clean reinstall of Office 2016
I cannot for the life of me figure out what is going on, did a Office 365 update break this? Does anyone have a knowledge for helping me isolate what is going on?
I ran the Microsoft Support and Recovery Assistant for Office 365, it did not pull up anything in regards to the plugin.
Any and all help would be appreciated.
This error started today Event ID 17204 - MSCRMTracing
CrmTrace encountered an error. Additional Info:Error in LoadDeploymentSettings [Cannot open database "MSCRM_CONFIG" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.], Stack Trace : at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
Outlook just updated to this:Monthly (targeted) 1906
June 27, 2019
If you try to set regarding in the web client, would it work or not?
What is your COM Add-in version? I mean the exact version number, you can find it in the Control Panel -> Programs -> Program and Features.
One more thing I would suggest is to clean your IE cache, and try it again.
You can enable trace on client and see what is going on.
After doing some more digging I ended up figuring out that everyone's outlook client that had an issue had updated the night before. I was able to resolve the problem by rolling back Office ProPlus versions. The errors in regards to the SQL DB within Dyn2013 I have our DB Admin looking into. Thank you all for the suggestions!
Have you found any other solutions to this one than rolling back the Office update? I have a similar problem too, but cannot roll back updates.
Business Applications communities