When creating a backup copy, the error message “Invalid folder path. Error 1181/0x52e has occurred because Administration Server has no write permission in...” appears.

Solution

1. Check whether the user accounts that run Administration Server and SQL Server services have permissions to access and write data to a shared folder.
2. Check that the shared folder exists and can be accessed from the Administration Server and SQL Server.
3. Configure the access permissions for the folder to which the backup will be performed.

The klbackup tool or backup task may display the following error in the klbackup.log file: «Backing up db ... FAILED - check whether SQL Server has enough permissions to access backup path ... Cannot open backup device ... Operating system error 3 (error not found).».

Solution

1. Use an UNC path to the backup folder if the SQL Server and Administration Server are located on different computers. This is necessary so that the klbackup tool and SQL Server have access to the backup folder at the same time. For details about UNC paths, see the Microsoft support site.
2. Configure the access permissions for the folder to which the backup will be performed. The SQL Server can only create or restore backups in a folder that it can access directly (this requirement is irrelevant for MySQL). The folder must be shared with read and write permissions (ACLs must be configured for sharing and NTFS).

If the issue still persists, use the instructions below.

The backup task in the klbackup.log file may end with the following error: “Backing up db ... FAILED - check whether SQL Server has enough permissions to access backup path ... Cannot open backup device ... Operating system error 3 (error not found).”.

Solution

1. Exit the klbackup tool if it is open.
2. Open Task Manager and terminate the klbackup.exe processes, if any.
3. Enable the level 4 tracing of the Administration Server and start the backup task (manually or according to its schedule).
4. Wait until the error appears.
5. Disable the Administration Server tracing.
6. Export the task history with the error to a text file.
7. Collect the following files on the computer with the Administration Server installed: $klserver-1093.log, $klserver-1093.log.bak, $klbackup-1093.log, klbackup.log and an event log.
8. Submit a request to Technical Support through Kaspersky CompanyAccount. Attach the collected files and the exported task history to your request.

The klbackup tool may fail with the following error: “Backing up db ... FAILED - check whether SQL Server has enough permissions to access backup path ... Cannot open backup device ... Operating system error 3 (error not found).”.

Solution

1. Exit the klbackup tool if it is open.
2. Open Task Manager and terminate the klbackup.exe processes, if any.
3. Enable the level 4 tracing of the Administration Server.
4. Start the tool and wait until the error occurs.
5. Disable the Administration Server tracing.
6. Save the error description to a text file.
7. Collect the following files on the computer with the Administration Server installed: $klserver-1093.log, $klserver-1093.log.bak, $klbackup-1093.log and an event log.
8. Submit a request to Technical Support through Kaspersky CompanyAccount. Attach the collected files and the saved error description to your request.

The backup task may end with the following error: “Generic DB error: “8985 'Could not locate file 'DATABASE_LOG' for database 'KSCSDB' in sys.database_files. The file either does not exist, or was dropped.{42000};'LastStatement='DBCC SHRINKFILE (DATABASE_LOG);’’.

Cause

The error occurs because the physical and logical database file names don’t match. This may happen if you created the Kaspersky Security Center server database yourself and changed the logical file name.

Solution

Change the logical database file name so it matches the physical name.

The backup task may end with the following error: “Database is corrupted. At least one repository C:\ProgramData\Application Data\KasperskyLab\adminkit\1093\gsyn\klsdata.dat has been corrupted and will not be recovered. Hardware fixing and application reinstallation are required.”.

Cause

The error may occur because of the operating system malfunction or an unexpected reboot of the system with disk caching enabled (for example, due to a power loss). This leads to the corruption of the Kaspersky Security Center repositories.

Solution

1. Uninstall Kaspersky Security Center.
2. Reinstall Kaspersky Security Center.
3. Restore the latest backup copy using the klbackup tool.