You have an error in your SQL syntax

Query seems to run manually…unsure of error:

mysql> SELECT option_value, autoload FROMwp_options WHERE option_id = “174”;
+——————————————————————————————————————————————-+———-+
| option_value | autoload |
+——————————————————————————————————————————————-+———-+
| a:3: {s:8:”hostname”;s:41:”ec2-53.6.126.120.compute-1.amazonaws.com/”;s:8:”username”;s:8:”username”;s:15:”connection_type”;s:4:”ftps”;} | yes |
+——————————————————————————————————————————————-+———-+

I tried the ‘mysqldump’ method, searched for similar support articles (I got the mysqldump suggestion from this support article:
https://www.ads-software.com/support/topic/deploy-errors-you-have-an-error-in-your-sql-syntax?replies=8

and re-read the documentation.

Same errors:

STEP2: UPDATE ERRORS (107)
Errors that show here are the result of queries that could not be performed.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from = "https://53.6.126.120/" WHERE id = "1"' at line 1
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from = "https://53.6.126.120/newsroom/" WHERE id = "4"' at line 1
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from = "https://53.6.126.120/newsroom/" WHERE id = "19"' at line 1
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from = "https://53.6.126.120/newsroom/" WHERE id = "30"' at line 1

This ‘non error’ shows up in yellow:

TABLE KEY ERRORS (0)
A primary key is required on a table to efficiently run the update engine. Below is a list of tables and the rows that will need to be manually updated. Use the query below to find the data.
SELECT @row := @row + 1 as row, t.* FROM some_table t, (SELECT @row := 0) r
No missing primary key errors

Hi globeonetechops,

It might be because the query is using a string for the where clause and not an integer, although its tough to tell from just that message, I’m not 100% sure to be honest…

Do you know how far apart the mysql versions are from the site that you originally created the package on are? It seems like the server where the package is being deployed is having issues with the sql generated on the orginal package server. There are a few tips on the FAQ, but I’m not sure how much they will help with generic SQL errors. Look for a question titled “What if I get errors or warnings on the install report?” I think it had some bullet points you can try…

Sorry, I wish I had a better solution…