Error "Could not connect to the server provided. Please check the network connection or the database configuration" appears when loading the new NuGenesis SDMS WebVision site - WKB239342

SYMPTOMS

• The following message appears in red text on the login page for the new WebVision 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 WebVision Web app's login page is empty
• In the Developer Tools in Edge or Chrome, the network trace shows no response from the Web server for the "project-servers" request
  • The same entry in the network trace shows the valid server name in the request URL

ENVIRONMENT

• NuGenesis 9.3 or later
• New WebVision loaded in a supported Web browser

CAUSE

The "SdmsProjectServers" site in IIS is bound to HTTPS at port 54824, and the site is started (listening on the port), but it does not have a certificate selected. OR, the certificate is expired. OR, the fully qualified domain name of the Web server is specified in the envConfig.json file for the main WebVision site.

FIX or WORKAROUND

• Certificates:
  1. Open IIS Manager on the SDMS Web server.
  2. Click the Sites entry in the list.
  3. Double-click the SdmsProjectServers site.
  4. Select the https binding and click Edit.
  5. Select a valid certificate from the drop-down list.
     • If there are no certificates, or no valid certificates, in IIS, see WKB17988 for instructions on creating a self-signed certificate. After creating the self-signed certificate, follow steps 1 through 5 to assign the certificate to the site.
  6. Repeat these steps for all "sdms" sites in IIS.
• envConfig.json file:
  1. Open the following file in Notepad with Admin rights:
     • Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsVision\assets\config\envConfig.json
  2. Ensure that only the Web server's hostname is in the "hostname" field in the file.
  3. Specify the Web server's domain name in the "domain" field.
  4. Save and close the file.
• Clear the Web browser's cache and reload the WebVision site.

ADDITIONAL INFORMATION