BSON field 'authenticate.nonce' is an unknown field

MongoDB Atlas
#1

Error [MongoError]: BSON field 'authenticate.nonce' is an unknown field. at Function.MongoError.create (D:\website\node_modules\mongodb-core\lib\error.js:31:11) at D:\website\node_modules\mongodb-core\lib\connection\pool.js:497:72 at authenticateStragglers (D:\website\node_modules\mongodb-core\lib\connection\pool.js:443:16) at Connection.messageHandler (D:\website\node_modules\mongodb-core\lib\connection\pool.js:477:5) at TLSSocket.<anonymous> (D:\website\node_modules\mongodb-core\lib\connection\connection.js:333:22) at TLSSocket.emit (node:events:527:28) at TLSSocket.emit (node:domain:475:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at TLSSocket.Readable.push (node:internal/streams/readable:228:10) at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) { ok: 0, errmsg: "BSON field 'authenticate.nonce' is an unknown field.", code: 8000, codeName: 'AtlasError' }

"mongodb": "^2.2.36",
"mongoose": "^5.1.1",
"mongoskin": "^2.1.0",
#2

couldn’t find any data about this error/issue.

#3

Does your collection contain a field called authenticate? What is the data type of authenticate.nonce? I guess I am wondering if this field is being represented in the sql/relational schema that BIC needs in place.
Are you using on-prem BIC or Atlas BIC? It looks like this is Atlas data based on the error message. If you are using Atlas BIC, you could try to resample the data (found in the cluster config).
What tool are using to connect with BIC? This last question is more out of curiosity and might help with further troubleshooting efforts for this issue.

Best,
Alexi Antonino (Product Manager, BIC & Atlas SQL)

#4

no, my collection does not contain a field called authenticate. it seems to be an internal error in node modules.

#5

also what’s BIC? :sweat_smile: its been 5 days I am not able to resolve this issue

#6

no, my collection does not contain a field called authenticate. it seems to be an internal error in node modules.