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.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
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
I am experiencing a problem in my on-premises CRM 2011 deployment , every two days or so all the outlook clients stop connecting but the server works normally over web .
What do you advise me to do ?
Do you have IFD enabled on the server ? If so did you use internal or exterl url to configure outlook client?
No we don't have an IFD . And we are using the internal ip address for the crm outlook 2011
When you say stops working after 2 days , is it throwing error or crm add-on gets disabled after 2 days?
it is not always 2 days and it is not throwing any error . All the users on outlook client get signed out , even if they press sign in they can't get in the CRM . On the other side if they access the server via the web interface everything works normally .
It is really weird I thought that the outlook clients fetches everything like a web browser.
You said you are using CRM server IP address for configuring.. this is going via NTLM authentication. Configure outlook clients with the URL or the CRM server name and make sure you can access CRM using browser with no prompts for credentials. This way it will go via windows authentication/Kerberos
Are we still having issues after configuring Outlook client with CRM server name and not IP address ?
Also ensure that the time on the client machine and CRM server are in synch.
I resolved this issue by limiting the sql's memory use . Turns out the rams where full and the server couldn't run more processes.
Business Applications communities