Error "Could not connect to the server provided. Please check the network connection or the database configuration" when loading new Audit Trail Web app for NuGenesis SDMS - WKB110157

SYMPTOMS

• The following message appears in red text on the login page for the new Audit Trail Web app for SDMS:
  • Could not connect to the server provided. Please check the network connection or the database configuration
• The list of servers on the Audit Trail app's login page is empty

ENVIRONMENT

• NuGenesis 9.1 SDMS

CAUSE

The new audit trail Web app's configuration has a bare server hostname for the audit trail's server component, and the Web browser blocked download of the server list because the server hostname does not match the certificate provided by the Web server.

FIX or WORKAROUND

1. Modify the envConfig.json file on the SDMS Web server to use the fully qualified domain name:
   1. Edit the file in Notepad: Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\AuditTrail\ClientApp\assets\config\envConfig.json
   2. For the "hostname" entry, type the fully qualified domain name for the server.
   3. Save and close envConfig.json.
2. Modify the AuditTrailRedirectRule URL Redirect Rule in IIS:
   1. Open IIS Manager on the SDMS Web server.
   2. Select the local server.
   3. Double-click URL Rewrite.
   4. Double-click the "AuditTrailRedirectRule".
   5. Scroll to the end of the page.
   6. Modify the "Redirect URL" by appending the DNS Suffix to the hostname and Apply the changes.
      • Example: "https://servername:444" to "https://servername.domain.com:444"
   7. Confirm that "Append query string" is active and that the redirection type is 301.
3. Remove the server name from the IIS bindings:
   1. Open IIS Manager on the SDMS Web server.
   2. Expand the list entry for the local server and select the site "AuditTrailClientApp".
   3. Click "Bindings".
   4. Select the binding for https and click Edit.
   5. Clear the Host Name field.
   6. Click OK.
   7. Repeat steps 3-6 for the site "AuditTrailWebServer".
4. Restart IIS.
5. Reload the Audit Trail login page.

ADDITIONAL INFORMATION

Even after applying the fix/workaround, when some users try to access a URL like https://servername.domain.com/sdmsapp in Chrome, they get a "Your connection is not private" error.

There are two options to work around this:

1. Click "Advanced" and allow to trust the connection.
2. Use the URL https://servername.domain.com:444/log-viewer instead.