We’ve officially retired the Yellow Screen of Death (YSOD). Users will see a friendly error page with a unique Error ID. All errors are logged in the ERR table for easy tracking. Common triggers for this new error page include server issues like “Server Error,” “DataReader” or “GetDataReader” failures, and “Invalid Column Name” errors—but thanks to the new system, these are handled smoothly and securely.


Instead of the YSOD, users now see:

  • A clean, branded error page
  • A message like “Oops, something went wrong”
  • A unique Error ID for support tracking
  • A Back to Home button


Behind the Scenes

  • Errors are now quietly logged. If you report an issue, just include the Error ID from the screen—it’s like a fingerprint for the problem. 
  • Errors are stored in the Error (ERR) Table.
    • Errors are now logged in a new ERR table.
    • Each error is stored with a hash of the stack trace.
    • Query Permissions need to be given to the ERR table.

What You Can Do

If you ever see the new error page:

  • Don’t panic—it’s normal.
  • Copy the Error ID if you’re reporting the issue.
  • Click Back to Home to keep working.


Expanded Error Coverage

Aeries  also handles the following errors with a modernized experience:

  • 404 Not Found
  • 400 Bad Request
  • Database connection failures


AdminCS Update Reminder for OnPrem Customers

To avoid fatal errors like Server Error, DataReader, or Invalid Column Name, it’s critical to:

  • Always apply the latest AdminCS update before updating Aeries Web. This ensures your database schema is aligned with the latest error-handling features.