Challenge
When backing up a machine running a Microsoft SQL server where TLS 1.0 has been disabled, a job may fail with the error code 0x80004005 [TLS 1.0].
The following warning will be found on the server that is being protected by either Veeam Backup & Replication or Veeam Agent for Microsoft Windows, the path to the file containing this warning is listed below.
- For a VM being processed by Veeam Backup & Replication:
%ProgramData%VeeamBackupVeeamGuestHelper_<dd.mm.yyyy>.log - For a server being backed up using Veeam Agent for Microsoft Windows:
%ProgramData%VeeamEndpoint<job_name>Job.Backup.log
INFO Connecting to mssql, connection string: Provider='sqloledb';Data Source='(local)SQLINSTANCENAME';Integrated Security='SSPI';Persist Security Info=False, timeout: 15
WARN Code = 0x80004005 WARN Code meaning = Unspecified error
WARN Source = Microsoft OLE DB Provider for SQL Server
WARN Description = [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.
WARN COM error: Code: 0x80004005
Cause
The SQL Server being protected by Veeam is using a SQL OLE DB provider which does not support TLS 1.2
Solution
Behavior Change Starting with Veeam Backup & Replication v11
Starting with Veeam Backup & Replication v11 the Microsoft OLE DB Provider (MSOLEDBSQL) will be used first to initiate communication. In all previous version only the SQLOLEDB provider was used. Also, starting with Veeam Backup & Replication v11 the software will first attempt to use MSOLEDBSQL first, then failover to Native SQL Client Provider, and then failover to using SQLOLEDB Provider. If Veeam Backup & Replication fails over to using SQLOLEDB provider the job will report «Using deprecated provider» warning.
It is therefore advisable if you are facing this issue to upgrade to Veeam Backup & Replication v11.
The direct solution to this situation is to review available updates for the SQL Server that is having this issue and ensure that TLS 1.2 is supported by the Microsoft OLE DB provider for SQL Server.
Please review: https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
As a workaround, it is possible to force Veeam to request that the ‘Native SQL Client Provider’ be used instead of SQLOLEDB. This is done by adding a registry value to the Guest OS of the machine being protected by Veeam.
Please review the scenarios below and use the location and value specified:
- For a VM being protected by Veeam Backup & Replication:
- Location: HKLMSOFTWAREVeeamVeeam Backup and Replication
- Value: UseSqlNativeClientProvider
- Type: DWORD
- Data: 1
- For machines being protected (managed or standalone) by Veeam Agent for Microsoft Windows:
- Location: HKLMSOFTWAREVeeamVeeam Endpoint Backup
- Value: UseSqlNativeClientProvider
- Type: DWORD
- Data: 1
- For SQL Failover Clusters protected by Veeam Agent for Microsoft Windows via a job in Veeam Backup & Replication with the option Backup logs periodically an additional value must be specified (the value in HKLMSOFTWAREVeeamVeeam Endpoint Backup also still remains the place).
- Location: HKLMSOFTWAREVeeamVeeam Backup and Replication
- Value: UseSqlNativeClientProvider
- Type: DWORD
- Data: 1
No server restart is required, registry key will be checked on next job run.
More Information
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
1 minute read
Description:
You will be getting errors/warnings stating:
1
Failed to truncate Microsoft SQL Server transaction logs. Details: Error code: 0x80004005 Failed to invoke func [TruncateSqlLogs]: Unspecified error. Failed to process TruncateSQLLog command. Failed to truncate SQL server transaction logs for instances: . See guest helper log. . Error code: 0x80004005 Failed to invoke func [TruncateSqlLogs]: Unspecified error. Failed to process TruncateSQLLog command. Failed to truncate SQL server transaction logs for instances: See guest helper log.
To Resolve:
-
On the SQL server with this error, navigate to
C:ProgramDataVeeamBackupand view the log:1 2 3 4 5
WARN Cannot truncate SQL logs for database: (DBNAME) Code = 0x80040e31 6/22/2016 1:12:46 AM 4640 WARN Code meaning = IDispatch error #3121 6/22/2016 1:12:46 AM 4640 WARN Source = Microsoft OLE DB Provider for SQL Server 6/22/2016 1:12:46 AM 4640 WARN Description = Query timeout expired 6/22/2016 1:12:46 AM 4640 WARN No OLE DB Error Information found: hr = 0x80004005
-
Open up SQL Server Management Studio and add the following user to the database that is failing the credentials:
1 2 3 4
User type: SQL user with login User name: System Login name: NT AUTHORITYSYSTEM Default_schema: db_backupoperator
-
Next add the following regkeys on the SQL server:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Hive: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeVeeaMVeeam Backup and Replication and HKEY_LOCAL_MACHINESOFTWAREVeeaMVeeam Backup and Replication Name: SqlExecTimeout Type: DWORD Value: 600 Name: SqlLogBackupTimeout Type: DWORD Value: 3600 Name: SqlConnectionTimeout Type: DWORD Value: 300 NOTE: These values are decimal values. I also had to add the following keys to the Wow6432Node hive: VeeaMVeeam Backup and Replication **Yes that is how it is supposed to be spelled with a capital M on the VeeaM key, according to support.
References:
“Failed to Truncate transaction logs on ONE db in instance”
“Job reports warning “Failed to truncate transaction logs for SQL instances…”
11 Replies
-
It looks like it failed creating one of the services.
Did you try «Run As Administrator» to see if that is it?
Was this post helpful?
thumb_up
thumb_down
-
That looks like a confusing error message. Half the sentence is missing ?!
Was this post helpful?
thumb_up
thumb_down
-
CyberSecHakr wrote:
It looks like it failed creating one of the services.
Did you try «Run As Administrator» to see if that is it?
Yes… I do this as a standard practice, when executing any installation.
Was this post helpful?
thumb_up
thumb_down
-
Kirsten (Veeam) wrote:
That looks like a confusing error message. Half the sentence is missing ?!
oh wow…. someone from Veeam confused by an error generated by a Veeam software… How reassuring!!!
Was this post helpful?
thumb_up
thumb_down
-
Possible corrupted installation file? You might try re-downloading it.
Was this post helpful?
thumb_up
thumb_down
-
Hi @Veet-
I have just never seen an error message that has half of the sentence missing and not very complete. @northlandeng’s idea might be something you want to try out.
If it persists, you should contact support here.
Was this post helpful?
thumb_up
thumb_down
-
Northlandeng wrote:
Possible corrupted installation file? You might try re-downloading it.
Yes… the thought did occur to me, so I re-downloaded the installation … no dice …same error
Was this post helpful?
thumb_up
thumb_down
-
Doesn’t the attached log-file provide any indication of the complete error message, and/or what’s causing the installation to fail ?
Was this post helpful?
thumb_up
thumb_down
-
Info: System.ComponentModel.Win32Exception (0x80004005): Fatal error during installation
From my searching online, i keep getting the error occuring when using Veeam Agent backup, which might not be of help here since you stated you are trying to install Veeam Backup & Replication. Even with the free editions, support is available. You can open a case here:
https://www.veeam.com/support.html Opens a new window
2 found this helpful
thumb_up
thumb_down
-
Hello,
Contacted Veeam support …. After almost 2hrs on-call, we managed to resolve the issue…. It was something to do with the SQL database instance…
Much appreciate, the time and patience of Veeam support agent Ruoy …. Thank you….
0 of 1 found this helpful
thumb_up
thumb_down
-
I realize I am late to this thread. Figured I’d updated it for the next person.
Just ran into this problem with v3.0.1.1039.
I uninstalled the 3 SQl pieces associated with Veeam; MS SQL Svr 2012 Mgmt Objt x64, MS SQL Svr 2012 Express LocalDB, & MS Sys CLR Types for SQL Svr 2012 x64. I was then able to update / install Veeam.
Was this post helpful?
thumb_up
thumb_down
I recently updated Veeam Backup and Replication from 9.0 update 2 to 9.5 update 2. Since completing the update my nightly backups have started having multiple backup failures on random guest OS running Windows. I run VMware ESXi 5.5 backing up to HP StoreOnce using CIFS. There were absolutely no VSS errors prior to the upgrade to Veeam 9.5. The guest systems having issues are a mix of Windows server 2008 R2 and 2012 R2 and Windows clients 7 and 8.1. There are three different backup jobs, each has guests experiencing the issue. I also have two 2003 servers that have not experienced the issue.
I have contacted Veeam support and provided event logs from a few target systems and Veeam Backup and Replication. They have told me to contact Microsoft stating it is a VSS issue and not Veeam. Microsoft will only test one guest per incident for this which does not help resolve the issue.
I am curious if anyone else running Veeam Backup and Replication has upgraded to 9.5 and experienced these issues, if so have you been able to resolve the problem?
Also important to note, for the backups that fail on first run, some succeed on first retry, those that fail on first retry succeed on second retry. I have not had any systems that have not had a successful backup after 3 attempts, this tells me Windows systems are ok otherwise I would expect the backup to fail every time.
On Windows machines that experience the error the following event log entry is found:
Level Date and Time Source Event ID Task Category
Information 9/17/2017 1:07:40 AM VSS 12349 None Volume Shadow Copy Service warning: The writer spent too much time processing it’s Freeze notification. This can cause this writer as well as other writers on the system time to time out and fail shadow-copy creation.
Operation:
Freeze Event
Context:
Execution Context: Writer
Writer Class Id: {18ec56c4-e042-497d-a3d4-eea24284fa03}
Writer Name: VeeamFreezeWriter
Writer Instance ID: {a6587b63-7e8f-4a6a-b326-5a06df951639}
Every morning Veeam back up status reports shows one of the following errors for random systems…
Unable to release guest. Error: Failed to call RPC function ‘Vss.Unfreeze’: Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Unfreeze error: [. Freeze timeout occurred. Total freeze time: 60 seconds].
Error: Failed to prepare VM for processing: Failed to call RPC function ‘Vss.Unfreeze’: Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Unfreeze error: [. Freeze timeout occurred. Total freeze time: 60 seconds].
Unable to release guest. Error: VSSControl: Failed to freeze guest over network, wait timeout
Error: Failed to prepare VM for processing: VSSControl: Failed to freeze guest over network, wait timeout
What I have done so far:
1. Verified all systems having issues are fully up-to-date with windows updates
2. Disabled UAC on a few systems as a test (found a Veeam KB article the indicated this could fix VSS issues)
3. Reviewed status of VSS writers to look for any in a error state (vssadmin list writers). No errors found
4. Opened a case with Veeam support and provided logs from Veeam and event logs from two problem servers
5. Opened a case with Microsoft (as instructed by Veeam support) to resolve VSS issues
6. Reviewed all problem systems to identify if there is anything in common such as same ESXi host, same LUN, same VLAN/subnet. The only thing in common is Veeam back up.
Any help would be appreciated. Thanks
While using Veeam Backup & Replication 9.5 to export an Exchange mailbox to a PST file I encountered the following error:
Unspecified error
0x80004005 Description: Unspecified error (Source: MAPIInitialize)
Office 2013 64bit is installed on the server as required and the mailbox is in an Exchange 2010 environment.
A quick dig around the Veeam Exchange Explorer logs (they are located in C:ProgramDataVeeamBackupExchangeExplorerLogs) didn’t turn up anything useful:
05/03/2019 17:22:29 1 (11560) Error: Unspecified error
05/03/2019 17:22:29 1 (11560) Type: System.Exception
05/03/2019 17:22:29 1 (11560) Stack:
05/03/2019 17:22:29 1 (11560) at Veeam.MAPI.Core.ErrorComposer.Throw(String uiMessage, String logMessage)
at Veeam.MAPI.MapiVerify.Throw(Int32 hr, String uiMessage, String logMessage)
at Veeam.MAPI.MapiInit..ctor()
05/03/2019 17:22:29 1 (11560) Error: 0x80004005 Description: Unspecified error (Source: MAPIInitialize)
Although I couldn’t identify the issue with Office 2013 the problem was solved by uninstalling it and replacing it with Office 2010!
- Remove From My Forums
-
Question
-
Hello,
These days when I try to open a shared folder in other machines(including XP, Vista, 7, Server 2003/2008) from my own Windows 7 Ultimate pc, I get a Network Error dialog saying:
Windows cannot access \machinesharedfolder, error code 0x80004005, unspecified error.It aslo failed with IP. And I have disable the Firewall
But the other XP, Vista, Server 2003 and Server 2008 machines can reach each other and they even can open the shared fodler from my Windows 7.
It’s too strange. Maybe you can give me some useful suggestion.
Thanks.
Xiaofeng
问题要简单，错误须详细@错误/异常/堆栈信息+操作系统+软件版本+all the context of the issue Hope Helpful | http://www.leoworks.net
Answers
-
In case this helps… I was having a similar problem on a new laptop (Toshiba) with Windows 7 Home Premium using wifi. Accessing a share on an XP desktop «suddenly» stopped working.
It appears the issue is related to the Microsoft Virtual WiFi Miniport Adapter, which was evidently installed with a driver update around the first week of April. Even though the adapter is disabled, it appears that any changes that you make to the
settings on your «normal» wireless adapter also need made on this one. For me, this included enabling NetBIOS over TCP/IP (under IPv4 settings) and ensuring IPv6 was disabled. Again, THE INTERFACE IS DISABLED, but these changes still
«magically» made my sharing work immediately.-
Marked as answer by
Friday, May 7, 2010 2:34 AM
-
Marked as answer by