How to Fix 'Collection Not Found' Error in MongoDB

The collection not found error in MongoDB happens when you try to access a collection that does not exist or is misspelled. To fix it, ensure you are using the correct database and collection name exactly as created, including case sensitivity.

Why This Happens

This error occurs because MongoDB cannot find the collection you are trying to use. This usually happens if the collection name is misspelled, the collection was never created, or you are connected to the wrong database.

javascript

const db = client.db('myDatabase');
const collection = db.collection('userss'); // typo in collection name
const docs = await collection.find().toArray();
console.log(docs);

Output

MongoError: collection userss not found

The Fix

Check the exact collection name in your database and correct any typos. Also, confirm you are connected to the right database before accessing the collection. MongoDB collection names are case sensitive.

javascript

const db = client.db('myDatabase');
const collection = db.collection('users'); // correct collection name
const docs = await collection.find().toArray();
console.log(docs);

Output

[{ _id: ObjectId("..."), name: "Alice" }, { _id: ObjectId("..."), name: "Bob" }]

Prevention

Always verify collection names by listing collections in your database before querying. Use consistent naming conventions and avoid typos by copying collection names directly from your database tools. Consider adding checks in your code to confirm collection existence before operations.

javascript

const collections = await db.listCollections().toArray();
console.log(collections.map(c => c.name));

Output

["users", "orders", "products"]

Related Errors

• Database not found: Happens if you connect to a wrong or non-existent database.
• Authentication failed: Occurs if your user lacks permission to access the collection.
• Empty result set: Collection exists but has no documents, which is different from collection not found.

Key Takeaways

Ensure the collection name is spelled exactly as in the database, including case.

Confirm you are connected to the correct database before accessing collections.

List collections programmatically to verify their existence before querying.

Use consistent naming conventions to avoid typos and confusion.

Check user permissions if you suspect access issues causing collection errors.