When taking an application-aware backup of a VM running Microsoft SQL (2014 in this case) with TLS 1.0 disabled, you may be presented with a 0x80004005 error regarding SQL log truncation failure.
Disabling TLS 1.0 on your Microsoft SQL Database will result in the following symptoms:
- Veeam console reports “Failed to truncate Microsoft SQL Server transaction logs. Details: Error code: 0x80004005”
- Guest Agent logs in C:\ProgramData\Veeam\Backup\VeeamGuestHelper_ddmmyyyy.log contain lines such as:
Cannot truncate SQL logs for instance: .
22/03/2017 3:12:02 PM 4404 WARN Code = 0x80004005
22/03/2017 3:12:02 PM 4404 WARN Code meaning = Unspecified error
22/03/2017 3:12:02 PM 4404 WARN Source = Microsoft OLE DB Provider for SQL Server
22/03/2017 3:12:02 PM 4404 WARN Description = [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
Modifying the following DWORD to 0 should produce the same symptoms as above:
Updating the DWORD back to 1 (thus enabling TLS 1.0) should make the symptoms disappear, although this is bad practice as ideally TLS 1.0 should not be in use.
Add the following DWORD entry on the affected VM that is running Microsoft SQL:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\