Mirroring Error

Hi lfparaujo 

Welcome to the Microsoft Fabric Forum. Also, thank you gslick for your response.
 

The "Internal System Error” encountered during SQL Server mirroring in Microsoft Fabric usually indicates a platform-level issue rather than a user misconfiguration, especially if gateway settings have been verified. This error, often accompanied by codes such as a mirror artifact ID, suggests an internal service disruption or compatibility conflict.

Check the Microsoft Fabric service status through the or the Azure Service Health dashboard. Even if no outage is reported, these errors can result from transient backend issues, and retrying after 15–30 minutes can often resolve the problem without intervention.

Ensure the on-premises SQL Server environment meets Fabric’s compatibility requirements. Also, verify that SQL Server is version 2016 or later, that TCP/IP is enabled, and that the connection uses SQL authentication. Deprecated features such as TEXT, NTEXT, IMAGE, or unsupported data types may also cause replication failures. It is recommended to inspect the schema for these data types and run a DBCC CHECKDB command to confirm the database integrity.

Even the gateway configuration may appear correct, it may be useful to restart the on-premises data gateway service and revalidate the data source settings in the Power Platform admin center. Rebinding the data source in Microsoft Fabric and testing the connection can help eliminate any hidden connectivity issues.

If the issue persists after these steps, consider deleting and recreating the mirrored database, starting with a small subset of tables to isolate any schema-related problems.

If this response resolves your query, kindly mark it as Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.

Thank You!