Problem with creating archives in Torgsoft

Archiving (backup creation) in Torgsoft does not work if there are disk limitations, access issues, SQL limits, or the server service is not running. This article will help you quickly find the cause and restore the backup.

When the backup is not created

• During automatic scheduled backup.

• During manual creation of a database archive.

• After Windows / SQL Server updates or changes to save paths.

• When working with cloud archive storage (Google Drive).

How it appears

• The backup is not created or is interrupted.

• There are errors in the task log:

• Operating system error 112 (There is not enough space on the disk)

• Operating system error 5 (Access is denied)

• Operating system error 3 (The system cannot find the path specified)

• PRIMARY filegroup is full

• There is no new archive file in the folder.

• Authorization error when uploading to the cloud.

Why the backup is not created

A. Not enough free disk space (most common)

Signs:

• Error error 112.

• Slow system performance.

Solution:

1. Check free space on the disk specified in Torgsoft as the archive storage location.

2. Delete outdated archives and update packages:

•    C:\TORGSOFT\Update

•    C:\DatabaseArchive

3. Clean up temporary Windows files (the Temp folder).

How to check the result:
A new archive file with the current date has appeared.

B. Access errors or incorrect path

Signs:

• Errors error 5 or error 3.

Solution:

1. Grant full access to the SQL system user or the “Everyone” group for the archive folder.

2. Check the path in “Scheduled Tasks” (the disk exists and is accessible).

3. Do not save archives to the Desktop.

How to check the result:
The backup is created without an access error.

C. Database overflow (SQL Express limit)

Signs:

• Error PRIMARY filegroup is full.

• Archiving does not start.

Cause:
Free versions of Microsoft SQL Server Express have a database size limit of 10 GB.

Solution:

1. Delete statistics for closed periods (additional option No. 006).

2. Clear the “User Action Log” and the “Document Change Log”.

3. Run a Shrink operation on the database through SQL Server Management Studio.

4. If necessary, switch to the full version of SQL Server without limits.

How to check the result:
The database size has decreased, and the backup starts.

D. Problems with the “Application Server” service

Signs:

• Automatic backup does not run.

• Error Authorization Error. You must re-authorize when archiving to the cloud.

Solution:

1. Restart the TorgSoftService service.

2. Authorize again in Google Drive through “Scheduled Tasks”.

3. Check available free space in Google Drive.

How to check the result:
The archive is uploaded to the cloud without errors.

Final check

1. There is a file with the current date in the archive folder.

2. The archive has appeared in Google Drive (if configured).

3. The task log shows the status “Successful”.

How to avoid the problem

• Regularly clean old archives (keep only the last few).

• Close periods to reduce database load.

• Use cloud archive storage (option No. 057).

• Restart the server periodically.

Summary: order of checks

If the backup is not created — check the disk → access permissions → database size → service operation.
In 80% of cases, the problem is solved by freeing up disk space or correcting access permissions.

What to send to support

• Torgsoft version and database version.

• SQL Server type and version.

• The exact error text.

• A screenshot of “Scheduled Tasks”.