RVR-MSSQL-RDBMS-207

1. Issue Summary

   • The error "Failed because of mismatch between versions" with Error Code: RVR-MSSQL-RDBMS-207 relates to a synchronization issue between Rivery and the MSSQL server due to version mismatches. This commonly occurs when the change tracking or change data capture setup on SQL Server doesn't align with what Rivery expects, leading to data extraction failures.

2. Action Steps:

   • Verify Minimum Valid Version: Check if the issue is caused by min_valid_version being zero or if last_sync_version is missing. Without these, the change tracking data cannot be retrieved properly, and you might need to reinitialize the table【4:0†source】.
   • Investigate Cleanup Processes: Automated cleanup processes might remove required change tracking data. Review the MSSQL server's logs for any cleanup process that might affect synchronization【4:0†source】.
   • Examine SQL Server Agent: Ensure the SQL Server Agent is running if your server is on an Azure SQL Server Virtual Machine. This may require starting the service manually【4:15†source】.
   • Reinitialize the Table: If synchronization versions are missing or mismatched, reinitialize the table from within Rivery. Navigate to your River's Schema and choose "Set initiate migration for all tables".
   • Review Table Activities: Check for frequent updates/deletions in the table without corresponding inserts, which might manage how change tracking data is retained and could lead to malfunctions【4:0†source】.
   • Check for Concurrency Issues: Ensure that there’s no concurrent process trying to use the same change tracking information, as this could lead to conflicts【4:0†source】.

3. External References:

   • For more detailed guidance, visit Rivery's official documentation on SQL Server Connection, particularly the sections dealing with Change Tracking and troubleshooting Rivery MSSQL integrations【4:12†source】.

If the issue persists or you need further assistance, please open a ticket with Rivery support.