none
Error while creating new organization (Deployment Manager - Dynamics CRM 2013)

    Question

  • While creating a new organization via Deployment Manager, I am facing the following error:
    Action Microsoft.Crm.Tools.Admin.ImportDefaultDataAction failed. Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=105; handshake=13532; [Login] initialization=0; authentication=1; [Post-Login] complete=136426; The wait operation timed out

    I tried google, but failed to find any solution with this specific error while creating an organization.

    My (Test) Environment

    • Windows 7 (Host)
      • VMWare Workstation 10.0 with 1 GB memory and 1 core (Guest)
        • Windows Server 2012
        • SQL Server 2012
        • Dynamics CRM 2013 trial (downloaded from Microsoft website)

    Paradise lies at the feet of thy mother. - Prophet Mohammed (PBUH) (skype: ali.net.pk)


    • Edited by Ali .NET Sunday, November 03, 2013 12:18 PM title enhancement
    Sunday, November 03, 2013 12:16 PM

Answers

  • Sorry for replying too late.

    It was a performance issue and got resolved by upgrading

    • processor to Core 2 Quad
    • RAM up to 6GB

    VMware Workstation settings:

    • 2GB memory
    • 2 cores

    Also apply VMware performance tweaks if required:
    Top 10 VMware Performance Tweaks


    Paradise lies at the feet of thy mother. - Prophet Mohammed (PBUH) (skype: ali.net.pk)



    • Marked as answer by Ali .NET Saturday, February 01, 2014 4:52 PM
    • Edited by Ali .NET Saturday, February 01, 2014 4:53 PM
    Saturday, February 01, 2014 4:51 PM

All replies

  • Hi Ali,

    Have you checked/monitored SQL server's system resources. Have a look at the CPU/RAM and Disk IO performance counters for SQL Server. It looks like to be a resource issue. Also, do you see any error in SQL server log?



    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" Thanks, Imran Abbasi

    Sunday, November 03, 2013 11:20 PM
  • Sorry for replying too late.

    It was a performance issue and got resolved by upgrading

    • processor to Core 2 Quad
    • RAM up to 6GB

    VMware Workstation settings:

    • 2GB memory
    • 2 cores

    Also apply VMware performance tweaks if required:
    Top 10 VMware Performance Tweaks


    Paradise lies at the feet of thy mother. - Prophet Mohammed (PBUH) (skype: ali.net.pk)



    • Marked as answer by Ali .NET Saturday, February 01, 2014 4:52 PM
    • Edited by Ali .NET Saturday, February 01, 2014 4:53 PM
    Saturday, February 01, 2014 4:51 PM