CRM 2011 Solution Import Fails with error “Object reference not set to an instance of an object” due to missing relationship “goal_DuplicateBaseRecord”

I had recently worked with a customer that was running into errors when trying to import a solution into some of their organizations. The solution import would fail with the following error message.

Entity Relationships        goal_DuplicateBaseRecord                Failure    0x80044150    Object reference not set to an instance of an object.

This goal_DuplicateBaseRecord relationship would exist in the source organization, but not the target organizations which caused this exception. We found that this relationship will be created if the duplicate detection had been toggled on and off within the goal entity. Once the relationship exists you will only be able to import that organizations solution into other orgs which the relationship exists.

After working with the support team we found that the goal_DuplicateBaseRecord relationship should exist on the Goal entity by default since it had Duplicate Detection enabled. This has been logged as an issue and will be fixed in one of the future updates.


If you are seeing this issue you can complete these steps to create the missing relationship.

1. Open the organization which you are getting the error message and go to Settings–Customizations-Customize the System.

2. Expand Entities and click on the Goal Entity.

3. Within the Goal properties UnSelect Duplicate Detection and Click Save.


4. Now Select Duplicate Detection to enable the feature and Click Save Again. This process will create the missing relationship to the DuplicateRecordBase table.

If you review the 1:N Relationships the missing relationships will now show up after the setting was toggled. You will now be able to import the solution without receiving the error message.

Before (Missing Relationships):



After (Relationships Created):



Please leave a comment if you found this post helpful and if it resolved the issue you were facing.



Jeremy Morlock

Microsoft Premier Field Engineer

Comments (7)

  1. MHL says:

    Thank you, I was experiencing the same issue and this helped me tremendously.

  2. JT says:

    Nope this did not help. Got a new error now. goalrollupquery_DuplicateBaseRecord

  3. BenK says:

    This did the trick! Useful tip, many thanks.

  4. SL says:

    It fixed first error now comes back with

    The entity relationship role of the referencing entity is required when creating a new one-to-many entity relationship new_goalrollupquery_DuplicateBaseRecord.

  5. SL says:

    I went to solution.xml found goalrollupquery_DuplicateBaseRecord EntityRelationship node and goalrollupquery_DuplicateMatchingRecord deleted them and it went fine

  6. Andy Gray says:

    To fix the above issues with goalrollupquery, perform a similar action described in the article on the "Rollup Query" entity. This will create the missing relationships.

Skip to main content