mscrm-addons.com - Blog

News.mscrm-addons.com Blog

rss

Hello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts!


CTI does not resolve phone number

If the calling/called phone number is stored in Microsoft Dynamics CRM, then the number should be resolved to the corresponded CRM record. If the number does not resolve, make sure that the number is stored in the "MSCRM-ADDONS.com CTI CallInfos" entity. 


RecordCounter - Plugin Registration Error

If the error message Plugin registration error of PTM Plugins! appears after the installation of RecordCounter, it means that the plugin wasn’t updated successfully. To solve this problem, please follow the instructions of this article.


What to do if the TAPI wrapper is not working properly

CTI 2011 TAPI wrapper needs a TAPI driver that is suitable to your Phone PBX server.

Each PBX phone-system vendor has its own TAPI driver.

Our TAPI wrapper has not an active role on the TAPI lines, it is just a passive listener to random TAPI driver events and eventually, it triggers them in case of outgoing calls, accepting the incoming offers.


Calling out from a CRM Entity by pressing the [Call Number]-button triggers no reaction

If you outgoing calls are successful when made from CTI client, but not from the CRM entity, simply check the Internet Explorer Security Options. Please make sure that your CRM Server is included in the Trusted Sites Zone.


The Entity or PhoneCall activity does not open when a call is made

Before an entity or PhoneCall activity can be opened by an incoming/outgoing phone call, the phonenumber must be resolved.


What to do when the Lync / OCS wrapper does not support outgoing calls?

The CTI supports only one call at the moment.

However, when transferring existing calls to a third party, it can happen that some sessions are not correctly closed. You can compare that with a broken Lync conversation.


Repair WScript.Shell ActiveX

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

That’s it! 


Connection dialog retrieves organizations, but refuses to connect

Check the log textbox if the following statement is present (might be accomodated by a 401 exception).


Service Unavailable after error in upgrade process

Receiving a service unavailable response on a website usually indicates, that the application pool of the site is not running.

To solve this issue, open your InternetInformation Management and verify all required app pools are started.


How to enable debugging for DocumentsCorePack Client (CRM 2011)

++++++++++++++++++++++++++++++++++++++++++++++++++++
Please note:
This article applies to 
DocumentsCorePack CLIENT for MS Dynamics CRM 2011 ONLY
++++++++++++++++++++++++++++++++++++++++++++++++++++

This article describes 2 different possibilities to activate debugging for DocumentsCorePack.

Solution 1: Activating debugging on your client via the DocumentsCorePack settings or in the registry.

Solution 2: Activating debugging on your server/manually via the webconfig.