Forum Discussion
Error - Using the MongoDB Om-Premise Connector
Hello everyone,
I'm trying to establish a connection between Fabric and an on-premises MongoDB server.
https://learn.microsoft.com/en-us/fabric/data-factory/connector-mongodb-overview
In fact, the scenario involves writing data from Fabric to an on-premises MongoDB NoSQL database.
The connection has been successfully established on the gateway side (with all necessary firewall rules configured).
Then I see the connection in the “Copy Data” section of the “Data Pipeline.” So that means the mapping is working properly.
However, the connection test isn't working...
Of course, the error message doesn't help at all.
For your information, here is the server pattern specified in the gateway connection
mongodb01.example.com:27017,mongodb22.example.com:27017,mongodb03.example.com:27017/?authMechanism=DEFAULT&authSource=xxxxxxxxx
Thank in advance for your help
Have a nice day,
Vivien
11 Replies
Before retrying:
- Database name has no dots
- Database name has no spaces
- Database name is not empty
- Database name is not the server name
- If parameterized, parameter resolves to a clean string
Hello Thomaslleblanc ,
Thank you for your feedback.
When you set up the connection at the gateway, you enter:
Option 1 :mongodb01.example.com:27017,mongodb22.example.com:27017,mongodb03.example.com:27017/?authMechanism=DEFAULT&authSource=xxxxxxxxx
or
Option 2:mongodb01.example.com:27017,mongodb22.example.com:27017,mongodb03.example.com:27017
By "Database name", do you mean what is specified as "AuthSource" ?
If so, in my case there’s just a “-”; the pattern is “xxxx-yyyy”
Thank in advance,
Have a nice day,
VivienHi vivien57
The issue is likely not related to the authSource value or the hyphen in the database name. In Fabric, the Database field in the Copy activity is separate from authSource and must explicitly reference a valid MongoDB database (not blank or unresolved). The more likely issue is the connection string format and how the connector parses it during validation. I would recommend using a standard MongoDB URI format such as: mongodb://mongodb01.example.com:27017,mongodb22.example.com:27017,mongodb03.example.com:27017/?authSource=xxxx-yyyy&authMechanism=DEFAULT
Also verify that the Database field in the Copy activity is explicitly populated, URI parameters are passed using standard & separators, and, if connecting to a replica set, the replicaSet parameter may also be required depending on the MongoDB configuration.
For isolation, it may also help to test temporarily with a simplified single-node connection string.
Regards,
ABD
Hi vivien57
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to Thomaslleblanc and ABD128 for sharing helpful suggestions.
Could you let us know if the suggested solution resolved your issue? If not, please share any additional details so we can assist further.
Best regards,
Community Support Team.Hi vivien57
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.
Thank You.
