CRM Watcher

CRM Watcher is the source for the latest Microsoft Dynamics CRM News and Downloads.

Saturday, May 10, 2008

Microsoft Dynamics CRM 4.0 upgrade / installation issues

Till now we' ve upgraded some of our customers to the new CRM 4.0 version and by doing that some issues appeared. Below some of them.

Issue 1:

Installation of CRM Outlook cliënts not possible in a Citrix / Terminal Server environment.

During installation the message appears, that there's an incompatible Exchange Server installed on the server but none of the servers we 've tried were Exchange Servers.....

This issue can easily be solved by editing the registry:

  1. Open the registry editor
  2. Export the whole key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange
  3. Delete this key
  4. Install the CRM cliënts
  5. Reïmport the key

Issue 2:

After an upgrade to CRM 4.0 we ran into a problem on decimal / money fields. By entering a value on a money / decimal field and saving it, the value changes with a factor 1000 and then will be multiplied  everytime with 100 when saving the record again.

To correct this issue you've to run a query via SQL Server Management Studio:

UPDATE UserSettingsBase SET DecimalSymbol = ','

Issue 3:

One of the error's i've seen during the installation of the Data Migration Manager is this one:

"The Data Migration Manager encountered an error while setting up the temporary migration database. Restart the Data Migration Manager, and then try migrating the data again."

You can resolve this issue by deleting the registry key, restarting Data Migration Manager, and signing in again.

You can find this registry key in the following path (depending on your system type):

  • 32-bit systems: HKLM\SOFTWARE\Microsoft\Data Migration Wizard

  • 64-bit systems: HKLM\Software\Wow6432Node\Microsoft\Data Migration Wizard

Issue 4:

The language pack(s) can't be activated

How to resolve this issue:

  1. Export the current customizations file
  2. Import the default customizations file (publish)
  3. Activate the language packs
  4. Import the customizations file of step 1 (publish)