System.Exception: Action Microsoft.Crm.Setup.Server.InstallConfigDatabaseAction failed. —> System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.



Got this error while installing CRM 2013.

Following post helped in fixing the issue.

Hope it helps.

“Could not open a connection to SQL Server” error while installing CRM 2011 Server


Nishant Rana:

Faced the same issue while installing CRM 2013.

Originally posted on Rajeev Pentyala - Dynamics CRM Blog:


You may come across below exception while installing CRM 2011 Server.

“Named Pipes Provider, error: 40 – Could not open a connection to SQL Server “

Scenario :-

  • You have a standalone machine “VM 1″, with SQL Server 2008  application
  • You have another machine “VM 2″, where you are trying to install “CRM Server” by pointing to the SQL Server on “VM 1″
  • Installation wizard throws the “Could not connect to….” exception in the midway

Reason :-

  • Remote connection was not enabled on SQL Server machine

Fix :-

  • Connect to the machine where SQL Server 2008  installed
  • Open the “Sql Server Configuration Manager” (i.e.,  Start –> All Programs –> Microsoft SQL Server 2008 R2 –> Configuration Tools)
  • Enable “Named Pipes” protocol (Refer below screen)
Enable "Named Pipes" protocol
  • Restart the “MSSQLSERVER” service (Go to “Run -> Services.msc”)
Restart "MSSQLSERVER" service
  • Resume the installation.

Hope it helps :)

View original

“Save and New” button in CRM 2013.


After upgrading the existing CRM 2011 solution to CRM 2013 we found out that Save and New button is missing while creating related child records.

The way we got it back was to open the solution in Ribbon Workbench and Customizing the command for Save and New button.


And removing the Mscrm.HideOnCommandBar rule.



Hope it helps.

Unable to get property ‘get_element’ of undefined or null reference in CRM 2013.



We were getting this error, while trying to add a new related child record through sub grid.

Only for few users with a specific role, we were getting this error. Installing the update rollup 2 fixed the issue.

Hope it helps.

An item with the same key has already been added error while importing solution in CRM 2013



Recently while importing a solution from dev environment to test environment we were getting this error.

This error occurs when we have some kind of mismatch among the attribute in both the environment for e.g. same attribute is created in both the environment with different datatype.

After comparing the dev and test environment, we realized that the Schema Name for one of the field was different in dev environment.

i.e. lss_Client_agress_to_LSSContract in test and lss_client_agress_to_lsscontract in dev

So we removed the field from form and deleted it in our dev environment.

After that import worked properly.

Hope this helps