Action Microsoft.Crm.Config.Client.InstallPstAction failed

While installing the Outlook Client, there is one error that appears to be popping up more than others:


Action Microsoft.Crm.Config.Client.InstallPstAction failed.
LaunchOutlookInstallerProcess failed.

There are some blog posts which offer solutions to this error message. If you have this message, try the following:
- Run %windir%\system32\fixmapi.exe
- Reinstall the client
- Install latest rollup of the Dynamics CRM for Outlook client (same version as on server)

Or look at the following blogs:
- http://blogs.msdn.com/crm/archive/2009/05/29/troubleshooting-the-microsoft-dynamics-crm-client-for-outlook.aspx
- http://blogs.msdn.com/mscrmfreak/archive/2006/06/12/627955.aspx

Now these solutions didn't fix the error for one of our clients. Thanks to my colleague Wouter de Nooij we solved this by setting the Microsoft Office language to English. Then redo the configuration (using Start > Microsoft Office > Microsoft Office Tools > Microsoft Office 2007 Language Settings). After that the configuration succeeded. Resetting the language setting to Dutch did not result into problems, so all is well now.

Update:
One more solution to add to the list:
- Provide write access to the file C:\Program Files\Common Files\System\MSMAPI\1033\MAPISVC.INF or "Program Files (x86)" for 64bit machines.

Please let me know if you find other solutions for this error message!

4 comments:

Anonymous said...

We got the same problem on one of the machines after updating MS CRM Client for Outlook v 3.0 installed via AD Group Polices to 4.0 version. We solve this problem by uninstalling 3.0 client (was shown only in "Add or remove programs")

Anonymous said...

Yes, make sure you have the latest security roll-up applied and this error goes away.

John Bryntze said...

"Update:
One more solution to add to the list:
- Provide write access to the file C:\Program Files\Common Files\System\MSMAPI\1033\MAPISVC.INF or "Program Files (x86)" for 64bit machines."

This fixed it! thanks a lot
/John Bryntze

Daniel said...

After 4 hours of installing/uninstalling, running %windir%\system32\fixmapi.exe fixes the problem for me.

Thanks for the post!