Resources for IT Professionals > Dynamics Forums > CRM Deployment > Microsoft Dynamics CRM for Outlook Configuration failed
Ask a questionAsk a question
 

AnswerMicrosoft Dynamics CRM for Outlook Configuration failed

  • Wednesday, June 03, 2009 1:32 PMAndriy a33ik Butenko Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi. Have a little problem with configuration of Microsoft Dynamics CRM for Outlook.

    On 32-bit Vista everything works fine. But when 64-bit Vista used have a problem with configuration:



    screen appears. And End of log file:

    11:18:37|  Error| Configuration exception.System.Exception: Action Microsoft.Crm.Config.Client.InstallPstAction failed. ---> System.Runtime.InteropServices.COMException (0x8004010F): LaunchOutlookInstallerProcess failed.
       в System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       в Microsoft.Crm.Config.Client.InstallPstAction.Do(IDictionary parameters)
       в Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)
       --- Конец трассировки внутреннего стека исключений ---
       в Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)
       в Microsoft.Crm.Setup.Common.Installer.Install(IDictionary stateSaver)
       в Microsoft.Crm.Setup.Common.ComposedInstaller.InternalInstall(IDictionary stateSaver)
       в Microsoft.Crm.Setup.Common.ComposedInstaller.Install(IDictionary stateSaver)
       в Microsoft.Crm.Config.Client.ClientConfig.Install(IDictionary data)
       в Microsoft.Crm.Config.Client.ClientConfig.Run()
    11:18:37|Verbose| Configuration Failed
    11:18:37|   Info| We were unable to successfully configure Microsoft Dynamics CRM for Outlook:

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

    I will be appreciated for any help.
    Truth is opened the prepared mind My blog - http://a33ik.blogspot.com

Answers

  • Wednesday, June 03, 2009 6:31 PMRichard M. Riddle Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The installpstaction failing sometimes indicates that Outlook has not been opened at least once prior to configuration or, if this is an upgraded client, the old PST still exists.  This does not appear to be an issue of Vista not support the 32-bit program, because you indicate the error is during configuration, which can only begin after a successful installation.

    Further, the media center edition of XP is not supported because media center pcs cannot be joined to a domain, which was necessary for CRM 3.0 Outlook clients.  If connecting only to an IFD or CRM online, you should be able to use media center pc.

All Replies

  • Wednesday, June 03, 2009 2:06 PMMichael SulzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Andriy,

    the Outlook Client is a 32bit application, 64bit is not supportet.

    on my client, a windows server 2008 64 bit works the outllo client in outllok 2007 very good, i have no problems.


    Viele Grüße

    Michael Sulz
    axcentro GmbH
  • Wednesday, June 03, 2009 2:16 PMAndriy a33ik Butenko Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi, Michael.

    According to Implementation Guide for Microsoft Dynamics CRM 4.0:


    Any one of the following operating systems is required.

    ·         Windows Vista

    ·         Windows XP Professional SP2 or SP3

    ·         Windows XP Tablet PC Edition SP2 or SP3

    ·         Windows XP Professional x64 Edition

     

    Important

    ·         Windows XP Media Center Edition is not supported for installing and running Microsoft Dynamics CRM for Outlook.

    ·         Because Microsoft Dynamics CRM for Outlook and Microsoft Dynamics CRM for Outlook with Offline Access are 32-bit applications, they must run in the Windows on Windows (WOW) system, when the application runs on a Windows XP Professional x64 Edition or a Windows Vista edition that is running on an x64 computer .

    I don't see why 64bit editions are not supported.

    Truth is opened the prepared mind My blog - http://a33ik.blogspot.com
  • Wednesday, June 03, 2009 2:44 PMMichael SulzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Andriy,

    you are right, the Outllook client is supported under x64 systems.

    Viele Grüße

    Michael Sulz
    axcentro GmbH
  • Wednesday, June 03, 2009 6:31 PMRichard M. Riddle Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The installpstaction failing sometimes indicates that Outlook has not been opened at least once prior to configuration or, if this is an upgraded client, the old PST still exists.  This does not appear to be an issue of Vista not support the 32-bit program, because you indicate the error is during configuration, which can only begin after a successful installation.

    Further, the media center edition of XP is not supported because media center pcs cannot be joined to a domain, which was necessary for CRM 3.0 Outlook clients.  If connecting only to an IFD or CRM online, you should be able to use media center pc.
  • Friday, November 06, 2009 4:56 PMGavasso Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    There is a Microsoft KB for this error: http://support.microsoft.com/kb/948312.
  • Friday, November 20, 2009 4:52 PMMartinNr5 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vista and Windows 7 require the user you are configuring the client for to be in the local administrators group. You then run the configuration guide as administrator, i.e. with elevated privilegies, in order to finish the installation (still logged on as the user you need to configure CRM for though).

    None of the CRM-related patches or applications that require elevation ask for it. Some fail ungracefully - like the one above - others point out that they need to be run as administrator but does not ask for credentials.

    After you have run the guide you can remove the user from the local admins group.

    It is claimed that from Update Rollup 7 you don't need this workaround but I have found (just now) that to be untrue.