Windows | MySQL 8.4 Connection Failures in Desktop ElastiCube Manager
Problem
When attempting to connect to or build an existing ElastiCube using MySQL version 8.4 within the legacy Desktop ElastiCube Manager (ECM), the process fails. Users may experience symptoms such as:
The initial database schema list loads successfully, but clicking 'OK' triggers an error.
Partial builds where the first table succeeds, but subsequent tables fail with an "Authentication failed" error.
Cause
The root cause is a technology mismatch between the legacy desktop application and newer database security standards:
Connector Limitations: The Desktop ElastiCube Manager relies entirely on legacy CLR (.NET) data connectors. The built-in CLR connector framework does not support the authentication requirements and updates introduced in MySQL 8.4. Because the MySQL CLR connector is deprecated and will no longer receive updates, it cannot be patched to support MySQL 8.4.
Authentication Protocol Clashes: MySQL 8.4 disables legacy native password mechanisms by default, shifting entirely to modern, secure authentication. The legacy CLR framework natively expects older behaviors, resulting in a failure to communicate.
Desktop Limitations: Desktop ECM natively lacks support for modern Java (JDBC) connectors.
Solution: Migrate to Web ElastiCube Manager
To resolve this issue and preserve your MySQL 8.4 architecture, your data models must be migrated to the Web ElastiCube Manager (Web ECM), which actively leverages modern, Java-based connectors capable of handling modern MySQL protocol requirements.
Step-by-Step Migration Guide
Follow these steps in the Web ElastiCube Manager (accessible via your browser under the Data tab) to migrate your dataset connections from legacy CLR to Java/JDBC connectors:
Log into the Sisense Web Application and navigate to the Data tab.
Open the affected ElastiCube model.
Locate the MySQL dataset you need to update, open its three-dot menu, and select Change Connection.
Update Connection Parameters:
If your connection parameters are already visible, simply verify them.
If the fields are blank, re-enter your MySQL 8.4 server credentials, hostname, and database configurations to re-initialize the connection via the Java driver.
Re-select or re-add the existing tables and click Next.
Save your changes and initiate an ElastiCube build to verify that data ingestion completes without authentication failures.
Recommendation: Always test this connection migration workflow on a test data model or lower environment before applying changes to business-critical production dashboards.
Conclusion
To successfully resolve this blocker and ensure long-term stability, workflows must be transitioned to the Web ElastiCube Manager (Web ECM). Web ECM is designed to utilize modern, Java-based (JDBC) connectors that natively support MySQL 8.4, allowing datasets to connect, retrieve tables, and build successfully.
