Strange error when deleting managed Solution

Strange error when deleting managed Solution

Seems like that Dynamics 365/CRM doesn’t catch all dependencies for managed solutions. This is how you can find and remove one of the tricky ones I got when uninstalling a managed solution which was:

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: During Solution Uninstall of Solution Id [solution-guid], cannot find any instances of the component with Component Id c97cd9d7-a0fa-4ed5-b360-3c2ad998a620 and Component Type 2.Detail: 
<OrganizationServiceFault xmlns:i=”” xmlns=””>
  <ErrorDetails xmlns:d2p1=”” />
  <Message>During Solution Uninstall of Solution Id [solution-guid], cannot find any instances of the component with Component Id c97cd9d7-a0fa-4ed5-b360-3c2ad998a620 and Component Type 2.</Message>
  <ExceptionSource i:nil=”true” />
  <InnerFault i:nil=”true” />
  <OriginalException i:nil=”true” />
  <TraceText i:nil=”true” />

After some thinking I figured that this was probably a reference to an attribute (Component type = 2) with the Guid = c97cd9d7-a0fa-4ed5-b360-3c2ad998a620 so I opened another attribute and then cut-n-pasted the url. And it seemed that you didn’t have to worry about the entity guid:


Change <onlineorgname> to your org, and <globalcrmcenter> to the crm-subdomain you are using, which for EMEA is crm4.

You will then see the field editor, and can then show the dependencies of the field and remove all of them manually to make sure they are not bothering the Solution uninstall. After that “publish all” and retry removing the solution.

Gustaf Westerlund
MVP, Founder and CTO at CRM-konsulterna AB

Making CRM stick by using Dr. John Kotter 8 Step method – part 3 – Creating a sense of Urgency

Making CRM stick by using Dr. John Kotter 8 Step method – part 3 – Creating a sense of Urgency

This is the third part of the series of posts in the series where I am discussing how to use the Kotter 8 steps of change method when implementing CRM in an organization. The previous posts can be found here:
Part 1 – Justification
Part 2 – Overview

“Yeah, we had planned to bring up the decision for budgeting the new CRM system at the board meeting, but we had so many urgent issues that we just didn’t have time. Maybe next time…”

Organizations everywhere are choked, especially the successful ones, the ones that have the resources to invest in CRM systems. The effect of this is that everyone can only work with the tasks at the top of their priorities. The first step of Kotter’s 8 steps of change, is to create a sense of urgency. In the case of implementing CRM, this means that we have to be very specific about the effects of what will happen if do not implement this right now.

When doing this, we have to, as always, understand the receiver, understand this party’s values and goals and try to address these. For instance, if the CEO is a very numbers oriented person you might try to work out how much time each sales person might save by using the new CRM and hence be able to put into working with selling more and generating x-% more income. If the CEO is more of a strategy and visions person, you might show her all the abilities she will get with the system and describing all the strategic advantages of this.

The bottom line is, you need to get the people with the decision power and the money to understand the importance of the CRM implementation project, in order for the project to be properly prioritized. If not, you risk being prioritized as number 11 in the list of the 10 item on the board meeting. And that dial does not go to 11.

Gustaf Westerlund
MVP, CEO and owner at CRM-konsulterna AB

Making CRM stick by using Dr. John Kotter 8 Step method – part 2 – Method overview

Making CRM stick by using Dr. John Kotter 8 Step method – part 2 – Method overview

This is the second part in the series on how to make CRM implementations stick in an organization by using the 8 step method described by Dr. John Kotter of Harvard.

The first posting treated the fact that many organization do not consider a CRM implementation a change to the organziation of such a magnitude that it requires a change mangement approach such as the 8 step method. I think that it gives ample evidence for the reasons for why this is not so and that as many as a quarter of all failed CRM Projects could probably have been helped with better change management.

Kotter describes the following 8 step method can in broad terms be described in the following picture:

The Kotter 8 steps of Change

The method required that you complete each step before moving to the next step. It is hence not a toolbox from which you can pick and choose the things which are easy to implement.

As the method is very general and treats many types of organizational changes I will attempt to give some examples of typical problems and suggestions from a CRM implementations perspective.

In the following parts I will discuss the steps in detail, but in short they are:

Step 1: Establishing a Sense of Urgency – many organizations have lots on their tables. If you want your CRM Project to be prioritized and have the resources required, you had better make sure people understand that they need the new CRM system RIGHT NOW. Every week without it is $$$ lost.

Step 2: Creating a Guiding Coalition – You need the backing of the right people to have a successful Project. A CRM Project without the CEO, Head of Sales, Head of Customer Service, CIO will have some issues.

Step 3: Developing a Change Vision – You need to sell the CRM implementation to the people who are going to use it. You need to create a very clear and appealing vision of where the implementation is going.

Step 4: Communicating the Vision – The vision is not going to distribute itself to the users. Create an internal marketing plan for how to get the message out to all users.

