[Steven Zahm]

@ Foaad

If this was working fine before, then something was changed at the database level in order for this error to occur because Connections does not have the ability to cause this error, only become affected by it.

The only solution is to turn off FULLTEXT search support in the settings. Go to the Connections : Settings admin and uncheck the FULLTEXT search option and then click Save Changes. You should no longer receive this error.