Error: unknown type of write result, cannot check ok

Emre Alparslan shared this problem 2 years ago
Solved

After updating to version 5.1.9(5.1.9), I get this error after every operation (update, delete..).

Example:


// run script failed At 05:27:54.604 PM


db.getCollection("products").update({_id:ObjectId("5d19f719a76ee9060475cf91")},

{$set:{"logo":"images/6942ffee-aceb-4046-89a5-fd0c6a499676.png"}})


// script result (only top 10) (duration: N/A)


{

"message" : "unknown type of write result, cannot check ok: { \"nMatched\" : 1, \"nUpserted\" : 0, \"nModified\" : 0 }",

"stack" : "Error: unknown type of write result, cannot check ok: { \"nMatched\" : 1, \"nUpserted\" : 0, \"nModified\" : 0 }" +

"at _getErrorWithCode (evalmachine.<anonymous>:2:149673)" +

"at Object.zNJWp (evalmachine.<anonymous>:1:318113)" +

"at doassert (evalmachine.<anonymous>:1:319686)" +

"at Object.uqtMa (evalmachine.<anonymous>:1:354763)" +

"at Function._0x18615e.(anonymous function) [as writeOK] (evalmachine.<anonymous>:1:441305)" +

"at MongoHandler.isMongoWriteResult (/Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/backend/mongoHandler.js:710:36)" +

"at /Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/backend/mongoHandler.js:754:28" +

"at tryBlock (/Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/node_modules/asyncawait/src/async/fiberManager.js:39:33)" +

"at runInFiber (/Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/node_modules/asyncawait/src/async/fiberManager.js:26:9)",

"code" : {

"nInserted" : 0,

"nUpserted" : 0,

"nMatched" : 1,

"nModified" : 0,

"nRemoved" : 0

},

"_script" : "db.getCollection(\"products\").update({_id:ObjectId(\"5d19f719a76ee9060475cf91\")}," +

"{$set:{\"logo\":\"images/6942ffee-aceb-4046-89a5-fd0c6a499676.png\"}})"

}

Best Answer
photo

We have worked out a hotfix(5.1.10) to resolve this issue, please download and give it a try.

https://nosqlbooster.com/downloads

Replies (2)

photo
2

We have worked out a hotfix(5.1.10) to resolve this issue, please download and give it a try.

https://nosqlbooster.com/downloads

photo
1

Seems like the issue is fixed in 5.1.10. Thanks for quick response!

Leave a Comment
 
Attach a file