So that you can „hide or block“ the toolbar in Word for none 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

2. HKLM\software\Microsoft\Office\Word\Addins\WordMailMerge.Connect                         (i.e. 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 “2” to block the toolbar for  the user.

Symptoms

Cause

More...

When using Documents Core Pack in different environments (office, home etc.) it is necessary to configure 2 profiles for the client.

1 for the IFD connection and 1 for the standard connection.
These profiles are configured via the DCP dataprovider on the client.

Please open the registry and add the the following string value to Hkey_Current_User\Software\PTM EDV-Systeme\WordMailMergeClient.

String value= failoverprofile
Value for failover profile = GUID of  the IFD profile.

Adding this setting to the Current User will ensure that DCP switches between the profiles as soon as a connection typ is not available.

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.

In an IFD Environment it is hard to implement a FileShare which is available through the Internet. We found a product named WebDrive where you could configure e.g. an FTP which will be mapped to a local drive. Here is a link to the product website: http://www.southrivertech.com/products/webdrive/winindex.html
You’re able to connect to FTP, WebDAV, FrontPage, GroupDrive, SFTP (ssh) and Amazon-S3.

We tested it out and in combination with DCP FileExplorer Integration it works like a charm.

More...

Basics:

Licensechecks are done each time the application is accessed by a user. Having an invalid license stops the whole product from working. And invalid license will never have any impact on the CRM, it only limits the addon itself.

Reasons for an invalid license :

• Wrong license OrganizationUnit
• Usercount has execeeded the granted licenses (Stops whole product, not only for the excessive users on all license models)
• Upgrading the product after having the support contract expired
• In Case of a time limited license (and a trial) : Reached the end of the license lifetime.

Licensetype normal license (aka perSite license)

Requires a license for each active CRM user, no matter if he uses the product or not. If new CRM users are added, the license needs to be extended with more users as well.

Disabled, ReadOnly users and Administrative users do not require a license.

Licensetype perUser license

Requires only as many licenses as you actually want to have, but starts at a minimum of 10 licenses and is double the price of a site license.

The license is a named user license and the license is activated via a checkbox on the Systemuser entity for a specific user. You may activate as many users for the access as you have licenses.

Exceeding the granted license count stops the product for all users.

This function  allows DCP users to add the document to each created activity! (only when using the file explorer or sharepoint setup).

For example when sending a mail to a marketing list,  an activity will be created for each member of the marketing list  and this extra setting will ensure that activity also has the document attached in CRM.

First you have to create a new Settings Key.                                                                   

In CRM first you have to open the “Settings” and then click on “mscrm-addons settings”.

More...

Symptoms

MSCRM ADDONS Toolbar not visible in Word

Cause

Deactivated elements

Solution

After WordMailMerge has been installed on your pc it can happen that our toolbar doesn't appear in word. To sort this problem please check the following steps.

More...

The problem due to the fact, that MS CRM is using an HttpModule for multitenancy scenarios. This http module will be called with an anonymous user account and therefore fail when trying to request e.g the metadata webservice.

Solution: To make it work, a new entry (remove CrmAuthentication) has to be specified within the web.config file of the specific Add-On.

<system.web>
 ...
 <httpmodules> 
 <remove name="CrmAuthentication" />
 </httpmodules> 
 ...
</system.web>