In some rare cases the WScript.Shell ActiveX component is not correctly registered. This causes, that the DocumentsCorePack "Print in Word" and TelephoneIntegration "Call Number" buttons are not working properly. To resolve the issue open a command prompt and enter regsvr32.exe wshom.ocx

We had the issue in the last months that some emails with a long text in it are taking ages till they were send. We are using the Email Router for sending and receiving email 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 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)

More...

Symptoms

Cause

More...

Contents:
Part One: Creating the Chart
Part Two: Creating the Drill-Down Click

Part One (Creating the Chart )
Pre required Steps:
Create the Fetch XML. To create a Custom Fetch it is advisable to use a fetch generator tool. If you have our DCP Add-on you will also find such tool. Otherwise you can use the Stunnware Tools for MSCRM.
More...

A detailed guide of how to find out the version number for each mscrm-addons product:

More...

Location of the Language Settings on the Client & Server

The name of the Language XML File is: <TwoLetterISOLanguageCode>.XML

For a list of two letter iso codes see http://www.worldatlas.com/aatlas/ctycodes.htm, Column A2

The language files are usually located in the sub folder localization of the products installation folder, typically under “C:\Program Files\PTM EDV Systeme GmbH\[ProductName] for MS CRM 4.0\Localization” or in the subfolder App_Data, similar to  “C:\Program Files\PTM EDV Systeme GmbH\[ProductName] for MS CRM 4.0\App_Data\Localization”

The language file for the english UI is for example en.xml

More...

Outlook 2010 is having some severe Problems with Ajax based functions. Being a reported error with Microsoft there is still no fix available, but only a workaroud:

The impacted product cannot be started inside Outlook, but needs to be launched as a seperate IE window.

You need to copy the ostarter.html into the root folder of the products serverside installation and adapt the sitemap as following:

Example GorupCalendar:

Per default the sitemap is not having seperate entries for WebClient and Outlookclient, so you need to replace the existing SubArea (ID : nav_GroupCalendar) with these two new entries:

<SubArea Id="nav_GroupCalendar" Url="/GroupCalendar/starter.aspx" Icon="/GroupCalendar/App_Themes/_imgs/18_calendar.gif" AvailableOffline="false" Client="Web" PassParams="1">
  <Titles>
    <Title LCID="1031" Title="GroupCalendar" />
    <Title LCID="1033" Title="GroupCalendar" />
  </Titles>
  <Privilege Entity="activitypointer" Privilege="Read" />
</SubArea>

<SubArea Id="nav_GroupCalendarOutlook" Url="/../GroupCalendar/ostarter.html?page=starter.aspx" Icon="/GroupCalendar/App_Themes/_imgs/18_calendar.gif" AvailableOffline="false" Client="Outlook" PassParams="1">
  <Titles>
    <Title LCID="1031" Title="GroupCalendar " />
    <Title LCID="1033" Title="GroupCalendar" />
  </Titles>
  <Privilege Entity="activitypointer" Privilege="Read" />
</SubArea>

After reinporting and publishing the sitemap the problem should be solved

1. Verify that the values under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders use valid drive letters.
2. If there are invalid drive letters, change them to point to valid drives
3. Try to install the software and check if that helps.

· Open your CRM
· Go to "Settings" in the navigation at the left
· Choose "mscrm-addons settings" from the navigation

More...

CTI does need the server component in a hosted environment as well, but you can launch the CTI Server setup from any Client, as long as you have a user with full access to the CRM. (You need to select the Hosted options on the connection dialog, for details see the product manual)

If you have physical access to the crm server you can just launch the setup on that server as if it were an onPremise installation.

Due to the mechanics of an IFD setup, the client will not use a SQL connection to retrieve the information but a webservice call

As webservice calls are more limited as SQL queries, its is recommended to create a hidden field in CRM on the entities you want to search in that will hold the numbers in a format similar to the one TAPI uses.

You can achieve this either via an onSave script or via a workflow in CRM, transmuting the number to a tapi compatible format. This is only required for caller identification, outbound calls will work with the formatted number, as they are processed by the client application.

Explanation:

The number stored in CRM is formatted canonical, looking like +43 (316) 680880 0

The TAPI drivers delivers a number as 00433166808800.

Though the information is the same, the formatting prevents the CTI to find the number, as the webservice call is not able to resolve the formatting.

If you have a field in the CRM entity that is getting filled with the unformatted number, you can setup the CTI to use that field for the lookup and get correct results in looking up the callers, but still have a well formatted number in the CRM to display.