MSCRM 2015 – Could not find file ‘C:\Program Files\Microsoft Dynamics CRM\LangPacks\xxxx\sql\7\StoredProcedures\MSCRM\fn_RollupByAccount.sql

MSCRM 2015 is just release in the previous last week. Maybe you come to the problem regarding the following error message:

System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.IO.FileNotFoundException: Could not find file ‘C:\Program Files\Microsoft Dynamics CRM\LangPacks\xxxx\sql\7\StoredProcedures\MSCRM\fn_RollupByAccount.sql

xxxx represents the MSCRM language code as 1031 for German. Here come the solution to proceed the organization upgrade from 2013 to 2015:

The following 3 files are missing for the upgrade to be completed:




The 3 files are actually allready in the filestructure, they are just named in a wrong way.




Please copy those 3 files and rename them. After all the upgrade will proceed as expected. Please note, this is an unsupported workaround. We hope of course, that Microsoft will deliver an appropiated fix for this issue.

This blog is based on .  Thanks for sharing the solution.


Dynamics CRM 2015 – All resources together on one view

Please see the following list with all relevant download resources regarding the new release of Microsoft Dynamics CRM 2015:

Server 2015 –

CRM 2015 SDK –

Email Router –

SharePoint List Part for CRM 2015 –

Microsoft Dynamics CRM 2015 Report Authoring Extension –

CRM 2015 Language packs –

Outlook Client –

CRM 2015 is now available for downlaod

Yes, CRM 2015 is now available for downlaod. See download under This is a big surprise because normally, the online environment comes out before the on premise one. Outlook (, SharePoint List component and Email router is available as well. What’s currently not available are the released Version of Dynamics CRM 2015 SDK, only a pre-released Version.

Integration that Outperforms: SharePoint Integration for Logistics and SCM

See the statement of Magici software to integrate Microsoft SharePoint to the most imported LOB application within the whole organization:

Enterprises that use SharePoint as a content and portal platform often find a need to integrate it with their logistics and supply chain management systems (SCM). Learn how-to overcome integration challenges, automate business processes across diverse systems and benefit from highly scalable integration architecture.

See more in YouTube:

Use a specific system view on search field to filter user results

We have covered into the problem, that CRM 2013 is not using the correct system view to filter appropriate results behind a search field. After investing with Microsoft support, we have identified the following solution:

Create a new WebResource with the following code, and register it to the form’s OnLoad event. (Or, add it to an existing WebResource/OnLoad handler.)
function OnLoad() {      Xrm.Page.ui.controls.get(<the lookup field name>).setDefaultView(“{<your view’s ID>}”); }
You can determine the view’s ID by opening the customization window to edit the view, and finding the ‘id’ parameter in the URL. For example, the ID is highlighted below:
To set the Contact field on an Opportunity to use the “Inactive Contacts” view, the handler would look like this:
function OnLoad() {      Xrm.Page.ui.controls.get(‘parentcontactid’).setDefaultView(“{00000000-0000-0000-00AA-000010001033}”); }

Of course this solution is “as-is” without any warranties, and confers no rights.

Microsoft Dynamics CRM 2013 Online Prices for Switzerland

Since November 2014, new Dynamics CRM 2013 is available for Swiss customers. In my point of view, there is never a overview regarding the services and related prices for Switzerland. After spending some time, I found everything and I would like to share the details:

Microsoft Dynamics CRM Online Professional

The most comprehensive plan for users who need full sales, service, and marketing capabilities of Microsoft Dynamics CRM Online.

CHF 64.10 (by user / month)

Microsoft Dynamics CRM Online Basic

Subscription plan for users who need access to accounts, contacts, leads, cases, reporting, and custom relationship management (xRM) capabilities of Microsoft.

CHF 29.60 (by user / month)

Microsoft Dynamics CRM Online Essential

Subscription plan for users who need access to custom relationship management (xRM) capabilities of Microsoft Dynamics CRM Online.

CHF 14.60 (by user / month)

Enhanced Support for Microsoft Dynamics CRM Online

Microsoft Dynamics CRM Online Enhanced Support Plan includes a fastest response time of <2 hours and eLearning.  Customers must choose either Professional Direct or Enhanced for the same number of seats in which they have licensed.

CHF 4.90 (by user / month)

In addition, there are the following addons:

Microsoft Dynamics CRM Online Additional Storage

CHF 9.90 (by Gb / Month)

Microsoft Dynamics CRM Online Additional Production Instance

CHF 541.70 (by organization instance / month)

Microsoft Dynamics CRM Online Additional Non-Production Instance

CHF 148.00 (by organization instance)

Dynamics CRM 2013 On Premise to Online Migration

Explanation of the Issue

We have done our first migration from a Dynamics CRM 2013 On Premise to Online environment. First, we have mentioned the error “0x80040203- Entity campaignresponse : Quick create is not supported for OOB Activity Entity”.

After investigation into the problem, we have found out, that the entity option “Allow quick create” is enabled in the On Premise environment. This option was not activated in the Online environment and that is the correct setting because Activity entities never have this options enabled.

See the following two print screen from the On Premise and the Online environment:

On Premise





To solve that problem, we have modified the file “Customizaiton.xml” within the exported solution. In the entity definition “Campaigneresponse”, we have changed the metainformation-tag “IsQuickCreateEnabled” from value “1” to value “0”. This solution is finally not supported from Microsoft and should be used as temporary workaround.