Embiro BI

Documentation › Troubleshooting

Error codes

What each Embiro BI error code means, such as Issue 1009 or Issue 1022, and how to fix it.

When something goes wrong, Embiro BI shows a message with one or more issue codes, such as Issue 1009. Click the code to come straight to its explanation on this page.

Can't find your answer? See Common problems or contact us with the code, the time and what you were doing.

Issue 1000: The data source is too large to query

The query took too long because the table is very large. Filter it more (a shorter time range, fewer rows), aggregate in your database with a view or summary table, or ask your database administrator to add an index.

Issue 1001: The database is under unusual load

Your database was too busy to answer in time. Try again in a few minutes, or simplify the query.

Issue 1002: The database returned an unexpected error

Your database rejected the query. The message under the error code is your database's own. It usually names the problem: a typo, a missing permission, a wrong data type.

Issue 1003: There is a syntax error in the SQL query

Check the SQL for typos, missing commas or brackets, and that column and table names are spelled as in the database. Remember each database has its own SQL dialect.

Issue 1004: The column was deleted or renamed in the database

A chart or query refers to a column that no longer exists. Open the dataset → Columns → Sync columns from source, then update charts that used the old column. For Google Sheets and Jotform, a renamed header or question renames the column.

Issue 1005: The table was deleted or renamed in the database

The dataset's table no longer exists. Edit the dataset's Source to point at the new table name, or restore the table.

Issue 1006: One or more parameters in the query are missing

The SQL uses a {{ parameter }} with no value. Fill in the input above the editor, or give the dataset a default. See Parameters and date ranges.

Issue 1007: The hostname can't be resolved

The database host has a typo, or isn't a public name. Check the Host field. Private names only your office network knows can't be used: see Firewalls and SSH tunnels.

Issue 1008: The port is closed

Nothing is listening on that port. Check the port number (5432 for PostgreSQL, 3306 for MySQL), that the database is running, and that it listens on its public address.

Issue 1009: The host can't be reached on the provided port

Usually a firewall. Allow Embiro BI's address 13.49.213.196 on the database port. See Firewalls and SSH tunnels.

Issue 1010: An error occurred while running a command

Something unexpected went wrong. Try again; if it repeats, tell us what you were doing and the time.

Issue 1011: An unexpected error occurred

Something unexpected went wrong on our side. Try again; if it repeats, tell us with the time it happened.

Issue 1012: The username is not valid

The database doesn't know that username. Check its spelling. For Supabase's pooler, use postgres.<project-ref>.

Issue 1013: The password is not valid

The password is wrong. Retype it, watching for spaces copied at the start or end.

Issue 1014: The username or password is incorrect

Check both. If the password has special characters and you use a SQLAlchemy URI, URL-encode them (@ is %40, # is %23).

Issue 1015: The database name is wrong or doesn't exist

Check the Database name field: it's the database inside the server, such as sales, not the server's name.

Issue 1016: The schema was deleted or renamed

The dataset's schema doesn't exist any more. Edit the dataset's Source and choose the right schema.

Issue 1017: The login doesn't have permission to connect

The database login exists but may not connect or read. For BigQuery, give the service account the BigQuery Data Viewer and BigQuery Job User roles. For PostgreSQL, GRANT CONNECT and GRANT SELECT as in Create a read-only login.

Issue 1018: Parameters needed to configure the database are missing

Fill in every required field of the connection form.

Issue 1019: The submitted data has the wrong format

A request to Embiro BI wasn't valid JSON. If you're using the API, check the request body.

Issue 1020: The submitted data has the wrong structure

A request to Embiro BI had missing or unexpected fields. If you're using the API, check the request body.

Issue 1021: Results storage for background queries is not configured

Background queries can't store their results. This is on our side: tell us.

Issue 1022: The database doesn't allow data changes

Only SELECT statements run on this connection. That's the safe default. An admin can switch on Allow DML in the connection's Advanced settings if you really need INSERT, UPDATE or DELETE.

Issue 1023: CREATE TABLE AS doesn't end with a SELECT

When creating a table from a query, the last statement must be a SELECT.

Issue 1024: CREATE VIEW AS has more than one statement

Creating a view needs a single statement, without extra semicolons.

Issue 1025: CREATE VIEW AS is not a SELECT

Creating a view needs a single SELECT statement.

Issue 1026: The query is too complex and took too long

Queries are stopped after 10 minutes in SQL Lab, and sooner for charts. Filter or aggregate more, or prepare a summary table or view in your database.

Issue 1027: The database is running too many queries

Your database is at its limit of simultaneous queries. Try again shortly, or open fewer heavy dashboards at once.

Issue 1028: One or more parameters in the query are malformed

A {{ ... }} template is broken, for example a missing closing brace. Each parameter is written {{ name }}.

Issue 1029: The object doesn't exist in this database

A schema, table or column in the query doesn't exist. Check spelling and, for PostgreSQL, upper and lower case (mixed-case names need double quotes).

Issue 1030: The query may have a syntax error

Check the SQL and run it again.

Issue 1031: The stored results are no longer available

SQL Lab results are kept for 7 days. Run the query again.

Issue 1032: The query behind these results was deleted

Run the query again.

Issue 1033: The stored results can't be read

The results were stored in an older format. Run the query again.

Issue 1034: The database port is invalid

The port must be a whole number between 0 and 65535.

Issue 1035: The background query couldn't start

The background worker didn't pick up the query. Try again in a minute; if it repeats, tell us.

Issue 1036: The database was deleted

The connection this chart or query used no longer exists. Recreate the connection, or point the dataset at another one.

Something unclear or missing? Tell us and we'll improve this page.