CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist
Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise.
Ronald Lemmon already posted the same issue on his blog:
http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html
I expected it to be fixed with SP1 but it is still happening every now and then.
With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore.
Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated.
What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system.
To find out the id of the target solution you can simply query the SolutionBase table and look it up there. Once you have the true id you can go ahead and update the records of the false solution ids with this query:
Now you should be able to import and update the target solution.
Ronald Lemmon already posted the same issue on his blog:
http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html
I expected it to be fixed with SP1 but it is still happening every now and then.
With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore.
select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID'
Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated.
What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system.
To find out the id of the target solution you can simply query the SolutionBase table and look it up there. Once you have the true id you can go ahead and update the records of the false solution ids with this query:
DELETE FROM ProcessTriggerBase WHERE SolutionId= '12ac16ec-41d5-1685-a230-0b1c31499250'
Now you should be able to import and update the target solution.
Hi Andreas- I thought it is worth mentioning that I had this issue and although I found your blog very helpful it is a little confusing unless I am missing something. In my case, it was a 3rd party managed solution that wouldn't import and it failed on an HTML web resource. I found the web resource in the database, then I looked up the target solution ID in the solutionbase table, then I updated the solution ID for the offending web resource record. I did not need to run your delete statement. Not sure if this is just a typo. I logged a call with MS support and they instructed me to to it this way. I just thought it is worth noting to avoid confusion. Unless in your example this is actually what you had to do.
ReplyDeleteHi all,
ReplyDeletefortunately this thread brought on the right track to figure out why I was getting the same error message. In my case it must have happened that applying a solution upgrade did not complete properly (my guess for the cause). The Metadata was full off entries referring to the "bad" solution GUID (MetadataSchema.Entity, MetadataSchema.Attributes,...). I went and deleted all rows referencing the solution GUID from the log and then I was able to import the new version of the solution.
Hi James, in my and Sigrun's case we had to delete it. Thanks for leaving your comment. It might help others as well.
ReplyDelete