When Replicating Microsoft Dynamics CRM entities to Microsoft SQL Server you may encounter Replication errors in execution history which mention CrmMigrationSchema. There are specific errors that can occur. See the screenshot example of execution history along with errors and resolutions below.

 

CRM Migration Schema error details

Error: The following error has occurred: Can't discover authority for organization: 72ca329b-ced8-4a5e-ad41-76c2b6ce87e5 from orginsightsapi: https://orginsights.crm.dynamics.com/api/v1/OrgInsightsMetrics/List?OrganizationVersion=9.2.21094.144&LanguageCode=1033:

Cause: When the replication ran, CRM returned the above error which says we were not able to obtain permission for the entity Orginsightsmetrics. This entity is selected to be replicated and has been working but this error has been seen to happen randomly.  

Resolution: Check CRM users permission on that entity. Provide appropriate permissions and test again.

CrmMigrationSchema error details

Error: The following error has occurred: No valid columns passed in the columnset:

Cause: There is a entity selected in the entity list that is not supported. Check the CRM help guide to confirm  Connector for Microsoft Dynamics 365 / CRM

Resolution: The entity is on the exclude entities list but you can still replicate the entity if you choose the all entities option. To resolve the issue, either use the all entities option or uncheck entities that are not supported for selected entities. 
 

CrmMigrationSchema error details

Error: The following error has occurred in the SQL Connector: To accomplish this action, set property RowGuidCol

Cause: The Connector for Microsoft SQL Server cannot alter a table in a Data replication target database to add new columns from the source system 

Resolution: Update the SQL Server user in the connection to have all permissions. Alter, update, create, delete etc. If changing the privileges for the user does not resolve the issue, then some type of restriction is still preventing the addition of new columns to be added. In this case we suggest you work with your SQL DBA to determine why the user cannot alter tables. A SQL profiler trace captured during the replication may provide more information as to why the user cannot alter the table to allow new columns.  
 

CrmMigrationSchema error details

Error: The following error has occurred in the SQL Connector: There is already an open DataReader associated with this Command which must be closed first.

Reason: This error occurs when another replication to the same target database has the same entity selected to be replicated.

Resolution: Ensure only one replication to the same target database has the same entities selected. Selecting the same entity in different replications to the same target database is not supported.  

This article describe several errors that happen with data replication jobs and Dynamics CRM. It includes examples of the errors, the causes, and resolutions.