Using Dynamics CRM

“Insufficient Permissions” when logging in Dynamics CRM using custom role

Frédérick Lecavalier — Wed, 18 Feb 2009 12:42:23 +0000

If you have used custom security role in Dynamics CRM, you may have seen this error message when a user tried to log in for the first time.

The initial workaround for this problem was:

Give a standard role to the user (such as System Administrator)
Ask the user to log in CRM
Remove the standard role and assign him the custom role

Microsoft finally came out with solution to this problem (kb 948311). The solution is allowing the “write” permission for the “User Settings” under “Business Management”.

Microsoft Dynamics has encountered an error while using Mail Merge with CRM Live

Frédérick Lecavalier — Mon, 09 Feb 2009 10:24:45 +0000

If you are using CRM Live, you may have experienced this error message while trying to use the Mail Merge functionality from the Outlook Client.

In order to fix this error, add the following Web site to your Trusted Sites in Internet Explorer.

https://signin.crm.dynamics.com
https://login.live.com
https://[organization name].crm.dynamics.com*

* Replace [organization name] with your own organization name. This is the URL used to login to CRM Live using the Web client (Internet Explorer).

Installing Visual C++ Runtime Required Components

Frédérick Lecavalier — Sun, 08 Feb 2009 11:16:30 +0000

If you had to run the installation program more than once for any of the Dynamics CRM components (Server, Outlook Client, Email Router, …) you probably realized that Visual C++ Runtime have to be install, even if it has already been installed on the server.

According to Microsoft KB 950421:

“This problem occurs because the Setup program of Microsoft Dynamics CRM must install the Visual C++ runtime components, even if the components are already installed.”

One or more e-mails in Microsoft Dynamics CRM are waiting to be sent

Frédérick Lecavalier — Sat, 07 Feb 2009 00:47:02 +0000

One of our customer ask us why they were always getting a message from CRM saying that “One or more e-mails in Microsoft Dynamics CRM are waiting to be sent” and there emails were not actually sent to the recipient.

The answer to this message resides in the Personal Options of the user. On the e-mail tab, you need to allow Microsoft Dynamics to send e-mail using CRM for Outlook.

After you made this modification, e-mails will be sent and a copy will be available in your “Sent Items”

Your Web browser options are currently set to disable cookies!

Frédérick Lecavalier — Fri, 06 Feb 2009 20:11:11 +0000

Recently, I was installing the Dynamics CRM for Outlook client at a customer and I kept having this error message while starting Outlook.

I looked at every option in IE to enable cookies but they were all enabled. The Web client was working without any problem. After a few searches on the Web, I found few hints referring to the server name. I haven’t realized that the server name contained an underscore (server_crm). Since SQL was installed on the server, I didn’t want the server to be renamed. I asked the IT guy to add a DNS entry called “CRM” referring to the server, which he did.

After uninstalling and reinstalling the Dynamics CRM for Outlook client, I received the same error. A look at the registry keys located under HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient and 4 entries were still referring to the original server name.

I’Ve exported the key and removed the unneeded line. I then replaced the original server same with CRM.

** demo should be replaced with your organization name.

After importing this file, I was able to use the Dynamics CRM for Outlook client without any problem.

Unable to load plug-in in assembly

Frédérick Lecavalier — Sat, 17 Jan 2009 12:10:29 +0000

Yesterday, I installed a plug-in created by one of our CRM developer. To do so, I used the plug-in registration tool and I didn’t get any error while registering the plug-in.

When I launced CRM, I received an error message saying “Unable to load plug-in in assembly”.

I found out that I registered my plugin on the disk and I didn’t copy the DLL in the appropriate folder (C:\Program Files\Microsoft Dynamics CRM\Server\bin\assembly). I unregistered the plug-in and registered it again using “database” property and the error message was gone when launching CRM.

“The path is not of a legal form” while installing the Dynamics CRM Outlook client

Frédérick Lecavalier — Sat, 17 Jan 2009 11:18:18 +0000

Recently, I was installing the Dynamics CRM 4.0 Outlook client on a test server. After selecting the install directory, I received an error message saying “The path is not of a legal form”.

This path is not of a legal form

However, the specified folder was “C:\Program Files\CRM Client” and it was present on the C drive. After a few searches on the Web, I found someone having a similar issue while installing the CRM Data Migration Manager.Their solution was to update manually the registry.

Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-18\Products\59DD8CB00184F24E99A62CF4D6109FA\InstallProperties]

Name: InstallLocation
Set the Data value to “C:\Program Files\Microsoft Dynamics CRM”

After this modification, setup continued without an error (this was empty on my installation).

Installing Dynamics CRM 4.0 using SQL 2008

Frédérick Lecavalier — Sat, 03 Jan 2009 12:42:10 +0000

During the holiday, I tried to install Dynamics CRM 4.0 on a SQL 2008 box running Sharepoint 2007. While running the install program, I faced two issues:

Service msftesql was not found on my server
CRM doesn’t seem to work if SRS has been configured to run in SharePoint integrated mode

The first issue, related to the Full-Text Search service, could be easily resolved by updating the setup files while installing the application as explained in Microsoft Knowledge Base article number 957053.

The second issue, related to SRS being configured to run in SharePoint integrated mode, is more complex to resolve. After a lot of research on the Web, I found many post saying that CRM does not support this configuration. However, I have not been able to find an official statement saying so. I finally installed another instance of SQL on my MOSS server to run CRM.

Enabling Multi-Language Interface (MUI) in Microsoft CRM 4.0

Frédérick Lecavalier — Sat, 27 Dec 2008 12:38:03 +0000

To enable multilanguage support in Microsoft CRM, you first have to download and install the language pack from Microsoft website.

http://www.microsoft.com/downloads/details.aspx?familyid=639EBB2E-236C-46F0-89A3-5B24D816E5B1&displaylang=en

Once the language pack have been installed, you have to enable it by logging in the CRM and going to Setting / Administration / Languages.

Users can then go to Option and select a language preference for both user interface and Help files. The language user interface includes Menus, Navigation Labels, Form Labels, Picklists, Reports, Knowledge Base Articles, E-mail Templates and System Customizations such as Custom Fields. However, actual data is not translated.

Invalid Action while accessing Microsoft CRM 4.0

Frédérick Lecavalier — Tue, 23 Dec 2008 02:44:16 +0000

After the week-end, we tried to access our Microsoft CRM 4.0 development server but were not able to. The meagingfull error message was ”Invalid Action: The selected action was not valid” error message.

While looking at the application log, we found the following:

Event Type: Error
Event Source: MSCRMKeyGenerator
Event Category: None
Event ID: 18949

Description:
Current active key (KeyType : CrmWRPCTokenKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:97f2183d-3bb6-dd11-8383-00155d00a608, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:11/19/2008 13:09:05, ExpiresOn:12/22/2008 13:09:05, CreatedOn:11/19/2008 13:09:05, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Key Setting :

After investigation, it appears that the Microsoft CRM Asynchronous Processing Service was stopped. After restarting the service, the error message disappeared.