Until now we have no installation routine for our Dashboards for MS CRM 2011. This is why this blog entry describes how to upgrade/install the Dashboards in a MS CRM 2011 environment manually.
Please note: This installation will only work in an on-premise installation and will not work in IFD and Claims-Based-Authentication-Mode.
Please note: This article applies to Group Calendar in MS Dynamics CRM 2011, 2013, 2015 and 2015/2016+++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++ Please note:This article applies to ActivityTools inMicrosoft Dynamics CRM 2011 and CRM 2013
(Click here for information on how to enable debugging in ActivityTools in higher CRM versions)
Please note:This article applies to TelephoneIntegration for MS CRM 2011, 2013 and 2015, as well as to CRM 2015/2016.
Basically there are two ways to activate debugging:
Solution 1: Activating debugging via the TI-Setup
Solution 2: Activating debugging on your Client via the Registry
If you receive the below error message, please make a repair install of Office. This should resolve the issue.
Read More »
If you upgrade from DocumentsCorePack (DCP) Server for MS CRM 2011 v5.5 to a higher version, you have to completely remove DocumentsCorePack Server for MS CRM 2011 from your CRM.
To successfully integrate our products with custom entities, these custom entites either have to be part of a managed solution or the navigation configuration has to be applied manually.
If you want to hide or block the toolbar in MS Word for non-DCP users on a terminalserver, please check the following steps:
1. You will have to create the following Reg key under current user instead of local machine:
HKLM\software\Microsoft\Office\Word\Addins\WordMailMerge.Connect (for example: HKCU\software\Microsoft\Office\Word\Addins\Wordmailmerge.connect)
3. Once you have created the reg key you can change the load behaviour for each user. Change it to
We once had the problem that some emails with a long text in it were taking ages till they were send. We are using the email router to send and receive emails to our support team.
As we moved some months ago from normal exchange to BPOS my first suggestion was that it has to do with the connection between BPOS and the Emailrouter. ( RU 14)
In the event-viewer I recognized the following entry:
#61042 - An error occurred while the outgoing email message with the subject Re: urgent problem with DCP config PTM CRM00114110 CRM: 0000132293' for ExchangeOnline: http://[servername]/PTMEDVSystemeGmbH for delivery through https://autodiscover-red002.mail.emea.microsoftonline.com/ews/Exchange.asmx The request failed with HTTP status 413: request entity too large, at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) bei Microsoft.Crm.Tools.Email.Providers.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.SendMessage(MessageType mailMessage) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.ProcessMessageInternal(email emailMessage)
Figure 1: Security Issue: WordMailmErge Add-On Error