You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: All Azure Database Extension Build: 20240219.1 Regression: Previous Release
Repro Steps:
Open Tree View of Attached Database Accounts -> Click Attach Emulator -> Select Azure Cosmos DB for MongoDB API
Check whether succeeds to Attach Emulator.
Expect:
Succeed to Attach Emulator.
Actual:
Failed to Attach Emulator for MongoDB with an error "Server at localhost:10255 reports maximum wire version 2, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)".
More Info:
It does not reproduce on the previous released Azure Databases extension v0.20.1.
Mongo DB version 4.0 has been installed in the Local Machine.
Emulator has been started, with the MongoDB endpoint enabled.
The text was updated successfully, but these errors were encountered:
Amar-QA
changed the title
Failed to Attach Emulator with an error "Server at localhost:10255 reports maximum wire version 2, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)"
Failed to Attach Emulator for MongoDB with an error
Feb 20, 2024
Amar-QA
changed the title
Failed to Attach Emulator for MongoDB with an error
Failed to Attach Emulator for MongoDB with an error.
Feb 20, 2024
Amar-QA
changed the title
Failed to Attach Emulator for MongoDB with an error.
Failed to Attach Emulator for MongoDB with an error
Feb 27, 2024
OS: All
Azure Database Extension Build: 20240219.1
Regression: Previous Release
Repro Steps:
Expect:
Succeed to Attach Emulator.
Actual:
Failed to Attach Emulator for MongoDB with an error "Server at localhost:10255 reports maximum wire version 2, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)".
More Info:
It does not reproduce on the previous released Azure Databases extension v0.20.1.
Mongo DB version 4.0 has been installed in the Local Machine.
Emulator has been started, with the MongoDB endpoint enabled.
The text was updated successfully, but these errors were encountered: