Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi BartoloIsmail ,

Thanks for using Fabric Community.

Here are some steps to troubleshoot the connection and set up MongoDB Atlas as a source:

 

  1. Verify Connection String:
    • Double-check your connection string for typos or incorrect formatting.
  2. Firewall Rules:
    • Ensure your network allows outbound connections to MongoDB Atlas on port 27017 (or the custom port you might be using). Check your Data Pipelines service's network configuration and any firewalls in between.

 

Additional Tips:

Consider increasing the timeout value in your connection string using connectTimeoutMS parameter. This might help if there's a slight delay in establishing the connection.

Docs to refer - Configure MongoDB Atlas in a copy activity - Microsoft Fabric | Microsoft Learn

Hope this helps. Do let us know incase of further queries.

BartoloIsmail's avatar
BartoloIsmail
Frequent Visitor
2 years ago

Hi Anonymous ,

this morning I tried to input 00000. IP address in order to allow all access for everyone, and now I can conclude that it's Microsoft Fabric that doesn't want to connect. I have an internal error.

 

I found a similar message (https://community.fabric.microsoft.com/t5/Data-Pipelines/MongoDB-Atlas-Data-Copy-Connectivity/m-p/3566910) regarding the issue I'm facing. Let me explain: I'm trying to copy data via a pipeline using Microsoft Fabric to retrieve my MongoDB Atlas collection. I had an error that I corrected by adding a parameter that allows access to all IPs to access the MongoDB service. After running the test, I now encounter a new error that appears (progress... :)). I'm coming to you to ask if you could explain where this new error might be coming from. Thank you for your help.