Last week the Microsoft CRM Support Team released a fantastic blog outlining common Outlook CRM Client issues and fixes to those issues. This post also included some additional troubleshooting information around configuration issues, login issues and responsiveness issues.

While their blog post was certainly thorough, it lacked a bit in terms of clarity and cohesion. Experienced CRM administrators would be able to decipher the information but it was slightly lacking for the end user. No pictures, no clear instructions for which programs and services to run, etc.

It is with these limitations in mind that I present to you: The Outlook CRM Client Troubleshooting Guide 'For The Rest Of Us!'

We will focus on 3 areas:

1. Client Configuration Issues

2. Login Issues

3. Outlook Add-In Issues

Troubleshooting Client Configuration

Check Managed Passwords:

  • When logging in through Internet Explorer from the client machine do you Get Prompted for Credentials?
    • Set "Automatic Logon with current user name and password" for the zone where the CRM URL was located. In Internet Explorer, click Tools > Internet Options

    • Under the Security tab, check the custom level options for User Authentication and select "Automatic Logon with current user name and password". This should be done for your 'Trusted' sites.

  • Remove Stored Passwords : located in Control Panel > User Accounts > Managed Passwords

If you've upgraded from the 3.0 Client:

Method 1: If you have Microsoft Office Outlook 2007 installed

  1. Start Outlook 2007.
  2. On the Tools menu, click Account Settings.

  3. Click the Data Files tab, Click Microsoft CRM, and then click Remove.

  4. Click the Address Books tab, Click Microsoft CRM Address Book, and then click Remove.

  5. Exit Outlook 2007.

Method 2: If you have Microsoft Office Outlook 2003 installed

  1. Exit Outlook 2003.
  2. Click Start, click Control Panel, click User Accounts, and then click Mail.
  3. In the Mail Setup dialog box, click Data Files.
  4. Click Microsoft CRM, click Remove, and then click Close.
  5. In the Mail Setup dialog box, click E-mail Accounts.
  6. Click View or change existing directories or address books, and then click Next.
  7. Click Microsoft CRM Address Book, and then click Remove.
  8. Click Close to close the Mail Setup dialog box.
  • If still failing: Uninstall 3.0, uninstall and reinstall CRM 4.0.

Permissions Issues when configuring:

  • The error message is "Action Microsoft.Crm.Config.Client.InstallPstAction failed. LaunchOutlookInstallerProcess failed."

