HomeBrandsMongoDBDatabase Server & Atlas37
M
37
Moderate
MongoDB · Database Server & Atlas
MongoDB server reported: File Rename Failed.
Quick Answer
Error code 37 on your MongoDB Database Server & Atlas means: MongoDB server reported: File Rename Failed.. This is usually fixable — see the step-by-step guide below.
Affected Models
Applies to all models
MONGO-ATLAS-DEDICATEDMONGO-ATLAS-SERVERLESSMONGO-COMM-6.0MONGO-COMM-7.0MONGO-COMM-8.0MONGO-ENT-6.0MONGO-ENT-7.0MONGO-ENT-8.0
Likely Causes
  1. MongoDB returned code 37 (FileRenameFailed) while processing this request path.
  2. A file-level or persistence-layer operation failed during execution.
  3. Repair/backup state or disk conditions blocked the requested change.
How to Fix It
1
Review logs/telemetry for code 37 (FileRenameFailed) and capture the exact command and parameters that triggered it.
2
Check disk health, free space, and filesystem-level errors on relevant nodes.
3
Validate backup/repair/index-build state before executing mutating operations.
4
Re-run after storage-layer alerts are clean and durability settings are confirmed.
5
Add monitoring for recurring FileRenameFailed events so future incidents are detected and triaged faster.
Pro Tip
This fix requires some technical knowledge. If you're unsure about any step, consider contacting support or a qualified technician.
Related Error Codes
12456
Video Guides
Loading video guides…
Search more on YouTube →