Troubleshooting

Detected Issues and Possible Solutions

This table lists issues that may be detected during SQL data transfer and provides possible solutions:

Issue	Cause	Solution
An application error is detected and the controller is set to HALT state .	A large amount of SQL data is transferred and the Watchdog Time that has been configured for a task has been exceeded.	Increase the Watchdog Time in the EcoStruxure Machine Expert Task Configuration. For further information, refer to the chapter Configuration of a Specific Task of the EcoStruxure Machine Expert Programming Guide.
A large amount of memory space is consumed by the SQL Gateway.	Too many log messages are saved on the hard disk.	Clear the content of the table in the Log Messages tab manually or adapt the settings for automatically removing the log messages as described under Clearing the Log Messages Manually and Automatically.
The connection to the database cannot be established	Data traffic on the TCP/IP port is blocked.	Configure the firewall in order to allow SQL data traffic on the TCP/IP ports 3457 (default) for unsecured connections 3458 (default) for secured connections

Issue

Cause

Solution

An application error is detected and the controller is set to HALT state .

A large amount of SQL data is transferred and the Watchdog Time that has been configured for a task has been exceeded.

Increase the Watchdog Time in the EcoStruxure Machine Expert Task Configuration.

For further information, refer to the chapter Configuration of a Specific Task of the EcoStruxure Machine Expert Programming Guide.

A large amount of memory space is consumed by the SQL Gateway.

Too many log messages are saved on the hard disk.

Clear the content of the table in the Log Messages tab manually or adapt the settings for automatically removing the log messages as described under Clearing the Log Messages Manually and Automatically.

The connection to the database cannot be established

Data traffic on the TCP/IP port is blocked.

Configure the firewall in order to allow SQL data traffic on the TCP/IP ports

3457 (default) for unsecured connections
3458 (default) for secured connections

Messages Indicating Connection Issues for MySQL Databases

The table lists messages issued by the SQL Gateway to indicate that the connection to the MySQL database cannot be established. Possible solutions are provided in the last column:

Message text	Cause	Solution
Authentication to host ‘localhost’ for user ‘root’ using method ‘mysql_native_password’ failed with message: Unknown database ‘qw’	The database is not found.	In the Database Connections node of the Configuration tab of the SQL Gateway, enter the correct Connection Name.
Host ‘WIN-1UT5MKD9831’ is not allowed to connect to this MySQL server	The server address is not found.	In the Database Servers node of the Configuration tab, enter the correct Server Address to identify the PC on which the database server is running.
Authentication to host ‘localhost’ for user “ using method ‘mysql_native_password’ failed with message: Access denied for user “@localhost’ (using password: YES)	The user name to access the database is not found.	In the Database Servers node of the Configuration tab, enter the correct User Name to access the database.
Authentication to host ‘localhost’ for user ‘root’ using method ‘mysql_native_password’ failed with message: Access denied for user ‘root’@’localhost’ (using password: YES)	The user name to access the database is not correct.
Authentication to host ‘localhost’ for user ‘root’ using method ‘mysql_native_password’ failed with message: Access denied for user ‘root’@’localhost’ (using password: NO)	The password to access the database is not found.	In the Database Servers node of the Configuration tab, enter the correct Password to access the database.
Authentication to host ‘localhost’ for user ‘root’ using method ‘mysql_native_password’ failed with message: Access denied for user ‘root’@’localhost’ (using password: YES)	The password to access the database is not correct.
Unable to connect to any of the specified MySQL hosts.	This message can have different causes: The connection protocol is not correct. The server address is not correct.	In the Database Servers node of the Configuration tab, select TCP as Connection Protocol. In the Database Servers node of the Configuration tab, enter the correct Server Address to identify the PC on which the database server is running.

Messages Indicating Connection Issues for SQLite Databases

The table lists messages issued by the SQL Gateway to indicate that the connection to the SQLite database cannot be established. Possible solutions are provided in the last column:

Message text	Cause	Solution
Data Source cannot be empty. Use :memory: to open an in-memory database	The database file is not found.	In the Database Connections node of the Configuration tab, enter the correct path to the SQLite Database File directly or click the Browse button to browse the file system for the file.