locked
Error during Update of a managed solution RRS feed

  • Question

  • Hi,

    we tried to Update a manged solution in CRM 2011 RTM with a newer version. The Import fails with the message

    A managed solution cannot overwrite the AttributeMap component with Id=0765e87f-cd53-e011-bb82-00155d397001 which has an unmanaged base instance.  The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged AttributeMap component on the target system, and now a managed solution from the same publisher is trying to install that same AttributeMap component as managed.  This will cause an invalid layering of solutions on the target system and is not allowed.

    The only unmanged customization in the target system are two Workflows/Processes where the Queue-Lookups have been adjusted to the system.

    A similar issue was reported in http://social.microsoft.com/Forums/en-US/crm2011beta/thread/4d92c7a4-9a1f-47cd-9896-2268b927c9bf
    It implies there might be a bug. Is there a workaround? When can we expect the issue to be fixed.

    Thanks in advance for any help.

    Wednesday, March 23, 2011 9:00 AM

Answers

  • The problem was, we customized the field mappings of opportunityproduct - quotedetail. Since there is an official KB (http://support.microsoft.com/kb/914921/en-us), I think this might be kind of supported.

    Now the first import (managed) of the solution suceeded. After the changes described above, the update failed due to the mappings.
    The resolution was to extract the exported solution and remove the Field mapping from the customizations.xml, and then importing the solution. This somehow feels not very "supported" to me :-( But at least I finally was able to update the solution.

    By the way, deleting all solutions from the system (as I mentioned: they all were managed except one containing two workflows) and then importing the newer version of the solution ended up giving the same error as the original update attempt.

    Friday, March 25, 2011 6:53 AM

All replies

  • It appears to be saying that your solution you are trying to upgrade is not managed, but I imagine your actual updated solution is.  You won't be able to upgrade your base solution if it is unmanaged. 


    Jamie Miley
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!
    • Proposed as answer by Jim Glass Jr Wednesday, March 23, 2011 4:00 PM
    • Unproposed as answer by Frank Bursitzke Thursday, March 24, 2011 7:45 AM
    Wednesday, March 23, 2011 2:10 PM
    Moderator
  • Actually the original solution has been imported managed. Then I needed to create an unmanaged solution with two of the workflow that refered queues, which could not be automatically resolved during the import and thus not activated.
    In the next step the original solution was updated in the development system (a change in a JavaScript and an updated report), the version number was increased and the solution was exported managed. But when I try to import the managed solution, which should update the existing managed solution, the error occurs.

    Thursday, March 24, 2011 7:02 AM
  • Take a look at the {org}_MSCRM database in Sql Management Studio and look at the "solutionbase".  You will be able to see exactly what solutions are installed in the system and what is managed "ismanaged=1" or not "ismanaged=0"

    Thanks, let me know what you find.


    Jamie Miley
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!
    Thursday, March 24, 2011 4:05 PM
    Moderator
  • The problem was, we customized the field mappings of opportunityproduct - quotedetail. Since there is an official KB (http://support.microsoft.com/kb/914921/en-us), I think this might be kind of supported.

    Now the first import (managed) of the solution suceeded. After the changes described above, the update failed due to the mappings.
    The resolution was to extract the exported solution and remove the Field mapping from the customizations.xml, and then importing the solution. This somehow feels not very "supported" to me :-( But at least I finally was able to update the solution.

    By the way, deleting all solutions from the system (as I mentioned: they all were managed except one containing two workflows) and then importing the newer version of the solution ended up giving the same error as the original update attempt.

    Friday, March 25, 2011 6:53 AM
  • Remove the the EntityMap tag from Customization xml

    <EntityMap>

    <EntitySource>lead</EntitySource>

    <EntityTarget>contact</EntityTarget>

    <AttributeMaps>

    <AttributeMap>

    </AttributeMap>

    </AttributeMaps>

    </EntityMap>




    • Edited by Saddamkhan Monday, February 5, 2018 5:35 AM
    Monday, February 5, 2018 5:35 AM