Experience your
30 day trial
now!
GET STARTED
This post will cover some of the common issues seen in support and the common resolutions to those issues. In this post we will focus on 3 main areas:
This post will also cover the Client Auto Update to help get the Update Rollups deployed faster to your users.
Troubleshooting Client Configuration
Check Managed Passwords:
If you’ve upgraded from the 3.0 Client:
Permissions Issues when configuring:
Active Directory DNS Issues:
Check the Deployment Properties table:
You may have an issue with MAPI . This is not as frequent, and this would be a last step.
Login Issues
Check the URL you are using:
Permissions may be causing a problem:
- CrmCheckPrivilege failed. Returned hr = -2147220960 on UserId: 8bebb2df-3ac8-dc11-8d71-005056000030 and PrivilegeId: 588725dd-c878-41c5-a4c3-5efc93cd3ffd
- If permissions are missing look in the Organization database to find out what privilege is missing.
Do you have any 3rd Party Addin’s?
Check the IFD Settings if it is enabled:
CRM Outlook Add-in Responsiveness
Apply the latest Update Rollup for Microsoft Dynamics CRM 4.0
Disable other Outlook Add-ins to see if the issues still occur.
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 to capture a Crash Dump or a Hang Dump:
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 Files\Debugging 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.
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 Files\Debugging 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
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.
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.
Client Update
Steps to deploy hotfixes to your Microsoft Dynamics CRM 4.0 Client for Outlook users.
<ClientPatches> <Create> <ClientPatchInfo> <PatchId>{004A7E60-5DB7-4F05-B7C1-1D2DD653A1A6}</PatchId>* <Title>Update Rollup 4</Title> <Description>Microsoft Dynamics CRM 4.0 – Update Rollup 4</Description> <IsMandatory>true</IsMandatory> <IsEnabled>true</IsEnabled> <ClientType>OutlookLaptop,OutlookDesktop</ClientType> <LinkId>150735&clcid=0x409</LinkId>** </ClientPatchInfo> </Create> </ClientPatches>
Notes:
*See http://blogs.msdn.com/crm/archive/2009/02/11/update-rollup-2-for-microsoft-dynamics-crm-4-0-more-info.aspx for all the patchid’s and linkid’s for UR2 *See http://blogs.msdn.com/crm/archive/2009/03/13/update-rollup-3-for-microsoft-dynamics-crm-4-0.aspx for all patchid’s and linkid’s for UR3 *See KB http://support.microsoft.com/default.aspx/kb/968176 for all patchid’s and linkid’s for UR4 (All patchid’s and linkid’s will be included in the Update Rollup KBs going forward). **When using a LinkId like 140023&clcid=0x409 it will fail to upload so you need to use 140023&clcid=0x409
Note: This is assuming the clientconfig.xml you created is also in the same directory. After running the command wait 30 seconds for the cache to flush before trying to check for updates on your client machine.
For more information on the Client Auto Update see the Microsoft Dynamics CRM Implementation Guide. (http://go.microsoft.com/fwlink/?LinkID=104413)
Thanks,
Microsoft Dynamics CRM Support Team
PingBack from http://microsoft-sharepoint.simplynetdev.com/troubleshooting-the-microsoft-dynamics-crm-client-for-outlook/
Hi,
thanks for this post - it is quite helpful.
We are currently in testing prior to rolling out the CRM Outlook client to about 100 users.
Does anyone know why we would keep getting an error "Microsoft Dynamics CRM was unable to add the Web address of the Microsoft Dynamics CRM server to Trusted Sites. ...".
Our CRM server url is part of our intranet domain which is a trusted site, but we keep getting this error ?! Any ideas why this may be ?
Peter
Hi ,
We are also testing prior to rolliwng th our the Outllok Client to 100 users.
And we are getting the exact same error that Peter mentions in his Augist 11 post.
In our test sample the error has only impacted half of the PCs.
Any solutions out there?
Tom
We have Dynamics 4.0 working on NT however we are starting to use Win 7 machines.
The install seams to have gone well on the trial machine however Ive noticed that when a new recorid is created from outlook the new contact screen that opens in completely blank can anybody help with this please?
Thanks, Gareth, Auckland
would we test the outlook client in the dev environment or should it always be tested against the live and if that is the case then what happens when we send out emials?
Does anyone have an issue where the Outlook CRM client toolbar just disappears?