Database Interface Database Troubleshooting IWS database interface provides powerful tools that will help you to identify configuration problems with databases. If you are having problems interfacing with a database, you should first enable the Database Messages in the Log window. You can do so by following the steps below: 1. In the IWS Development environment, make sure to show the Output window ( Output Window check box on the View tab of the ribbon). 2. Right-click in the Output window (usually located in the lower-right corner of the development environment), and then click Settings on the shortcut menu: 3. In the Log Settings dialog, check the Database Messages option:
After enabling this option, the Output window will display error messages related to the database. The FAQ section below lists some common errors that you can see in the Output window. enabling Database Messages GENERAL QUESTIONS Q : I configured my database, but the runtime modules (Alarm, Trend, and Events) are not being saved to the database. I only see the following error message in the Output window: Database: Error: Error to add new register[CMD_ADD]. A : Most of the database errors in the Output window will be followed by additional information such as the SQL command being executed, the Connection String and the Table name.
Error messages such as the one described above, will usually happen after a more detailed message. For example, if your Trend task fails to add a register in the database because the cable is disconnected, you should first receive a network error; if the task tries to add more registers before the time specified in the Retry field (see Database Configuration dialog ), it will only display Database: Error: Error to add new register[CMD_ADD] . If you think that your configuration is correct, and you want to debug this type of problem, reduce the Retry. Then you should see more detailed information. Q : When I try to access the MySQL database server, I get the following message:
Object is not set to an instance of an object. A : This problem was detected under the following conditions: • A known bug in MySQL Connector/Net v6.1.2 would not correctly specify the charset; and • The database table you are trying to access doesn't exist. To solve this problem, make sure you are using MySQL Connector/Net v6.2.0 and that the table you are accessing exists in the database. Q : Why is the Database Interface automatically closing some connections? Page 412 InduSoft Web Studio