metricsign
Start free
Medium severitypermission

Power BI Refresh Error:
1410

What does this error mean?

A GRANT statement with a non-existent user and the implicit user creation is blocked — use CREATE USER first.

Common causes

  • 1Using old MySQL 5.6 syntax `GRANT ... TO 'user'@'host' IDENTIFIED BY 'password'` on MySQL 8.0+ which requires CREATE USER first
  • 2The NO_AUTO_CREATE_USER SQL mode is active (default in MySQL 5.7.7+)
  • 3The executing user does not have CREATE USER privilege

How to fix it

  1. 1Step 1: Create the user first: `CREATE USER 'new_user'@'%' IDENTIFIED BY 'password';`
  2. 2Step 2: Then grant privileges separately: `GRANT SELECT, INSERT ON your_db.* TO 'new_user'@'%'; FLUSH PRIVILEGES;`
  3. 3Step 3: Update automation scripts that use the old combined GRANT + IDENTIFIED BY syntax to the two-step CREATE USER + GRANT pattern.

Frequently asked questions

What changed in MySQL 8.0 regarding user creation with GRANT?

MySQL 8.0 removed the ability to implicitly create users with GRANT. You must use CREATE USER first, then GRANT privileges. The old `GRANT ... IDENTIFIED BY` syntax is no longer supported.

How do I update old MySQL 5.6 provisioning scripts for MySQL 8.0?

Replace each `GRANT privileges ON db.* TO 'user'@'host' IDENTIFIED BY 'pass';` with two statements: `CREATE USER IF NOT EXISTS 'user'@'host' IDENTIFIED BY 'pass'; GRANT privileges ON db.* TO 'user'@'host';`

Can MetricSign detect when provisioning failures prevent pipelines from connecting?

Yes — MetricSign surfaces ADF pipeline connection failures with the MySQL error code, making it easy to trace whether the issue is a missing user account.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html

Other permission errors