Error
Error Code:
180
MongoDB Error 180: Bad Perf Counter Path
Description
MongoDB Error 180, "Bad Perf Counter Path," indicates that the database instance on a Windows system is unable to access or locate required Windows Performance Monitor counters. This typically occurs during startup or operation when MongoDB attempts to gather performance metrics, signaling an issue with the underlying OS performance counter configuration.
Error Message
Bad Perf Counter Path
Known Causes
3 known causesCorrupted Performance Counter Registry
The underlying Windows registry entries that define performance counters may be damaged or inconsistent, preventing MongoDB from finding valid paths.
Insufficient Service Account Permissions
The user account running the MongoDB service lacks the necessary read permissions to access Windows performance counter objects or their configuration.
Missing or Unregistered Counter Libraries
Essential Windows performance counter components or DLLs required by MongoDB are either absent or not correctly registered with the operating system.
Solutions
Coming SoonDetailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:
General Troubleshooting Tips
- Check the error message carefully for specific details
- Review recent changes that might have caused the error
- Search for the exact error code in the official documentation
- Check log files for additional context
- Try restarting the application or service