Step 5: Empowering Broad-based Action – Make sure that who want to act on the vision can and are not hindered by technology, old procedures, backward colleagues etc.

Step 6: Generating Short-term WinsPlan for short term wins. Otherwise the risk of being stopped in your tracks Before generating anything substantial is large.

Step 7: Never letting up – Make sure to keep the pressure. There might be bugs, some people might revert to Excel or stop using the system. Monitor usage.

Step 8: Incorporating Changes into the Culture – Not until the CRM system is truly a part of the Company Culture, a part of the management meeting, board meetings, sales meetings, will you have fully succeeded.

The next part in this series will be on the first step of this, the important part of establishing a sense of urgency.

You can find Dr. John P. Kotter’s website here:

If you would like to read his excellent book, it is quite easy to find, for instance here:

Gustaf Westerlund
MVP, CEO and owner at CRM-konsulterna AB

Making CRM stick by using Dr. John Kotter 8 Step method – part 1 – Justification

During the CRM UG Summit I held a presentation on the subject of how to use the method described by Harvard professor John P. Kotter called the 8 Steps of Change to aid in the implementation of CRM in an organization. This is the first blog entry in a series which will discuss this subject. This first post will be on the question of if using this method is even justified?

Many companies do acknowledge that major change in the organization, like a fusion, changing from line to matrix organization, and so on, however, there are many companies that do not acknowledge that the implementation of a new CRM system is a change of such a substantial degree that it does require it to be handled as a change management Project.

If you are not already aware of the failure rates of CRM Projects, do have a look at the following links:

The numbers vary, if 70% failure or 30%, but the fact is that a substantial amount of Projects do fail and it is important to be humble to this in order to attempt to mitigate the possible risks of derailing the CRM investment.

Forrester researched 150 companies to find out which problems they were facing in their CRM initiatives as described here:

In short the problems can be divided into the following areas:

  • Creating a CRM strategy – 18% strategy,
    • inadequate deployment methodologies (40%)
    • poorly defined business requirements (25%)
    • lack of alignment on objectives (18%)
  • Re-architecting customer-facing processes – 27%
    • including technical/integration difficulties in supporting company processes (48%)
    • poor business process design (31%)
  • Selecting technology – 33%
    • perceived shortcomings in vendor solutions (30%)
    • a lack of skills needed to implement the solution (23%)
    • system performance shortfalls (19%)
  • Implementing customer-centric behaviors – 22%
    • slow user adoption (49%)
    • poor change management and training (36%)
    • difficulties aligning culture with new ways of working (15%) 

Several books could be probably be written based on this. From an implementation perspective, we can note that about 25% the companies, seem to be having no issues major problems with getting their CRM Strategy correct, they have managed to re-architect their processes and the have overcome all Technical issues, but still their issues lie with the implementation of CRM within the organization. If this is not justification enough that CRM is and requires dedicated and very deliberate change management within the organization.

As I Work as a Consultant, often contracted to implement CRM for a Customer, I would also like to note that Managing change within the organization is not something a temporary external party can do, why it is important to assign internal Resources at the implementing organization to drive the change management Project.

A final note, these numbers might be demoralizing if you are looking at starting you CRM Project or have started it, but I would suggest you look at it in another light. By seeing the problems and errors that others have faced and being open and transparent about your own issues you have a better chance of avoiding these pitfalls. I talked to one of the project leaders for one of the biggest infrastructure Projects in Stockholm which will be completed Before time and within budget. I asked her if she could give me one or two reasons why they were doing so well and she answered:

  • We have very senior and technically experienced people in the Project leadership committee
  • We have been very risk aware from the start, and have had weekly risk meetings

Gustaf Westerlund
MVP, CEO and owner at CRM-konsulterna AB

US Judge orders MSFT to hand over data stored in the EU

As I have previously discussed (on Software Advice in this article) the US laws regarding the rights for the US legal authorities to order US owned companies to hand over data is very strong. Hence, if one has sensitive data that might be of interest to any government agencies in the US, one should think once or twice about storing it in a data center owned by a US company (like, Amazon, Microsoft, Google etc.).

A recent case in in New York has shown that this is not on theory but very much practice. In this case regarding an email account probably on however the difference to or CRM Online is purely academic.

On the positive side, Microsoft are fighting back trying to protect their customer, something I am very happy about. I do hope they do this for all customers.

The other direct positive side to this of course, is that Microsoft CRM can be aquired from other sources than from companies based in USA. For instance a standard CRM On-premise installation, or a partner hosted installation, which there are many service providers of, like Midpoint and our my own company CRM-Konsulterna in Sweden. on the other hand, do not have this option, so if you have sensitive data, be careful, it might be ordered into the wrong hands.

Gustaf Westerlund
MVP, CEO and owner at CRM-konsulterna AB