Skip To Content

Troubleshoot a database connection

Note:

Database connections are supported in Insights Enterprise and Insights Local.

When creating a new database connection or trying to access an existing database connection, Insights for ArcGIS may not be able to establish a connection to the database.

When a connection problem occurs, one of the following messages appears:

  • Invalid credentials. Ensure the user name and password provided for this connection are correct indicates that an incorrect username or password was entered.
  • Invalid host. Ensure server name provided for this connection is valid and that the host is accessible indicates that an incorrect server name or port number was entered.
  • Invalid database name. Ensure database name provided for this connection is valid indicates that an incorrect database name or instance name was entered.
  • Something went wrong. Verify your connection properties, or click here to troubleshoot this is used for SAP HANA only. This error message indicates that one of the required parameters is incorrect.

The following list provides common causes of database connection problems that can be investigated:

  • The connection properties, such as User Name, Password, and Port Number are invalid. Verify that the connection properties for the database connection are correct. If changes are required for an existing database connection, you can edit these properties by updating the database connection.
  • You don't have the database privileges required to create the connection.
  • Database driver files are not present or are improperly configured on your organization's hosting server site (Insights Enterprise only). To establish a connection, your portal's hosting server must have Java Database Connectivity (JDBC) files uploaded and registered. See Configure ArcGIS Enterprise to support Insights or Register Relational Data Store Type in the ArcGIS REST API help.
  • The database is not configured to accept connections. Some databases require additional configuration to allow remote clients to connect. For example, for Microsoft SQL Server databases, you must enable the server network protocol to accept connections over the network.
  • Connections have been blocked. Database administrators can prevent users from connecting to a database while they perform certain database maintenance tasks, such as backup and recovery, and upgrades.
Caution:

If you're having trouble using a database connection item that previously worked in Insights, you may need to update the connection. Do not delete the database connection. When Insights creates a dataset from a database table (or multiple database tables in the case of a joined dataset), a database connection is required. Deleting the database connection will cause any dependent datasets to be inoperable. This caution is especially important if the database connection has been shared with others. Only when you're sure no datasets are dependent, or you purposefully want to disable upstream datasets, should you delete a relational database connection.