Forum Discussion

blull's avatar
blull
Frequent Visitor
2 years ago

MongoDB Atlas Data Copy Connectivity

I'm trying to utilize the new MongoDB Atlas connector in Data Pipelines/Copy Data, but have had no luck at all connecting to my MongoDB Atlas database.  It seems to be a connectivity issue or something wrong with my connect string.  Can anyone help with the proper format on setting up atlas as a source?  Things I've tried for the server:

 

  1. mytest.vsd37ej.mongodb.net
    • Internal error has occurred.
      Activity ID: 5c2fb0a3-5eab-4817-9e64-92f478d17401
  2. mongodb+srv://<username>:<password>@mytest.vsd37ej.mongodb.net
    • >Connection to MongoDB server is timeout.
      A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+AreSessionsSupportedServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : "2", Type : "Unknown", State : "Disconnected", Servers : [] }.

It could also be a firewall related issue but I did set a whitelist for 0.0.0.0 in my testing and it didn't make a difference either way. are there set IPs I need to whitelist in Atlas so fabric can communicate?  I 

 

 

5 Replies

  • v-cboorla-msft's avatar
    v-cboorla-msft
    Microsoft Employee

    Hi blull 

     

    We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.

  • BartoloIsmail's avatar
    BartoloIsmail
    Frequent Visitor

    i have also the same issus with my copy activity in microsoft fabric. Should I check if there are specific permissions for Microsoft Fabric to access my mongodb atlas collection? I successfully retrieved data via a Python script and added my IP to the list of IPs. 

     

    • BartoloIsmail's avatar
      BartoloIsmail
      Frequent Visitor

      '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.