CRM 2013 - Solution Import failure during plugin imports RRS feed

  • Question

  • Hi All,

    We are in the process of upgrading our CRM 4.0 to CRM 2011 and then to CRM 2013 in our test environment. Now we need to test solution import functionality, so during production deployment we will no have any issues.

    Following is the scenario on which  we are facing issue:

     - We have test environment ready with all customizations converted into valid CRM 2013 and in working condition.

     - We have created new vanilla version of CRM 2013 environment and done import organization functionality by taking test environment's database.

     - Now we are trying to import unmanaged solution exported from ready test environment in first point above..

    At this time, we are getting error during processing of Plugin Assemblies. We are having random issues in this. I want to mention here, both database have equal plugins available. Sometimes we are getting duplicate key issue and sometimes it is saying that plugin should be register in isolation mode.

    Are we missing anything? Can't it be possible to do solution import when both have same database available?

    Monday, September 8, 2014 1:26 AM

All replies

  • Hi Ravi,

    Please check if the id that you use to register the plugin/Import the solution is a Deployment Administrator on crm.



    Monday, September 8, 2014 1:30 AM
  • Hi Jithesh,

    Thanks for reply. The ID which we have used in import organization is different than ID used during plugin registration. Both IDs are there in Deployment Administrator. I have removed the plugin (which doesn't have any steps) from the exported solution and now I am getting random issues. Error is there in SDK Message Processing now.

    Do you have any idea about that?

    Monday, September 8, 2014 3:30 AM
  • Hi Ravi,

     Could you please post the exception message that you receive so that we can take a look?



    Monday, September 8, 2014 3:37 AM
  • Thanks Jithesh. But we are getting random issues. I have one assembly called CompiledWorkflow{some guid} which I am not really aware of what it is. Error was saying, its already there in destination organization, so you can not insert duplicate key. I have skipped that, and now its giving isolation mode related errors on SDK Processing messages. Right now we are skipping those also as thinking to register assembiles manually.

    I will let you know if we get any fix error.

    Monday, September 8, 2014 11:23 PM