MS Dynamics CRM 4.0 Client Configuration Wizard fails with “Outlook is not set as the default mail client” on Windows Server 2008 x64

Whilst trying to install the MS CRM 4.0 client on my laptop today I received the following error:

Microsoft Outlook is not set as the default mail client. Please set Microsoft Outlook as the default mail client from Control Panel\Internet Options\Programs, and then re-run the check.”

Luckily this was fairly easy to diagnose with the help of the excellent Process Monitor utility. All I had to do was setup a filter to only capture events for the “Microsoft.Crm.Client.Config.exe” process by going to Filter->Filter and selecting Process Name is Microsoft.Crm.Client.exe as an inclusion filter. Then using the toolbar deselect the file events and run through the wizard again until I got an output like this:

Here we can see that the registry key [HKLM]\SOFTWARE\Wow6432Node\Clients\Mail\(Default) key is being interrogated, a quick look at this in Registry Editor shows that the default is “Windows Mail” for some reason as shown below:

All we need to do is change this value from “Windows Mail” to “Microsoft Outlook”:

Then the wizard will run through fine!

Summary

I am unsure if this is a Windows Server 2008 issue or a general x64 issue, however to resolve it change
[HKLM]\SOFTWARE\Wow6432Node\Clients\Mail\(Default)
from “Windows Mail” to “Microsoft Outlook”

I am unsure if the Wow6432 key is unique to my machine / configuration.

About these ads

7 responses to “MS Dynamics CRM 4.0 Client Configuration Wizard fails with “Outlook is not set as the default mail client” on Windows Server 2008 x64

  1. Have you ever tried to open microsoft outlook. When it prompts you to set as the default mailing client all you had to do was click on the buton Yes.
    Another thing you could have done was open the control panel and set outlook as the default mailing client.
    But it’s always a good choice to install a process monitor, attach it to the installer, analyze witch keys are being acessed in the registry and change them… This is the easiest solution :)

  2. @DebianWayOfLife,
    I really don’t know why I didn’t consider using the GUI as you suggest to set the default client…..

    Oh actually I do, it’s because it already was set as the default client and clearly the installer was checking in the wrong way for x64 (WoW)

  3. On Server 2008 using the tick box in Outlook:
    Make this the default program for… doesn’t work.
    If you follow the instructions on the CRM Setup program to use Internet Explorer/Internet Options/Programs you discover that its changed on Server 2008 (32bit and 64bit). The same is true of default programs in Control Panel (takes you to the same place). You can associate Outlook with a series of extensions but thats not good enough.
    In order to make the client happy you do seem to need a registry edit. 32bit Server 2008 is just the same but without the WOW64 branch.

    Thank you for discovering this answer for me. I’ve never appreciated the usefulness of tools like process monitory

  4. Exellent thanks alot been lokking for this.. solved my big problem. :)

  5. Thanks, that fixed it.
    Also, “Wow6432″ was exactly the same on my 2008 64 bit server

  6. Thanks alot for this solution. Great Job. :)

  7. Thank you! This worked for me too, after using the default programs GUI failed to make outlook the default.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s