KSWS Error sending the request to KSN 0x80230017

[Tahmeed702]

I have 151 server out of that 11 server showing Database outdated and application database are corrupted, all server running ksws 11.0.1.897 , out of 11 server 1 server showing this error "KSWS Error sending the request to KSN 0x80230017"

 

[KarDip]

Hello @Tameed7022

The issues you're describing with Kaspersky Security for Windows Server (KSWS) require systematic troubleshooting to resolve both the outdated database and application database corruption, as well as the KSN error. Here's a step-by-step guide to address the problems:

---

1. Database Outdated

This typically happens due to issues with updates not being applied. To resolve:

• Check Update Sources:

  • Ensure the servers are configured to get updates from a valid source (e.g., Kaspersky Security Center or direct Kaspersky update servers).
  • Verify that the update task is running successfully in the Kaspersky Security Center or locally on the affected servers.

• Manually Update Database:

  • On the affected servers, run the update task manually to check for errors.
  • If the update fails, review the logs in:
    • C:\ProgramData\Kaspersky Lab\Endpoint Agent\Logs\
    • C:\ProgramData\Kaspersky Lab\KSWS\Logs\.

• Network Issues:

  • Ensure the affected servers can reach the update server or Kaspersky Security Center.
  • Verify the DNS settings and proxy configuration if applicable.

---

2. Application Database Corruption

Corrupted application databases may require rebuilding or reinitializing:

• Rebuild the Database:

  1. Stop the Kaspersky Security Service.
     Copy code

     net stop KLAdminServer
  2. Delete the corrupted database files. Locate them in:
     Copy code

     C:\ProgramData\Kaspersky Lab\KSWS\Database\
  3. Restart the service:
     Copy code

     net start KLAdminServer

• Reinstall KSWS if Required:

  • If rebuilding fails, uninstall KSWS from the affected servers, ensuring remnants are removed, and then reinstall.

---

3. KSN Request Error (0x80230017)

This error indicates a failure in communication with the Kaspersky Security Network (KSN). To resolve:

• Network Access:

  • Ensure the server has access to the KSN servers. Verify outbound connectivity on the required ports (e.g., HTTPS port 443).
  • Test access to https://ksn.kaspersky.com/ and related endpoints.

• Proxy Settings:

  • If your environment uses a proxy, ensure it is correctly configured in KSWS settings and allows traffic to KSN servers.

• Time Synchronization:

  • Ensure the server's system time and date are synchronized with an NTP server.

• Disable KSN (Temporary Test):

  • If KSN communication is unnecessary for your environment, disable it in the settings to determine if the error resolves.

---

4. Logs and Monitoring

For further diagnostics:

• Collect detailed logs from the affected servers using klactlogs:

• Copy code

  klactlogs.exe --start --path C:\Logs

  Run this before reproducing the issue. After capturing, use --stop to finalize logs.

• Check Kaspersky Security Center for errors in the Event Log under Administration Server > Events.

---

Summary Actions

1. Update database sources and manually test updates.
2. Rebuild the corrupted application databases.
3. Troubleshoot KSN connectivity for the error 0x80230017.
4. Monitor logs for detailed diagnostics.

If the issues persist despite these steps, escalate to Kaspersky Technical Support with detailed logs from the servers.

Thank you

Edited November 26, 2024 by KarDip
added text console

[Renan Corassa]

7 horas atrás, Tahmeed702 disse:

Tenho 151 servidores dos 11 que mostram que o banco de dados está desatualizado e o banco de dados do aplicativo está corrompido, todos os servidores executando o KSWS 11.0.1.897, dos 11 servidores, 1 servidor mostra este erro "Erro do KSWS ao enviar a solicitação para o KSN 0x80230017"

 

Clean the KSC administration server update repository.

Start the [Download updates for the Administration Server repository] task.

After completion, start the KSWS Database Update task for the Servers.

Most likely, the Servers have a corrupted KSN component due to some application database update failure.