How do I resolve certificate validation failures when "Validate Server Certificate" is enabled in the MS SQL monitor?

How do I resolve certificate validation failures when "Validate Server Certificate" is enabled in the MS SQL monitor?

When Validate Server Certificate is enabled, the MS SQL monitor checks the certificate the SQL Server presents. Three different checks can fail, and each has its own message. Match the message you see, then follow that section.

1. The hostname in the SQL Server's certificate does not match the configured hostname.

Applications Manager messageMS SQL : Certificate validation failed. The hostname in the SQL Server's certificate does not match the configured hostname. Please ensure the certificate's Common Name (CN) or Subject Alternative Name (SAN) matches the hostname used in Applications Manager.

This error can occur in either of the following scenarios.

Scenario 1 — error during Test Connectivity or monitor addition

Cause: the SQL Server was configured using an IP address in the Host Name / IP Address field. SSL/TLS certificate validation requires a hostname that matches the certificate's Common Name (CN) or Subject Alternative Name (SAN). Since certificates are typically issued to hostnames rather than IP addresses, validation fails.

Fix: re-enter the monitor details using the fully qualified hostname (FQDN) instead of the IP address in the Host Name / IP Address field, and retry.

Scenario 2 — error after successful monitor addition

Cause: although the monitor is added successfully, Applications Manager performs a reverse DNS lookup on the SQL Server IP address to obtain the hostname used for SSL certificate validation. If reverse DNS is not configured, or returns an unexpected hostname, that hostname may not match the CN or SAN entries in the SQL Server certificate. Certificate validation then fails and the monitor turns critical.

  1. Navigate to Monitors → Filter by: MS SQL → Overview tab.
  2. In the Monitor Information table, click the edit icon next to the Host Name field.
  3. Update the field with the correct hostname or FQDN that matches the SQL Server certificate.
  4. Save the changes.

The monitor should recover during the next polling cycle.

Option 2 — configure reverse DNS

  1. Configure a PTR record for the SQL Server IP address so that the reverse DNS lookup resolves to the hostname specified in the SQL Server SSL certificate.
  2. Verify that the resolved hostname matches one of the values present in the certificate's Common Name (CN) or Subject Alternative Name (SAN).

2. The SQL Server's certificate has expired.

Applications Manager messageCertificate validation failed. The SQL Server's certificate has expired. Please renew the certificate on the SQL Server and re-import it into the Applications Manager truststore.

Cause: the certificate is trusted, and its validity period has run out. Applications Manager will not accept an expired certificate.

  1. Check the expiry date on the SQL Server host. Open Certificates (Local Computer) → Personal → Certificates and look at the certificate bound to SQL Server.
  2. Have the certificate renewed, and re-bind it in SQL Server Configuration Manager → Protocols for <instance> → Certificate.
  3. Restart the SQL Server service so it picks up the new certificate.
  4. In Applications Manager, open the certificate screen, use Trust certificates to import the renewed certificate, and confirm it with List certificates.
  5. Edit and save the monitor, or wait for the next poll.
If the certificate cannot be renewed immediately, the only supported alternative is to clear Validate Server Certificate in the monitor, which stops the check. Treat that as temporary: it removes the protection the setting exists to provide.

3. The SQL Server's certificate is missing or not trusted by Applications Manager.

Applications Manager messageCertificate validation failed. The SQL Server's certificate is missing or not trusted by Applications Manager. Please import the correct server certificate into the Applications Manager truststore and retry.
Driver text you may also seePKIX path building failed
unable to find valid certification path to requested target

Cause: Applications Manager does not have the certificate, or the chain above it, in its truststore. Nothing is wrong with the certificate itself.

  1. Get the certificate from the SQL Server administrator. If an internal CA issued it, get the CA root certificate as well — importing only the server certificate is not enough when a CA signed it.
  2. In Applications Manager, open the certificate screen, select Trust certificates, upload the certificate, give it an alias and import it.
  3. Open List certificates and confirm the alias is listed.
  4. If the chain includes an intermediate CA, import the intermediate and the root as well. A chain is trusted only when every link above the server certificate is present.
  5. Edit and save the monitor, or wait for the next poll.
Do not replace the truststore by copying a file over it. Always import through the product, so the file and the password the product keeps stay in step.

4. What to share with support

If validation still fails, send the following to the Applications Manager support team:

  • The exact certificate validation message shown on the monitor.
  • The value in the monitor's Host Name / IP Address field.
  • The certificate's Common Name (CN), Subject Alternative Name (SAN) entries and expiry date.
  • Whether the certificate was issued by an internal CA, and whether the CA chain was imported.
  • A screenshot of List certificates from the certificate screen.
  • A Support Information File (SIF).

Refer to our feature page to learn more about SQL Server monitoring in Applications Manager.