There’s generally more information in the error message. What is your actual relevant code, from the point of building the sql statement, through to after the query has been executed, with whatever error handling you have?
You might want to consider how you lay your queries out to make them easier to read, for example with your query:
UPDATE users SET name = 'Sailor Sam',email = 'ssam@industechnology.com', role = 'Moderator',password = '1234', enabled = 0, updated_by = 'lurtnowski@industechnology.com', updated = CURRENT_TIMESTAMP WHERE user_id = 2
When laid out like for example like this:
UPDATE
users
SET
name = 'Sailor Sam'
, email = 'email@domain.com'
, role = 'Moderator'
, password = '1234'
, enabled = 0
, updated_by = 'updater@domain.com'
, updated = CURRENT_TIMESTAMP
WHERE
user_id = 2
it makes it much easier to read.
btw, you should be using prepared statements when working with any data being plugged into a query, no matter what the source of that data is and how well you trust the source of the data