![SQL Server full and transaction log backups completing but differential backups failing because of Veeam B&R configuration - Virtually Impossible SQL Server full and transaction log backups completing but differential backups failing because of Veeam B&R configuration - Virtually Impossible](https://i2.wp.com/www.virtuallyimpossible.co.uk/wp-content/uploads/2012/08/Veeam_BR_App_Processing001.png)
SQL Server full and transaction log backups completing but differential backups failing because of Veeam B&R configuration - Virtually Impossible
![KB2027: Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption." KB2027: Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."](https://cdn.veeam.com/content/veeam/en/knowledge-base/kb2027/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_2094723869/section-with-background-content/expander/expander-content/image/file.web.ntfile.png/AccountSpecified.png)
KB2027: Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."
![Failed to truncate Microsoft SQL Server transaction logs. Error code: 0x80004005 [TLS 1.0] - Veeam Backup & Replication 9.5 - Just Virtualise It Failed to truncate Microsoft SQL Server transaction logs. Error code: 0x80004005 [TLS 1.0] - Veeam Backup & Replication 9.5 - Just Virtualise It](http://kanecharles.com/wp-content/uploads/2017/03/Screen-Shot-2017-03-25-at-6.14.23-pm-800x391.png)
Failed to truncate Microsoft SQL Server transaction logs. Error code: 0x80004005 [TLS 1.0] - Veeam Backup & Replication 9.5 - Just Virtualise It
![Veeam Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption | Deiby Marcos Veeam Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption | Deiby Marcos](https://deibymarcos.files.wordpress.com/2016/02/console-warning.jpg)
Veeam Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption | Deiby Marcos
![Warning Veeam Backup & Replication 9.5: Unable to truncate Microsoft SQL Server transaction logs in fase di Backup di una VM SQL Server - RaffaeleChiatto.com Warning Veeam Backup & Replication 9.5: Unable to truncate Microsoft SQL Server transaction logs in fase di Backup di una VM SQL Server - RaffaeleChiatto.com](https://www.raffaelechiatto.com/wp-content/uploads/2020/02/veeam-truncate-01.png)