Troubleshooting

When a login user is created in Microsoft Azure SQL Database and is granted permission only on some of the databases present on the server, and if the aggregation task is run for that application, aggregation fails as the user is not able to access other databases.

Resolution: In configuration under the Databases to Include section, provide the complete list of databases (comma separated list) for which the login user has access. This completes the aggregation successfully, and only details of the users present in the list of included databases will be fetched.

When the Microsoft Azure SQL Database application is created with the proxy application set as Cloud Gateway, and all the required jars are not present in the CloudGateway\WEB-INF\lib directory, account aggregation fails with the following error:

Exception during aggregation

Resolution: For account aggregation to complete successfully, ensure that all the jars are present in that /IdentityIQ/WEB-INF/lib directory, and the IdentityIQCloudGateway.jar file for IdentityIQ Cloud Gateway is present in the CloudGateway\WEB-INF\lib directory.

A transient error, also known as a transient fault, has an underlying cause that soon resolves itself. An occasional cause of transient errors is when the Azure system quickly shifts hardware resources to better load-balance various workloads. Most of these reconfiguration events finish in less than 60 seconds. During this reconfiguration time span, you might have issues with connecting to your database in SQL Database. The connector checks for transient errors and retries the operation for configured number of times by waiting for configured number of seconds. In case you get any of the following errors during connector operation, either increase the configured number attempts and delay parameter in the application Debug page, or else simply retry the operation after a delay of several seconds.

List of transient error messages:

• com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.

• com.microsoft.sqlserver.jdbc.SQLServerException: Database 'mydatabase' on server myserver.database.windows.net' is not currently available. Please retry the connection later.

• com.microsoft.sqlserver.jdbc.SQLServerException: No route to host (Read failed)

• com.microsoft.sqlserver.jdbc.SQLServerException: Broken pipe (Write failed)

• com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset

• com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error

• java.sql.SQLException: Cannot get a connection, pool error Timeout waiting for idle object

• Unable to connect to database ‘mydatabase’. message = Read timed out, cause = com.microsoft.sqlserver.jdbc.SQLServerException: Read timed out

When you connect to your Azure SQL Databases using the proxy connection policy and the session is still open without activity, the Azure SQL Gateway will terminate the session after it is idle for more than 30 minutes. This may happen with the connector and connections open inside the connector may get dropped from the network and display the following errors:

• com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset

• com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error

Resolution: If you frequently see the provided errors, try changing the connection policy to Redirect so that connections won't be terminated. For more information, refer to Azure SQL Database Connectivity Architecture.