Jump to content

About this blog

Entries in this blog

KSC backup fails with "Error -1963 ('Database connection is broken " 'Connection failure{08S01};' [KSC for Windows]

Scenario After the deployment of KSC in the environment, the Backup task fails with the following error using the KSC Backup task or klbackup utility (screenshot is below). All the permissions were correctly assigned on the shared folder, and ports were opened, but still the backup was failing. There were no blocking events in the Firewall traffic logs. Error -1963 ('Database connection is broken " 'Connection failure{08S01};' LastStataement='select type from sys.system_object whe

svc_kms

svc_kms in Known Problem

NAgent 15 klmover behavior change [KSC for Windows]

In NAgent 15, klmover was updated and now requires NAgent uninstallation password, if it is set in NAgent's policy. Right now the password can't be passed to klmover as an argument, but it can be supplied via echo: echo <password>|klmover -address <administration server ip> Because cmd doesn't parse quotes and spaces in echo properly, if klmover is star

svc_kms

svc_kms in Known Problem

Install required updates and fix vulnerabilities task malfunctions after changing KSC Service account [Kaspersky Security Center for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. Problem You change the account of the administration server service via the klsrvswch tool. Note that this is the only way to change the account, manual modification (for example, via services.msc) is not supported.  Then, the you run the Install required updates and fix vulnerabilities task. As a result, the task is cancelled and updates are not installed.  Diagnostics The following

svc_kms

svc_kms in Known Problem

Get error "curl: (58) schannel: Failed to import cert file" when sending a request via KPSN API from Windows client [Kaspersky Private Security Network]

Issue An attempt to send POST request via KPSN API from a Windows client.: curl --cert C:\\Users\\user_A\\Desktop\\kpsn_api kpsn_api_crt.pem --key C:\\Users\\user_A\\Desktop\\kpsn_api kpsn_api_key.pem -k -X POST -d "{\\"action ": \\"check_url\\",\\"data ": {\\"urls ": [\\"website1.com "]}}" https://10.90.116.27:80/api/ Fails with the following error: curl: (58) schannel: Failed to import cert file C:\\Users\\user_A\\Desktop\\kpsn_api kpsn_api_crt.pem, last error is 0x80092002 Th

svc_kms

svc_kms in Known Problem

KSC Web Console shows an error after upgrade - incorrect user or password [KSC for Windows]

The problem is in the certificate - it has a 1024 bit long key. While Web Console now works only with 2048 bit long keys.  The customer needs to reissue KSC server certificate to 2048 key length. What to do -  1. Generate reserve KSC certificate - for example by using command -  klsetsrvcert -t CR -g "dns_name" -o "RsaKeyLen:2048" where DNS name is DNS name of KSC 2. Wait several days - hosts will connect to KSC and receive reserve cert.  The customer could check on c

svc_kms

svc_kms in Known Problem

How to renew the KSC certificate correctly [KSC for Windows]

This article is about Kaspersky Security Center for Windows (KSC for Windows) Problem: KSC certificate renewal or replacement is made incorrectly because the option to instantly replace the server certificate is used. As a result, managed devices loose the connection with KSC and klmover command or re-installation of klnagent is required to restore the connectivity.  Cause: After the certificate is renewed with "-t C" option, network agent

svc_kms

svc_kms in How-to

Issue with encoding of events transferred to SIEM by the KSC [Kaspersky Security Center]

KSC sends events to SIEM in UTF-8 encoding. If the events received from KSC in the SIEM system look unreadable, for example, like this: Тип приложениÑ: ÐеизвеÑтное приложение\r\nÐаправление: ВходÑщее\r\nПротокол: ICMPv6\r\nСтатуÑ: Разрешено\r\nУдаленныРIt is necessary to configure UTF-8 encoding in the SIEM system itself.

Stan Shpatar

Stan Shpatar in Known Problem

How to collect SNMP component trace [KSC for Windows]

To troubleshoot SNMP functionality in KSC specific traces should be collected. Step-by-step guide To collect traces: Download archive Use trace-5-snmpagt.reg to start trace Reproduce the issue Use trace-off-snmpagt.reg to stop trace Archive files and send to Kaspersky Support.

svc_kms

svc_kms in How-to

How to collect Klakaut traces [KSC for Windows]

In some cases klakaut traces should be collected for diagnostics. Step-by-step guide To do so: Import klakaut-on_x*.reg file. Restart klakaut service. net stop klakaut net start klakaut Enable another trace if required. Reproduce the issue. Impor

svc_kms

svc_kms in How-to

KSC service accounts password generation guidelines [KSC for Windows]

KSC installer generates default passwords for service accounts (automatically created to run KSC service), KIPxeUser and KIScSvc. Those passwords have 16 characters length, characters are taken randomly so that the password contain 3 out of 4 of the following groups of characters: Lowercase characters (a – z) Uppercase characters (A – Z) Numbers (0-9) Symbols (~ ! @ # $ % ^ & * - _ + = [ ] { } | \ : ' , . ? / ` ~ " < > ( ) Also the password cann

svc_kms

svc_kms in How-to

SIEM intergration - no events: the most frequent reason for error [KSC for Windows]

This article is about Kaspersky Security Center for Windows (KSC for Windows) Problem You set up integration with SIEM but no events come up on SIEM side. In some cases there is no incoming traffic to SIEM from KSC server. Solution In vast majority of cases the root cause can be located in KSC server trace Trace example #1 25.01.2017 09:56:56.855 00001320.0000015C L1 KLSPLG: There is no key for SystemM

svc_kms

svc_kms in Known Problem

How to export events to Splunk [KSC for Windows]

This article is about Kaspersky Security Center for Windows (KSC for Windows) Step-by-step guide Make sure that System Management license is installed, otherwise KSC events won't be exported to SIEM. For more information please refer to SIEM integration: the most frequent error.   Specify Splunk Server address and port;   Login into Splunk Management console;   Press Settings → Configure data inputs;   In the o

svc_kms

svc_kms in How-to

How to export task history [KSC for Windows]

For any types of issues with tasks managed by KSC, we require export of task execution history in .txt file. Task execution history is a sequence of events generated by client computer during task execution. Step-by-step guide To export task execution history, follow these steps: Open task results window.    In the upper part of the task results window, select problem computer.   Right-click some event in the lower part of the task results window,

svc_kms

svc_kms in How-to

How to Restrict Policy Modification in KSC Using a Custom Role [KSC for Windows]

Description You may want to allow certain users to do everything, but without giving them access to modify policies, manage users, or assign roles. However, when using default roles provided by KSC, some permissions are either too broad or unchangeable. Steps to Create the Custom Role: Open Kaspersky Security Center. Go to Administration Server Properties → Users Roles. Click “Add” to create a new role. Enter a role name (e.g., Rule for Hospitals).

svc_kms

svc_kms in How-to

Troubleshooting the 'Install updates and fix vulnerabilities' task [KSC for Windows]

In certain cases, ‘Install updates and fix vulnerabilities’ task might fail with some error. Below example contains ‘Error verifying file signature’ error but you may use mentioned keywords and overall approach for investigation of other errors met while running ‘Install updates and fix vulnerabilities’ task. Here are some steps to investigate such problems: First of all view list of updates aimed at installation on client. For this purpose in network agent trace file search for ‘Update

svc_kms

svc_kms in Troubleshooting



×
×
  • Create New...