Forum Discussion
Error - Using the MongoDB Om-Premise Connector
Hi 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
Hello ABD128 ,
Thank for your help.
With the suggested connection string, I get this error (which already seems clearer and more specific).
I tried using a single-node setup, but it doesn’t work.
I’d say we’ve made some progress with the new errors, but for the moment I can’t find.
Thank in advance,
Have a nice day,
Vivien
Hi vivien57
That’s useful feedback, because it confirms the issue is not related to the replica set syntax or multi-node configuration. The newer error also makes it clearer that Fabric is rejecting URI-style options in the Server field itself, so the connector is at least validating the input more specifically now.
At this stage, the key points to verify are:
Use only the host:port value in the Server field (no mongodb://, no authSource, no query parameters)
Configure authentication separately in the connection settings/gateway
Explicitly populate the Database field in the Copy activity with a valid MongoDB database name Validate that the MongoDB user has permissions on both the authentication database and the target database.
Since the single-node test also fails, this may now point more toward a limitation or compatibility issue between the Fabric MongoDB connector and your MongoDB authentication/topology configuration through the on-premises gateway.
Regards,
ABD
Hello ABD128 , v-karpurapud ,
I have received your messages and thank you for them.
I haven’t had time to make any progress on this issue, but it remains unresolved for the time being.
I will keep you informed as soon as possible.
Thank you again for your help,
Have a good day,
Vivien
Hi vivien57
Thanks for the update. Hope your issue gets resolved soon. when it does, please share the insights with the community as it can be helpful to others.
Regards,
Microsoft Fabric Community Support Team.
