Database connection troubleshooting

This topic includes some general, as well as database-specific, suggestions for some of the more common problems with establishing a network connection to the remote RDBMS databases.

Things to check on the database side

  • Check with the database administrator (or owner of the database) to make sure that your login credentials have sufficient authorization for establishing a remote connection to the database.
  • Make sure the database is running and is correctly configured.

Things to check on the Workbench Property Sheet

  • Make sure that both the RdbmsNetwork and database have their Enabled properties set to true.
  • Check that you have the correct User Name and Password. These are the credentials required by the third-party database, not the credentials to log into the platform or station.
  • Confirm the name of the database. This could be the Database Name, Instance Name or Service Name.
  • Check that you have set the correct Port number. Default port numbers may not have been used when the database instance was initially configured.

MySQLDatabase connections

Make sure that you have installed the correct MySQL connector version.

 NOTE: The rdbMySQL-MySQLDatabase component was tested with the MySQL connector version “mysql-connector—java–8.0.24”. Use of earlier versions of this connector is not recommended and not supported. 

If you see the following, or similar, error it could mean that you are running an incompatible version of the connector. java.lang.NoClassDefFoundError: Could not initialize class com.mysql.cj.protocol.a.authentication.AuthenticationLdapSaslClientPlugin.

SqlServer RDBMS connections

  • If the RDBMS server is running a named instance of the database that you are trying to connect to, make sure that you have the correct Instance Name which is provided during the sql server installation. If Instance Name is empty, the driver ignores the property and defaults to the database assigned in the SqlServer.
  • For a station to connect, the Microsoft SQL Server instance must be configured for SQL Server Authentication. This is a property to configure in the third-party database. It is not a Niagara property.
 NOTE: By default, SqlServerExress provides named instances for databases. The default name provided is "SQLEXPRESS." 

To monitor the performance of an instance of SQL Server or troubleshoot problems with the queries being submitted to the database by the station, alongside the usual Platform-Application Director output it is often useful to use an SQL Profiler.