Active Directory DNS Issues:

  • The following error is shown when configuring – "The configuration wizard cannot connect to the Microsoft CRM server. This might indicate that the server is down."
    • Add DNS Record for Organizations being accessed over IFD
    • Add DNS Records if you are using a Host Header on the CRM Website
  • Verify you have the correct SPN set on the Account running the AppPool. (http://support.microsoft.com/kb/929650)

Check the Deployment Properties:

You may have an issue with MAPI .
This is not as frequent, and this would be a last step.

  • You receive the error "Action Microsoft.Crm.Config.Client.InstallPstAction failed. LaunchOutlookInstallerProcess failed."
    • Run the fixmapi.exe which is located at %windir%system32fixmapi.exe
    • Double Click to run

Login Issues

Check the URL you are using:

  • Can you login in from the client machine with Internet Explorer successfully?
  • Does the User in CRM have a CRM Security Role?
  • Is the user set to Administrative Mode on the user record in CRM?
    • If so the users set to Administrative Mode will not be able to successfully launch the Microsoft Dynamics CRM Client for Outlook.

 

Check Managed Passwords as in the Client Configuration section

Permissions may be causing a problem:

  • First, check the Permissions on the Security Role
    • Turn on Platform Tracing and Reproduce the Issue.
    • Search the Platform Trace Logfile for any CrmCheckPrivilege errors. It will resemble the following:

    CrmCheckPrivilege failed. Returned hr = -xxxxxxx on UserId: {SOME USER ID GUID} and PrivilegeId: {SOME PRIVILEGE GUID}

  • If permissions are missing, look in the Organization database with SQL Server Tools to determine which Privilege is missing.
    • Select your Organization's DB [ORGNAME_MSCRM]

    • Run the following statement: Select * from privilegebase where PrivilegeID = [THE PRIVILEGE ID FROM THE ABOVE STEP]
  • On the User Record in CRM, check the Access Mode and see if it is set to Administrative Mode, and if it is, change it to Full

  • If there could be a permission issue on the Website in IIS. Look at the IIS Logs after reproducing the issue.
    • Where are my IIS Logs stored?
      • Run IIS
      • Select the website from file tree on left and right-click > Properties

      • On the website tab you will see a button that says 'Active Log Format.' Click on the properties button

      • At the bottom of the General Properties tab you will see a box which lists the Log file directory and the name of the log file. Navigate to this area and open your log file.

Do you have any 3rd Party Addin's?

  • Do you have the latest updates to other Addin's?
  • Temporarily disable 3rd party Addin's to find the Addin that is causing the issues.

Check the IFD Settings to see if it is enabled:

CRM Outlook Add-in Responsiveness

Apply the latest Update Rollup for Microsoft Dynamics CRM 4.0

  • Run Update from Start Menu at Start > Program Files > Microsoft Dynamics CRM

     

  • Select 'Update' from the CRM Drop Down Menu in Outlook

     

  • If Auto Update is not configured, download the latest rollup from Microsoft

Disable other Outlook Add-ins to see if the issues still occur.

  • Start enabling the Add-ins one at a time to find out what Add-ins are causing the issues.
  • Check to see if there are any new updates for the Outlook Add-ins that are installed on the client machine. We have seen issues where older versions of some Outlook Add-ins have caused issues with Microsoft Dynamics CRM.

Gather a crash dump or hang dump to send into Technical Support using the ADPlus Tool at http://support.microsoft.com/kb/286350

ADPlus is a tool that will allow us to get a memory dump from a process that is giving you problems. To get this tool, please install the most current version of "Debugging Tools for Windows" from http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Once these tools are installed, do the following:

 

1. Create a directory called c:adplus

2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is c:Program FilesDebugging Tools for Windows

3.a. Crash Dump – If Outlook crashes (restarts or the Outlook.exe process disappears), then a crash dump is required.  This can be captured using the following commands and needs to be run before the Outlook crash occurs.

To capture a Crash Dump type the following:

cscript adplus.vbs -crash -pn Outlook.exe -o c:adplus

Note: a WARNING window will pop-up regarding debugging symbols – click OK

3b. Hang Dump – If Outlook is hanging or non-responsive to mouse clicks or keyboard commands for at least a minute or more than a hang dump may be required to troubleshoot the issue and can be captured using the steps below.  The hang dump is a point in time capture and must be performed after the hang has occurred.  Do not perform the steps to capture a hang dump before the problem has occurred, but after the Outlook.exe process has hung.

To capture a Hang Dump type the following:

cscript adplus.vbs -hang -pn Outlook.exe -o c:adplus

Note: A WARNING window will pop-up regarding debugging symbols – click OK
Note: It is best to take three different Hang Dumps usually 30-60 seconds apart from each other.

4. Do not interfere with the windows that are opened, just let it run minimized.

5. You will not be able to log off the system while you are monitoring.

6. After the hang/crash occurs, please zip and send the contents of the c:adplus directory.

If help is required with these procedures, please open a support case.

 

Final Words

Troubleshooting the Outlook client can be a daunting task when one considers the sheer amount of components that are working together to create a seamless work environment. Hopefully this blog was able to provide some assistance with isolating and fixing issues with the Outlook CRM client. All we focus on here at PowerObjects is Microsoft Dynamics CRM; it is our passion. If you were unable to solve your issue using this guide, we are available on a time and materials basis to dig in and solve any issue that you may be experiencing. Please contact us and let us know how we can bring focus to your Dynamics CRM!

Return to Top ▲Return to Top ▲