Your member portal was working fine this morning. Now a member calls in the middle of event registration—the form just errored out and gave them a blank message. You check the homepage: it loads. But the events page? Registration? Both broken. No error details, just a wall of nothing.
Drupal's "unexpected error" message is intentionally vague. Your association's member portal, event registration, or AMS integration suddenly stops working, and all you see is a generic error page. Drupal is protecting your association's data by not showing error details publicly, but this leaves you in the dark.
The actual problem could be a module conflict, a failed database query, or an issue with your AMS integration. We'll find it.
What This Error Means
When Drupal encounters a fatal error during page load or form submission—especially during sensitive operations like member login or event registration—it stops execution and shows this generic message. The real error details are logged elsewhere, not displayed on the page.
This is good for security (your database credentials stay hidden), but it makes troubleshooting harder. Fortunately, Drupal logs everything.
Common Causes
These are the patterns we see most often. Your diagnostic log will pinpoint which one is affecting your site.
- Module conflicts — Two modules trying to do the same thing, or a module incompatible with your Drupal version
- Corrupted or missing database tables — Usually after a failed module installation or update
- AMS integration failure — Your Drupal site can't reach your Association Management System, or the connection credentials are wrong
- Memory limit exceeded — PHP ran out of memory during a complex operation like member data sync
- File permissions issues — A module or theme can't write files to the server
- Broken hook or custom code — A custom module or integration has a syntax error
- Theme issues — A theme template file has broken code
Step-by-Step Diagnostic
Step 1: Check the Drupal Error Log
Drupal logs all errors to a file or to the database. This is where the real error message lives.
If you can access the Drupal admin (at /admin), go to Reports > Recent Log Messages:
- Look at the most recent "Error" entries
- These will show the actual problem: module conflicts, undefined functions, database errors, etc.
If you can't access /admin because the site is completely broken:
- Connect to your server via SFTP
- Navigate to /sites/default/files/
- Look for a debug.log or watchdog.log file (it may also be in /logs/)
- Download and open it to see recent errors
- If logs aren't file-based, check your database. You'll need to query the watchdog table directly (contact your hosting provider if you're not comfortable with this)
Step 2: Enable Detailed Error Messages
For more specific errors, enable Drupal's debug mode (if not already on):
- Go to /admin/config/development/logging/
- Under "Logging level," select "Debug"
- Save configuration
- Try the action that causes the error again (login, register, event registration)
- Check the log again—you'll see detailed debug messages now
Step 3: Identify the Culprit Module
Once you see the error, look for module names in the message. For example:
- If you see "Call to undefined function custom_member_sync()," a custom module or module integration is broken
- If you see "Cannot execute query in module X," that module has a database issue
- If you see "Allowed memory size exhausted," you need to increase PHP memory
Go to /admin/modules and disable modules one by one to isolate the problem.
- Disable a suspect module
- Test the broken function again (member login, event registration, etc.)
- If it works, you've found the problem module
- If it still fails, re-enable it and try the next module
Step 4: Check AMS Integration
If your Drupal site connects to an AMS for member data, the error might be there:
- Go to /admin/config/ and find your AMS integration settings (varies by provider)
- Verify the API key, endpoint URL, and credentials are still correct
- If your AMS was updated or moved, update the connection details
- Test a member login or data sync
If the AMS integration is the issue, you may need to contact both your Drupal support team and your AMS provider.
Step 5: Check Database and Permissions
If the error mentions database tables or file permissions:
- Via SFTP, check that your Drupal directories have proper permissions (usually 755 for folders, 644 for files)
- Go to /admin/reports/status and check the "Database" section for missing tables or corruption
- If tables are missing, a module may not have installed correctly. Uninstall and reinstall it via /admin/modules
When to Call a Professional
Stop here if any of these apply. You've hit the boundary of standard Drupal troubleshooting.
- The error log shows database corruption or missing tables
- Disabling modules didn't fix it—the problem is in Drupal core or your hosting environment
- Your AMS integration is broken and you need help fixing the connection
- Your members can't log in or register for events and the site has been down for more than 30 minutes
- You're not comfortable navigating the Drupal admin interface or editing configuration files
Emergency Drupal Diagnosis and Recovery
If your Drupal site is throwing this error and you can't find the cause—or if it's affecting your member portal, AMS integration, or event registration—contact us for emergency Drupal support. We specialize in association sites and can diagnose the problem quickly and walk you through the fix.
Contact us and we'll prioritize root cause identification and a clear recovery plan.
Read our full emergency support or Contact us.