Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
Importing managed solution issue

Proposed Answer Importing managed solution issue

  • Tuesday, 6 March 2012 2:52 PM
     
     
    Sign In to Vote
    0

    Hi all,

       I have an existing unmanaged solution and i have imported an managed solution(added custom entities and nothing deleted from exisiting unmanaged solution).The publishers/rollups for all the managed and unmanaged solution are same.

    issue...

    An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft 

    Found 179 dependency records where unmanaged component is the parent of a managed component. 
    First record (dependentcomponentobjectid = f521e701-2967-e111-9631-005056c00008, 
    type = AttributeMap, requiredcomponentobjectid = 0014c275-2867-e111-9631-005056c00008, 
    type= EntityMap, 
    solution = bc5d99ea-779a-4747-807a-29769d598bcc).  


    Thanks & Regards Vijji

     

All Replies

  • Tuesday, 6 March 2012 3:32 PM
     
     Proposed Answer
    Sign In to Vote
    1

    You cannot import a managed solution if it contains components that already exist in the organization in an unmanaged state. So if in the managed solution there are any custom components that are also in the unmanaged solution, the import will fail until you remove either the unmanaged component or the managed component.

    Kirsten


    • Edited by KirstenClapham Wednesday, 7 March 2012 9:14 AM typo
    • Proposed As Answer by vasubabuk Monday, 18 March 2013 12:21 PM
    •  
     
  • Wednesday, 7 March 2012 10:40 AM
     
     
    Sign In to Vote
    0

    Hi kirsten,

      This might the issue of managed existed in unmanaged mode in organaisation..

    For understanding... i have  taken a new organization say "abc" a fresh with default customisation .... i  imported the managed solution... imported successfully..

    the next thing i have done is uninstalled(deleted)  the managed solution from the solution list,now what i observe is ......

    Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: 
    attributemap With Id = c14ebeb4-f367-e111-9631-005056c00008 Does Not ExistDetail: 
    <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
      <ErrorCode>-2147220969</ErrorCode>
      <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
      <Message>attributemap With Id = c14ebeb4-f367-e111-9631-005056c00008 Does Not Exist</Message>
      <Timestamp>2012-03-07T23:33:50.9133594Z</Timestamp>
      <InnerFault i:nil="true" />
      <TraceText i:nil="true" />
    </OrganizationServiceFault>

     

    i didnt get why attribute map is checked while deleting solution. 

    Thanks & Regards Vijji

     
  • Tuesday, 13 March 2012 1:27 PM
     
     Proposed Answer
    Sign In to Vote
    1

     Had the same error and in my case the reason for it was custom Attribute Mappings between entities. It seems that I cannot have a custom mapping from an entity outside of a managed solution to an entity it a managed solution.

     When you import the managed solution for the first time where the entities already exists (in my example I'm upgrading my solution from crm4 to crm2011) the entities are considered to be unmanaged therefore the error. At least this is what I think :)

     As a workaround I did the following :

    Edited customization.xml

     I unzipped the solution and edited customization.xml, searched for <AttributeMaps> and replaced that tag with <AttributeMaps /> removing any related attribute mapping definition. After editing I made a new zip with the solution.

    In the System Receiving the Solution

     Removed the corresponding attributemappings in the crm system, if not removed you run into trouble when importing the solution WITH the attribute mappings.

    After these changes I was able to import the solution as managed. I Published everything and and imported the original file with the attribute mappings included.


    • Edited by Kjell L Tuesday, 13 March 2012 1:30 PM
    • Proposed As Answer by Kjell L Tuesday, 13 March 2012 4:23 PM
    •  
     
  • Friday, 23 March 2012 8:49 AM
     
     
    Sign In to Vote
    0

    Hi Vijji,

    Any luck with this error, I am having the same error when I was trying delete a Managed solution.

    thanks

    Thomas T(MCBMSS) If you find this post helpful then please "Vote as Helpful" and "Mark As Answer".

     
  • Sunday, 6 May 2012 10:59 PM
     
     
    Sign In to Vote
    0

    Kjell L,

    Thanks for the workaround!  After trawling through the database trying to find the relevant dependentobjects and mappings, I eventually found your response in this forum...but only after telling Google to display similar results!

    By viewing all of the <AttributeMaps> in the customization.xml file, you can figure out which maps need to be deleted in the target CRM instance...and thankfully, deleting these maps does not delete data, as we'll be deploying this new solution into Production shortly.

    Ironically, my import log always said I had 2 dependency records, even though there ended up being about 7 attribute maps that I had to remove.  I thought I was making progress when the GUID's kept changing, but I eventually hit a wall that I was only able to get around after reading your post.  So thanks again...definitely worked for me.

    Andrew

    Kind regards, Andrew www.cevian.com.au

     
  • Thursday, 6 September 2012 6:02 PM
    Owner
     
     Proposed Answer
    Sign In to Vote
    0
    http://blogs.msdn.com/b/emeadcrmsupport/archive/2012/09/06/cannot-import-managed-solution-after-upgraded-from-dynamics-crm-4-0-to-crm-2011.aspx

    Regards, Donna

     
  • Monday, 22 October 2012 12:59 PM
     
     
    Sign In to Vote
    0

    This was also fixed in Rollup10

    Assume that you try to import a solution that converts unmanaged components to managed components. If the managed solution contains entity maps, the solution import fails. Additionally, you receive an error message that resembles the following:
    Found 1 dependency records where unmanaged component is the parent of a managed component. First record (dependentcomponentobjectid = 36fc8cb9-3b5e-e111-a9ca-00155d42da0e, type = AttributeMap, requiredcomponentobjectid = 908685b1-3b5e-e111-a9ca-00155d42da0e, type= EntityMap, solution = e70812bd-e237-4e3a-9517-546b77024319)

    Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd Microsoft Community Contributor Award 2011

     
  • Monday, 11 March 2013 12:03 PM
     
     
    Sign In to Vote
    0
    Yes u cannot import an managed solution so,while exporting ur solution export it in unmanaged solution and then import  it .Before that delete the managed the solution.