CRM 2013

CRM 2013 Outlook Performance After installing the Microsoft CRM 2013  and client, you may notice that the connection over the internet is slow and not as desired. One likely reason for this is that WCF communication is not compressed, and the outlook client is using that to talk to the CRM server. Assuming that your current environment is configured correctly with Windows 2012 R2 and IFD, then you can simply update the server to support WCF compression and improve performance for CRM 2013 and outlook. Enable compression by manually updating the ApplicationHost.Config 1. On the CRM Server Navigate to: C:\Windows\System32\Inetsrv\Config\applicationHost.config and open it with notepad. 2. Search for the Section: “<dynamicTypes>” and in that section you should fine an entry that looks like this:  <add mimeType=”application/x-javascript” enabled=”true” />  3.  Below that, add the following line:  <add mimeType=”application/soap+xml; charset=utf-8″ enabled=”true” />  4. Save the file and reset IIS for the setting to take effect.

CRM 2013 has an annoying CRM 2013 Welcome Popup (First Things First) Not exactly sure why they did not predict the need to turn of this popup Organisation by organisation, however the solution is to just turn it off for good. The Solution On the CRM server, run “Regedit.exe” as an administrator. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRMAdd  and right click to new 32 Bit DWord   Name the new Dword: DisableNavTour Set the Data Value to 1 Restart IIS That’s it, your CRM server should never show the Popup again.

When browsing to your CRM server: /adfs/services/trust/mex  you receive an 503 Error. In our case this was to “https://sts1.iwebscrm.com/adfs/services/trust/mex” and we received the 503 Error. This became evident as we were testing the importing and upgrading of custom JS scripts from CRM 4.0 and CRM 2011 to use the new SDK in CRM 2013 (also applicable to CRM 2015). When we used fiddler to look at why the test environment failed we noticed a call to the ADFS mex endpoint. Looking at the ADFS Logs for the server will show a 102 Error: There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service. Additional Data Exception details: System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:808. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your… Read More »adfs/services/trust/mex Returns 503 on CRM 2013 Windows 2012 IFD – MEX EndPoint Fix