KMS Validation test results show 5XX error

Problem:

You click the Test KMS button on the KMS Server Validation screen, and receive "Cannot connect to KMS/Application server (5XX)" message.

Solution:

Check the Alarm Dashboard for the reason in which the error occurred.
1. Click System Monitoring > System Monitor > Alarm Dashboard.
2. Select the KMS alarm in the Enterprise Alarms pane.
3. See the Details pane for information about the selected alarm.
Check the Recorder KMS log file.
1. Log on to the Recorder and go to %IMPACT360DATADIR%\logs, and then open the Recorder KMS log file.
2. Search for a log entry similar to the following:
  
  [ThalesKmsRegistr|ThreadPoo~~Wheel,11>|I] 2019-03-13 18:36:50.645+02:00 From Thales silent registration log file: <The server returned an error - 400 Registration is locked from IP address "10.165.243.205", because of too many failed attempts. It will be unlocked in "11" minutes.>
Using the information provided in the Alarm Dashboard, correct the error.
Make sure that the following entries are the same.
- Shared Secret Key field on the Security page in Enterprise Manager
- Registration Shared Secret field on the Registration Shared Secret page in the Thales KMS web application
  
  If the entries are not the same, make the necessary corrections.
If you see the too many failed attempts message in the log file, do the following:
1. On the Application server, stop the Recorder KMS service and the Watchdog service.
2. Wait the amount of time specified in the log file (for example, 11 minutes is shown above).
3. On the Application server, start the Recorder KMS Service and the Watchdog service.