SQL on prem mirroring cryptic error

[ptmk25]

when trying to configure mirroring in fabric to an on prem sql db

error:

configuring replication: Axios Error network error

[ptmk25 · Accepted solution]

thanks for all your help, this was actually resolved once we bumped up to Fabric admin role

[v-prasare]

Hi @ptmk25  ,

We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

@spaceman127, @Shai_Karmani & @DaleT ,Thanks for your prompt response

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support

[spaceman127]

Hi @ptmk25,

It would be best if you could give us a little more information so that we can help you.
Otherwise, we're just guessing in the dark.

Information such as which version of SQL Server you are using would be very helpful.

Here is some Microsoft documentation on mirroring.

You can choice which mirroring are using.

https://learn.microsoft.com/en-us/fabric/mirroring/overview

Best regards 

[Shai_Karmani]

Some info is missing but my guess based on what is provided:

This error is coming from the Fabric frontend  when the browser or on-prem gateway cannot reach the mirroring service, not from SQL itself.

Some first steps to troubleshoot that:
Check that your on-prem data gateway is online and in the same region as your Fabric capacity, and that the SQL data source test passes. Then verify from the gateway machine that outbound HTTPS to the Fabric endpoints is not blocked by firewall or proxy. 

Shai Karmani | Data & Analytics

If it helped  please mark as resolved & give a kudo so others can find it too.

Let’s connect on LinkedIn

[DaleT]

Hi,

The information here is insufficient and unclear. Since this is a scenario between Fabric and On-premise SQL, I would suggest as follows: 

1. Check the logs in the Data Gateway. Enable the detailed log if necessary. 

2. Catch the SQL DB queries to see what really is happening. Use SQL Profiler if it's SQL Server.

3. Try to connect the DB from other places. Make sure it's connectible from Fabric.