SolarWinds Platform Web Console error "Warning: Fatal Error 9001 occurred at MM/DD/YYYY HH:MM. Note the error and time, and contact your administrator."

12/1/2025 5:36 PM

12/1/2025 5:36 PM

Warning: Fatal Error 9001 occurred at MM/DD/YYYY HH: MM. Note the error and time, and contact your system administrator.

Additionally, you may receive a warning within the WebUI stating that "Database maintenance started on MM/DD/YYYY has finished with errors."

 

Similar errors can be found in the  Orionweb and swdebugmaintenance logs in C:\ProgramData\SolarWinds\Logs\Orion.

Hybrid Cloud Observability

The "Fatal Error 9001" indicates an issue occurring at the SQL Server database level. It is often related to database corruption or unexpected interruptions during database operations.

 

In this case, the error appears in conjunction with database maintenance tasks, such as the stored procedure adm_dbm_ADM_ProcessingQueue_DeleteOrphans failing to execute properly.

 

Database maintenance activities—like index rebuilding, statistics updates, or cleanup jobs—can sometimes cause temporary locking, blocking, or resource contention on the database. This can lead to queries or processes timing out or failing, which is reflected in the SolarWinds Orion platform as errors when it tries to query the database (e.g., the Information Service query failures you see).

 

The root cause is likely that the database maintenance process either encountered an issue or caused temporary unavailability, which led to the SolarWinds platform experiencing query failures and the Fatal Error 9001.

Check with your DB Admin team for manually running database maintenance tasks.

 

Ref articles: How to run the database maintenance manually in Orion environment

 

Database maintenance in the SolarWinds Platform

 

Additional Recommendations:

• Ensure maintenance tasks are optimised and do not overlap with peak usage times.
• Confirm that the database is healthy and not suffering from corruption or hardware issues.