Nishant Rana's Weblog

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

Faced the same issue while installing CRM 2013.

Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

Hi,

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)

Restart the “MSSQLSERVER” service (Go to “Run -> Services.msc”)

Resume the installation.

Hope it helps 🙂

View original post

“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.

Hi,

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.

http://cupofdev.com/crm2013-rollup2-fixlist/

http://www.microsoft.com/en-in/download/details.aspx

Hope it helps.

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

Hi,

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

Refreshing the Web Resource in CRM 2013.

In one of our Entity’s Form we were using HTML Web Resource and this HTML web resource was showing values of the attributes in that form.

Now in CRM 2011, after we save the record the form reloads and so our web resource was picking up the new values saved.

However in CRM 2013, on save, as the form doesn’t reload, the values were not getting updated in the HTML Web Resource.

So the solution was to refresh the Web Resource using Jscript on the On Save event of the form.


function refreshWebResArea() {

var webResArea = Xrm.Page.ui.controls.get("WebResource_Name");

webResArea.setSrc(webResArea.getSrc());
}

Hope it helps.

Getting back the Mail Merge button in CRM 2013

After upgrading to CRM 2013, we found out that mail merge button was missing in the command bar.

The solution was to customize the command for the existing mail merge button on the form.

For this open the solution containing the entity in Ribbon Work Bench and select Form of the Entity.

Right click the Mail Merge button and select Customize Command

Select commands and select Edit Display Rules

Remove Mscrm.HideOnCommandBar rule

Refresh the xml generated and publish the solution.

Helpful post

http://www.develop1.net/public/post/How-to-restore-a-hidden-button-on-the-CRM-2013-Command-Bar.aspx

Hope it helps.

Share It -

Share It -

Share It -

Share It -

Share It -

Share It -

Nishant Rana's Weblog