Data Quality Portal Not Showing Any Exceptions After Upgrade

How to Fix the Data Quality Portal Not Showing Any Exceptions After Upgrade

After upgrading the Data Quality Portal, you may encounter issues where exceptions are not appearing as when you visit a specific data quality control. This problem can often be resolved by modifying the connection string in the client.config file to include TrustServerCertificate=True. Here's a step-by-step guide to help you make this change.

To confirm that this is the cause of the error, start by looking at the DQ Portal logs.

1. Open log4net.config in the DQ portal folder, often in C:\Program Files\Exmon\Portal and find an entry indicating what the portal log location is.
2. Open the logfile soon after experiencing the issue on the portal, and see if this error is in the file at the time of visiting:
   ERROR Unable to open database. Connection string: ‘CONNECTION STRING’; Error: 'Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) ---> System.ComponentModel.Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted
      at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

Steps to Resolve the Issue

1. Locate the client.config File

   • Navigate to the installation directory of the Data Quality Portal.
   • Find the client.config file within the configuration subfolder.

2. Open the client.config File

   • Use a text editor (e.g., Notepad, Notepad++, Visual Studio Code) to open the client.config file.

3. Modify the Connection String

   • Find the connection string within the client.config file. It will look similar to:

     Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;

   • Add TrustServerCertificate=True to the connection string, which should now look like:

     Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;TrustServerCertificate=True;

4. Save the Changes

   • Save the modified client.config file and close the text editor.

5. Restart the Data Quality Portal

   • Open IIS Manager and restart the Application Pool and the DQ Website.

6. Check for Exceptions

   • Log in to the Data Quality Portal and check if exceptions are now being displayed as expected.

If the problem persists even after following these steps, you may need to verify the following:

• Ensure that your server's SSL certificate is not expired.
• Check network connectivity between the Data Quality Portal and the database server.
• Ensure that there are no firewall rules blocking the necessary ports for SQL Server.

By including TrustServerCertificate=True in the connection string, you inform the system that it should trust the SQL Server's SSL certificate, helping to resolve SSL-related issues that might prevent exceptions from being displayed.

If you have any additional questions or need further assistance, feel free to post a query in the TimeXtender Community. Our team of experts is here to help!