Database troubleshooting

MySQL gateway setup and troubleshooting

Troubleshoot MySQL connection tests, server name resolution, Connector/NET driver issues, user host grants, SSL/encryption errors, and primary key behavior.

MySQLMedium

Use this guide when

Connection test failed for MySQL
Requested value 'None' was not found
MySQL works locally but Power Automate cannot connect
Power Automate cannot resolve the MySQL server name

Prerequisites

MySQL server is running and reachable from the gateway machine.
MySQL Connector/NET or the required MySQL client provider is installed on the gateway machine.
A MySQL user exists for the host context used by the gateway, such as user@localhost, user@127.0.0.1, or user@%.
Tables used by row operations have explicit primary keys.

Fast checks before you debug

If MySQL is on the same machine as the gateway, test 127.0.0.1 on port 3306.
If a friendly host name fails DNS resolution from the gateway host, use the IP address or add DNS/hosts resolution.
The MySQL username is case-sensitive in account matching contexts; test the exact username.
The MySQL connector may require an explicit primary key value for insert/update/delete scenarios.

Step-by-step diagnostics

Test MySQL reachability from the gateway host

Start with the network path. If the gateway cannot resolve or reach the server, credentials and schema settings do not matter yet.

Test-NetConnection 127.0.0.1 -Port 3306

Test-NetConnection <mysql-server-name-or-ip> -Port 3306

Resolve-DnsName <mysql-server-name>

Test the MySQL login with mysql.exe or Workbench

Run the same host, port, database, and username that Power Automate will use. If mysql.exe is not in PATH, use its full installation path.

& "C:\Program Files\MySQL\MySQL Server 8.0\bin\mysql.exe" -h 127.0.0.1 -P 3306 -u <user> -p <database> -e "SELECT CURRENT_USER(), DATABASE();"

Confirm MySQL account host grants

MySQL accounts include a user and host. A user that works as user@localhost might not work as user@% or user@127.0.0.1 unless each account/grant exists.

CREATE USER IF NOT EXISTS 'flowmigrator_mysql_user'@'%' IDENTIFIED BY '<password>';

GRANT SELECT, INSERT, UPDATE, DELETE ON flowmigrator_mysql_lab.* TO 'flowmigrator_mysql_user'@'%';

FLUSH PRIVILEGES;

Check the gateway driver/provider after MySQL client changes

If the local login works but Power Automate still fails, verify the MySQL provider on the gateway machine and restart the gateway service after driver changes.

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object { $_.DisplayName -like '*MySQL Connector/NET*' } | Select DisplayName, DisplayVersion

Restart-Service PBIEgwService

Common errors and fixes

Name resolution of the MySQL server failed.

Likely cause: The gateway machine cannot resolve the host name used in the connection dialog.
Fix: Use 127.0.0.1 when MySQL is on the gateway machine, use the server IP, or fix DNS/hosts resolution.

Requested value 'None' was not found.

Likely cause: The gateway's MySQL provider may be rejecting the unencrypted SSL mode value sent by the connector.
Fix: Try Encrypt Connection, then verify Connector/NET/provider version on the gateway host and restart the gateway service after changes.

The username/password works in Workbench but not Power Automate.

Likely cause: Workbench used localhost or a different MySQL account host than the gateway connection.
Fix: Test the same host value and create grants for the exact MySQL account host pattern needed.

Power Automate connection fields

Field	Use this value
Server	Use 127.0.0.1 if MySQL is on the gateway host; otherwise use a resolvable host name or IP.
Database Name	Exact MySQL schema/database name, for example flowmigrator_mysql_lab.
Authentication Type	Basic.
Encrypt Connection	Leave unchecked for a simple lab unless SSL/provider errors require testing the encrypted path.

Validation checklist

Test-NetConnection succeeds from the gateway host to port 3306.
mysql.exe or Workbench succeeds with the same server/database/user values.
Connector/NET/provider is installed on the gateway host and the gateway service was restarted.
Power Automate connection uses the exact username and server value that succeeded locally.
Flow Migrator MySQL actions bind to the MySQL connection after import.

Related gateway guides

PostgreSQLCheck PostgreSQL host reachability, Npgsql/provider prerequisites, database grants, schema access, SSL settings, and table primary keys before building PostgreSQL action templates.OracleDiagnose Oracle Database connector setup, gateway host driver/client requirements, TNS/service names, credentials, row-operation limits, and common import validation steps.SQL ServerDiagnose SQL Server connection failures, invalid credentials, gateway reachability, table metadata issues, and V2 trigger requirements for Flow Migrator SQL actions.