How to Fix Package Creation Error in Kaspersky Security Center 15.1

Error When Creating Standalone Packages in Kaspersky Security Center 15.1.0.20748 After Deleting Old Packages

The error when creating standalone packages in Kaspersky Security Center 15.1.0.20748 after deleting old packages usually occurs due to remaining references to deleted packages in the database and update repository. To resolve the issue, it’s necessary to clean up unused data using the built-in KSC cleanup wizard, check repository integrity, and use utilities to completely remove references to deleted packages.

Contents

• Causes of the Error
• Where References to Deleted Packages Might Remain
• Step-by-Step Solution
• Tools for Data Cleanup
• Preventing Similar Issues in the Future
• Additional Recommendations

Causes of the Error

The error when creating standalone packages after deleting old packages occurs due to several key factors:

Remaining references in the database
When packages are deleted manually (through Windows Explorer), only the files on disk are removed, but records in the Kaspersky Security Center database remain that reference these deleted files. This causes the system to try to access non-existent files when creating new packages.

Update repository corruption
As noted in the official Kaspersky documentation, deleting packages without using built-in tools can corrupt the update repository structure, causing errors in subsequent package operations.

Insufficient disk space
The original problem with limited space (only 60 GB total) is exacerbated by the fact that even after deleting files, space may not be completely freed due to locked or corrupted files.

Where References to Deleted Packages Might Remain

References to deleted packages can be located in several places:

1. Administration Server database

In the SQL Server database used by KSC, records remain in the tables:

• InstallationPackages - information about installation packages
• PackageComponents - package components
• UpdateRepository - update repository

2. Update repository

The path to the repository is usually located at:

C:\ProgramData\KasperskyLab\adminkit\<version>.working\repository

Here may remain:

• Partially deleted update files
• Corrupted index files
• Cache files with references to deleted packages

3. Event logs and reports

In KSC logs, records referencing deleted packages may remain, especially if deletion was performed without restarting the server.

Step-by-Step Solution

Step 1: Clean up unused data through the KSC wizard

To properly clean up, use the built-in cleanup wizard:

1. Open the Kaspersky Security Center console
2. Go to Additional → Administration → Clean up unused data
3. Launch the Clean up unused data wizard
4. Select data types to clean up:
   • Deleted installations
   • Outdated package versions
   • Temporary files
5. Perform the cleanup

Important: As stated in the Kaspersky documentation, the cleanup wizard allows you to safely remove data left after package deletion.

Step 2: Check and restore the repository

If the cleanup wizard didn’t help, perform the following actions:

1. Check repository integrity:
   C:\ProgramData\KasperskyLab\adminkit\<version>.working\repository
   

2. Delete files with extensions .tmp, .bak, .old from the repository
3. Restart the Kaspersky Administration Server service

Step 3: Using the data removal utility

To completely remove all related data, use the utility mentioned in official sources:

1. Download the Administration Server removal utility
2. Run it in data cleanup mode
3. Specify the option to clean up residual installation data

Tools for Data Cleanup

Built-in KSC tools

Clean up unused data wizard

• Allows safe removal of residual data
• Works through the KSC console graphical interface
• Provides reports on performed operations

Command utility klclean

• Located in the KSC installation folder: C:\Program Files (x86)\Kaspersky Lab\Kaspersky Security Center <version>\klclean.exe
• Allows automation of the cleanup process
• Supports various cleanup parameters

External utilities

Kaspersky Administration Server Cleanup Utility

• Designed for complete removal of related data
• Works in safe mode
• Creates backups before deletion

Preventing Similar Issues in the Future

Data storage optimization

1. Regular automatic cleanup

   • Set up a schedule for automatic cleanup of unused data
   • Use built-in KSC task schedulers

2. Disk space monitoring

   • Set threshold values for space shortage warnings
   • Regularly check repository usage

Proper deletion procedures

1. Use built-in KSC tools

   • Never delete files manually through Explorer
   • Always use the package removal wizard in the KSC console

2. Create backups

   • Regularly back up the KSC database
   • Keep copies of important packages before deletion

Additional Recommendations

Working with limited disk space

When working with a server that has only 60 GB of disk space:

1. Move the repository to another drive

   • Change the repository path in KSC settings
   • Use symbolic links to move data

2. Optimize report storage

   • Set up automatic deletion of old reports
   • Limit the event retention period

Problem diagnosis

If cleanup didn’t help, perform diagnosis:

1. Check the System Event Log for KSC errors
2. Use the kltrace utility to analyze logs
3. Contact Kaspersky Technical Support with a complete log of actions

Sources

1. Clean up unused data in Kaspersky Security Center
2. Kaspersky Security Center data removal tool
3. KSC 15.1 update repository issues
4. Update repository cleanup in Kaspersky Security Center
5. Creating standalone installation packages
6. Forum discussion on package removal problems
7. Removing unused data in Kaspersky Security Center

Conclusion

To fix the error of creating standalone packages in KSC 15.1.0.20748 after deleting old packages, you need to:

1. Use the built-in cleanup wizard for unused data - this is a safe way to remove remaining references in the database
2. Check and clean the update repository - manually delete temporary and corrupted files
3. Apply data removal utilities - to eliminate all remaining references
4. Set up regular automatic cleanup - to prevent the problem from recurring
5. Monitor disk space and optimize data storage

It’s important to remember that manual file deletion without using specialized KSC tools always leads to problems with the database and repository. Always use built-in tools for safe package and data removal.