How to solve main problems when downloading updates to the repository in Kaspersky Security Center
Latest update: August 29, 2024
ID: 15633
Show applications and versions that this article concerns
- Kaspersky Security Center 14.2 (version 14.2.0.26967)
- Kaspersky Security Center 14 (version 14.0.0.10902)
- Kaspersky Security Center 13.2 (version 13.2.0.1511)
- Kaspersky Security Center 13.1 (version 13.1.0.8324)
- Kaspersky Security Center 13 (version 13.0.0.11247)
Issue
When downloading updates to the repository in Kaspersky Security Center, the following problems may occur:
- The update task won’t start.
- The update task takes a long time to complete or fails.
- The update task log contains error events or the task fails. Examples of error messages:
- “Not every component has been updated. One or more update components may be missing in the update source.”
- “A file necessary for the database update is missing from the update source.”
- “No updates available.”
- “Failed to retranslate the component. '<Component>'”
- “Failed to verify the signature of a file. '<URL>'”
- “Failed to connect to the update source. '<URL>'”
- “Update task has completed. File download error.”
- “Download has timed out.”
If the Download updates to the Administration Server repository task completes successfully, but you are having problems getting updates to your endpoints, follow the recommendations from the article.
Solution
Check that the Kaspersky Security Center infrastructure meets the criteria and recommendations listed below.
Check if the Administration Server and database server meet the system requirements
Verify the following:
- Hardware and software meet the system requirements for the installed version of Kaspersky Security Center.
- The database server has enough disk space to function properly.
- The database server has the recommended settings:
Check that network settings and credentials are correct
Do the following:
- Make sure that the network settings for connecting Administration Servers to external services are correct. You can check this in the logs of the proxy server or network equipment that provides access to the Internet.
- Make sure that the proxy server credentials are correct if the Administration Server downloads updates via the proxy server.
To check this, log in to the proxy server using these credentials to check this. - Check that the scanning of encrypted connections between the Administration Server and the proxy server is disabled if your infrastructure uses Deep Packet Inspection (DPI) or traffic decryption and analysis technologies (SSL inspection application) as part of third-party security solutions.
If the scanning of encrypted connections is enabled, the update download fails with the error “Failed to establish the HTTPS connection: TLS error (54). ‘/’". To fix this issue, replace HTTPS with HTTP to avoid the issues with the proxy server.
Check the settings of the update task with a local or network folder as a source
Do the following:
- Make sure that the requirements from the Sources of updates block in step 4 are met.
- Check that the update source is not the KLSHARE shared folder of another Administration Server.
Configure an update via an additional shared folder. To copy updates in advance, select the Copy downloaded updates to additional folders check box in the update task settings. - Make sure that the credentials for connecting to the shared network folder of the update source in the task settings are correct.
If a domain user account is used, enter the domain name. For example, company.local\User, where company.local is a company domain. - Check that the account has read access to the shared network folder of the update source.
To check the access, go to the shared network folder under this account and open any file in Notepad. - Make sure that the account has a sufficient level of NTFS access in the shared network folder settings of the update source.
If the level of NTFS access is insufficient, the error “Update task has completed. File download error.” will appear in the task log. - Check that a network disk that is connected as a local disk, such as Z:\KAVUpdate, is not used as the update folder.
Check that the Kaspersky Security Center components are up-to-date
Do the following:
- Check the versions of the application management plug-ins using this guide. If the plug-in version is not supported or the plug-in is not being used, remove it.
- Remove installation packages of applications that you do not plan to use.
- Make sure that supported application versions are installed on the managed devices (including devices with the Network Agent) in the Unassigned devices section of the Administration Console.
- Make sure that you are using a supported version of Kaspersky Security Center. We recommend updating the application to the latest supported version.
- Make sure that all Administration Servers in the hierarchy have the same version, or that the Administration Server that updates the network folder with a copy of the anti-virus databases has the same version as the primary server.
- If the Administration Server has secondary Administration Servers, check that the listed components are up-to-date on all of them.
If you are using Kaspersky Update Utility to download anti-virus database updates
- Select the Download updates by using the old scheme check box in the task settings.
- Clear the Administration Server updates repository.
- Use other recommendations for working with Kaspersky Update Utility.
Additional recommendations
- Check that the update source priority and parameters in the Download updates to the Administration Server repository task are set correctly.
- Try to remove the Download updates to the Administration Server repository task and create it again with the correct settings. Use these instructions.
- Clear the updates repository of the current server and the primary Administration Server if it is specified as the source of anti-virus database updates.
What to do if the issue persists
- Collect diagnostic data on the Administration Server if you are using one server.
If a hierarchy of Administration Servers is configured:- Collect diagnostic data on the primary Administration Server if it is the source of the updates.
- Collect diagnostic data on the secondary Administration Server where the problem occurs.
Wait at least 30 minutes after collecting the diagnostic data on the first server.
- Save the collected data for each server to a separate folder with the server name.
- Submit a request to Technical Support through Kaspersky CompanyAccount. Attach the collected diagnostic data to the request and specify which steps from this article you have tried to perform.
How to collect diagnostic data
- Enable level 4 tracing for the Network Agent on the Administration Server.
- If possible, enable screen recording. If it is not possible, take screenshots of your actions and the error.
- Run the Download updates to the Administration Server repository and wait for it to complete.
- Disable screen recording if it was enabled.
- Disable tracing.
- Export events from the Download updates to the Administration Server repository task result.
- Export the Download updates to the Administration Server repository task to a .klt file. To do so, right-click the task and select All tasks → Export.
- Create a report using the Report on Kaspersky software versions template for the Managed Devices group and save it to a file.
- Collect the GetSystemInfo report with the Include Windows event logs option enabled.
- Copy the updater.ini configuration file from the working folder of Kaspersky Update Utility if it is used to prepare the Administration Server updates repository.