If you’ve ever imported a solution before, the worst is when it doesn’t import properly. Normally, CRM would give you a nice error within the error log regarding what went wrong. Usually there are easy fixes for the issues, such as missing or invalid dependencies or invalid plugin/plugin steps, but, panic ensues when there is no error message in the import solution wizard!
If you ever encounter this error, one of the first things you should check is the SQL server, specifically SQL Replication jobs; as this may be the source of the problem. When you try to import a solution and that solution as well as the SQL Replication job are using the same data, the solution will fail without any specific error referencing the replication job. Unfortunately SQL Replication is not supported with CRM, as it causes changes to the database schema. In a recent case, we saw a replication job that had monitors on SQL views that were changing with this solution, thus when the import wizard tried to drop and recreate the views with additional fields, SQL server would not let it happen.
Once you delete the SQL replication job, the import of the solution will go without error.
To ensure you don’t have similar issues, make sure your developers are aware that SQL server Replication jobs are unsupported and they should instead look at CRM’s API for replication of data fields or records. If they are looking for a broader synchronization scope (i.e. more data) they would need to look at a custom solution tailored to fit their needs, such as SSIS.
In instances where these steps do not resolve the issue, we would encourage you to reach out to our support team as there may be additional issues causing the solution import failure. We hope you enjoyed this blog! For more information, check out our Dynamics CRM education department for even more knowledge!