When using KLC to connect to an endpoint, an error message is thrown stating: "Error: The request failed with status code: 404." Also, when reviewing the MakeSelfSignCert logs(See log location below), this error is shown:
[ApplicationRunnerBase] Fatal exception encountered
..\MakeSelfSignedCertApplication.cpp(174): Throw in function int __cdecl Kaseya::MakeSelfSignedCertApplication::RunApplication(void)
Dynamic exception type: struct Kaseya::Utility::RuntimeException
No mapping between account names and security IDs was done (system:1332)
Log Location: C:\Windows\System32\config\systemprofile\AppData\Local\Kaseya\Log\MakeSelfSignedCert.exe folder on Kaseya VSA server
This is an issue where the VSA install certificate does not install correctly immediately after upgrading to R9.3. The certificate is needed to begin all authentication requests that KLC uses.
WORKAROUND / RESOLUTION
The workaround is to run Reapply (or Reinstall) Database Schema. This will kick off the process to reassign the certification to the VSA server. IMPORTANT: Running Reapply (or Reinstall) Schema can temporarily bring down the Kaseya VSA server while the process completes. Please schedule a 20-30 minute maintenance window for the completion of this process.
Reapply Schema will permanently fix systems which have already been affected. The Kaseya Development team are investigating how to prevent future installations from being affected. This KB article will be updated with the patch version as to when a code fix is released.
Please note, if the above steps do not resolve the problem, please create a new support ticket and include the following logs in a zip file:
From the VSA Server
From the Endpoint (Agent) Machine
C:\Program Files (x86)\Kaseya\[AgentInstance]\AgentMon.log
Reference: #129412 / RC-1631 / DEVOPS-181