Users Page Not Loading after upgrade to 3.1.0 or newer: MariaDB/MySQL Error (Storage Engine MEMORY Disabled)

This article describes an issue where the Access Server Users page fails to load after upgrading to version 3.1.0 or newer. The issue is accompanied by a database error indicating that the MEMORY storage engine is disabled and table creation is disallowed.

Summary

Starting with version 3.1.0, Access Server uses MEMORY tables to optimize the loading of the Users page. If the database configuration prevents the creation of MEMORY tables, the page may fail to load.

Symptoms

You may observe the following behavior:

• The Users page doesn't load in the Admin Web UI.

• The following error (or a similar one) appears in the logs when using MySQL/MariaDB with the API Debug is enabled (DEBUG_API=True) under /usr/local/openvpn_as/etc/as.conf:

2026-02-04T13:17:05+0000 [stdout#info] [WEB] OUT: '2026-02-04T13:17:05+0000 [twisted.web.client._HTTP11ClientFactory#info] Starting factory _HTTP11ClientFactory(<function HTTPConnectionPool._newConnection.<locals>.quiescentCallback at 0x7b4b13ce8b80>, <twisted.internet.endpoints._WrapperEndpoint object at 0x7b4b13c8bcd0>)'
2026-02-04T13:17:05+0000 [stdout#info] '(mariadb.OperationalError) Storage engine MEMORY is disabled (Table creation is disallowed).\n[SQL: \n CREATE TABLE materialized_profiles_cache_13088e6c (\n id INT NOT NULL,\n name VARCHAR(128) NOT NULL,\n prop_name  VARCHAR(128) NOT NULL,\n prop_value VARCHAR(1024) NOT NULL,\n PRIMARY KEY (id, prop_name)\n)\n ENGINE=MEMORY]\n(Background on this error at: https://sqlalche.me/e/14/e3q8):

Cause

This issue occurs when the MEMORY storage engine is disabled in the MySQL/MariaDB configuration. This configuration is common in some managed or cloud-hosted database environments, such as Google Cloud SQL, where in-memory tables are restricted, and specific database configurations are used to prevent the use of volatile, in-memory tables.

Although Access Server includes an internal check to verify that the MEMORY storage engine is available, some database versions report the engine as available even when table creation is still disallowed.

We have confirmed this behavior with MySQL 8.0.31 on Google Cloud SQL, but other versions and cloud providers may also be affected.

Solution

In most cases, upgrading the database server resolves the issue.

Specifically, upgrading from MySQL 8.0.31 to 8.0.34 or newer addresses the behavior where MEMORY tables are reported as available but cannot be created.

Steps to resolve

Recommended approach: upgrade the database

1. Back up the database
   Ensure you have a complete, verified database backup before making any changes.

2. Upgrade the database server
   - Upgrade your MySQL/MariaDB instance to a version that includes the fix (e.g., from 8.0.31 to 8.0.34 or higher)
   - Refer to your database vendor’s release notes for version-specific guidance and compatibility considerations.

3. Verify the result
   After the upgrade completes, sign in to the Admin Web UI and click Users. The page should load normally.

If the issue persists or you have additional questions, submit a support ticket.