Unable to truncate transaction logs.

Availability for the Always-On Enterprise

Re: Unable to truncate transaction logs.

Veeam Logoby tsightler » Thu Oct 15, 2015 1:03 pm

Tomsyr wrote:We needed to move service accounts with DA rights into a special group that now has deny 'interactive logins', so now we get unable to truncate SQL server transaction logs, etc... 'Win32 error:Logon failure: the user has not been granted the requested logon type at this computer.'.
Due to passwords expiring, we need to have service accounts NOT expire, and since service accounts have 'known' passwords, we need to prevent interactive logins.

I'm not sure if there's any way to prevent requiring "known passwords", but certainly the account does not need to be a Domain Admin. To perform VSS freeze the account used for AAIP needs to be a Local Admin, and to truncate logs the account must have db_backupoperator role on any databases in FULL or Bulk recovery mode, or you can assign SQL sysadmin rights to the account to allow it to truncate logs on any database.
tsightler
Veeam Software
 
Posts: 4687
Liked: 1698 times
Joined: Fri Jun 05, 2009 12:57 pm
Full Name: Tom Sightler

[MERGED] Updated to 8.0.0.2084, errors on one backup job

Veeam Logoby macademy » Thu Nov 12, 2015 9:17 am

Hi,

Since updating to 8.0.0.284 we are seeing a warning on one of our servers in the job log. The warning is:

"Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to enumerate SQL instance on host. Failed to retrieve the configuration parameters of the [PsShutdownSvc] service. Win32 error:The system cannot find the file specified. Code: 2"

This is an old Windows 2003 server, running SQL Server 2005.

All of our other SQL servers (running 2008 R2 and SQL 2008) are backing up fine.

Any ideas how I can fix this?

Thanks
macademy
Enthusiast
 
Posts: 27
Liked: 3 times
Joined: Mon Nov 10, 2014 4:07 pm
Full Name: Ian Cullen

Re: Updated to 8.0.0.2084, errors on one backup job

Veeam Logoby vmniels » Thu Nov 12, 2015 9:20 am

Please have a look at http://www.veeam.com/kb2027 - if the error still occurs then please contact support.
VCP-DCV
Veeam Certified Engineer
http://foonet.be
vmniels
Veeam Software
 
Posts: 1385
Liked: 311 times
Joined: Mon Jul 15, 2013 11:09 am
Full Name: Niels Engelen

Re: Unable to truncate transaction logs.

Veeam Logoby Shestakov » Thu Nov 12, 2015 9:31 am

Hi Ian,
Did it work with no issues before the update? What version have you updated from?
By design VBR supports transaction log backups for Microsoft SQL Server 2005, so contacting the support team will also help.
Thanks!
Shestakov
Veeam Software
 
Posts: 4530
Liked: 362 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: Unable to truncate transaction logs.

Veeam Logoby macademy » Thu Nov 12, 2015 9:41 am

We upgraded from 8.0.0.2030 and there were no errors then. We upgraded to 8.0.0.2084 two days ago and both nights have generated a warning on this one server.

I've checked http://www.veeam.com/kb2027 as suggested by vmniels on my original thread (thanks for moving it) but none of the suggestions seemed to apply, the veeamguesthelper log shows this:

Code: Select all
12/11/2015 00:38:18   4828                      Truncating SQL logs
12/11/2015 00:38:18   4828                              Enumerating MS SQL instances by service names.
12/11/2015 00:38:18   4828                              Enumerating MS SQL instances by service names.. Failed.
12/11/2015 00:38:18   4828                      Truncating SQL logs. Failed.
12/11/2015 00:38:18   4828  INFO        RPC: truncation SQL logs.. Failed.
12/11/2015 00:38:18   4828  ERR     BlobCall() error.
12/11/2015 00:38:18   4828  ERR         Failed to process 'TruncateSQLLog' command.
12/11/2015 00:38:18   4828  ERR         Failed to enumerate SQL instance on host.
12/11/2015 00:38:18   4828  ERR         Failed to retrieve the configuration parameters of the [PsShutdownSvc] service.
12/11/2015 00:38:18   4828  ERR         Win32 error:The system cannot find the file specified.
12/11/2015 00:38:18   4828  ERR          Code: 2


I've restarted the server just now to see if this makes any difference and will contact support tomorrow if the warning still occurs.

Thanks
macademy
Enthusiast
 
Posts: 27
Liked: 3 times
Joined: Mon Nov 10, 2014 4:07 pm
Full Name: Ian Cullen

Re: Unable to truncate transaction logs.

Veeam Logoby Gostev » Thu Nov 12, 2015 9:55 pm

Could it be this issue > v8 Update 3 & SQL Log Truncation
Gostev
Veeam Software
 
Posts: 21166
Liked: 2305 times
Joined: Sun Jan 01, 2006 1:01 am
Full Name: Anton Gostev

[MERGED] Unable to truncate Microsoft SQL Server transaction

Veeam Logoby stanleymok » Sat May 28, 2016 1:13 am

Hi all,

I am using Veeam Backup & Replication v9 to backup SQL server, once backup job completed, it showed a warning message as below:

Unable 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. .

Anyone can help?

Thanks a lot,

Stanley
stanleymok
Novice
 
Posts: 8
Liked: never
Joined: Fri May 13, 2016 3:54 am

Re: Unable to truncate transaction logs.

Veeam Logoby Shestakov » Sat May 28, 2016 7:52 pm

Hi Stanley,
Please provide support case number as required when posting questions regarding technical errors.
Also, please review the topic for possible solutions.
Thanks!
Shestakov
Veeam Software
 
Posts: 4530
Liked: 362 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

[MERGED] Unable to truncate log.

Veeam Logoby JosueM » Thu Oct 27, 2016 2:21 pm

Good day everyone,

This backup job mssql 2008 VM was working fine till last night displayed this warning:

Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate SQL server transaction logs for instances: . See guest helper log. .

I was unable to find something about the error message since is very general, any idea about this? or where to find the "guest helper log"?

Veeam 9.0.0.1491 here. thanks in advance.
JosueM
Expert
 
Posts: 145
Liked: 9 times
Joined: Sat Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Thu Oct 27, 2016 2:25 pm

Josue, please review some hints provided in this thread and contact support in case nothing helps.
foggy
Veeam Software
 
Posts: 14346
Liked: 1054 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Unable to truncate transaction logs.

Veeam Logoby JosueM » Thu Oct 27, 2016 2:35 pm

thanks foggy, will seek any help on this else I'll contact support
JosueM
Expert
 
Posts: 145
Liked: 9 times
Joined: Sat Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado

Re: Unable to truncate transaction logs.

Veeam Logoby JosueM » Thu Oct 27, 2016 2:42 pm

where do you find the veeamguesthelper ??

macademy wrote:We upgraded from 8.0.0.2030 and there were no errors then. We upgraded to 8.0.0.2084 two days ago and both nights have generated a warning on this one server.

I've checked http://www.veeam.com/kb2027 as suggested by vmniels on my original thread (thanks for moving it) but none of the suggestions seemed to apply, the veeamguesthelper log shows this:

Code: Select all
12/11/2015 00:38:18   4828                      Truncating SQL logs
12/11/2015 00:38:18   4828                              Enumerating MS SQL instances by service names.
12/11/2015 00:38:18   4828                              Enumerating MS SQL instances by service names.. Failed.
12/11/2015 00:38:18   4828                      Truncating SQL logs. Failed.
12/11/2015 00:38:18   4828  INFO        RPC: truncation SQL logs.. Failed.
12/11/2015 00:38:18   4828  ERR     BlobCall() error.
12/11/2015 00:38:18   4828  ERR         Failed to process 'TruncateSQLLog' command.
12/11/2015 00:38:18   4828  ERR         Failed to enumerate SQL instance on host.
12/11/2015 00:38:18   4828  ERR         Failed to retrieve the configuration parameters of the [PsShutdownSvc] service.
12/11/2015 00:38:18   4828  ERR         Win32 error:The system cannot find the file specified.
12/11/2015 00:38:18   4828  ERR          Code: 2


I've restarted the server just now to see if this makes any difference and will contact support tomorrow if the warning still occurs.

Thanks
JosueM
Expert
 
Posts: 145
Liked: 9 times
Joined: Sat Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Thu Oct 27, 2016 2:51 pm

This log is located on the guest VM, you can find the full path in the mentioned KB article.
foggy
Veeam Software
 
Posts: 14346
Liked: 1054 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

[MERGED] Veeam job fails to truncate sql logs

Veeam Logoby the_mentor » Wed Mar 22, 2017 4:28 pm

Hi Everyone,
On a few of my sql servers i get the following warning:

Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to call RPC function 'Vss.TruncateSqlLogs': 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

Any ideas on what i can do to solve it ?
the_mentor
Enthusiast
 
Posts: 37
Liked: 5 times
Joined: Thu Jul 26, 2012 11:10 pm
Full Name: DeMentor

Re: Unable to truncate transaction logs.

Veeam Logoby phil.p » Fri Mar 24, 2017 1:15 pm 1 person likes this post

Thought I'd post my fix to the error mentioned by the_mentor as came across it recently. The issue (for me) seems to be caused by the SQL OLE Provider (that Veeam is using), we started disabling TLS1.0 support on our servers after running some vulnerability scans across the network. Turns out the OLE DB Provider doesn't support TLS1.1 or 1.2 so breaks when this change is made, if you look in the guesthelper log on the guest VM the following WARN lines will be seen:

Code = 0x80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.

Came across this thread while looking into it so hopefully this will help someone else who sees this issue. For now I've resolved by re-enabling TLS1.0 on our SQL servers as it's not a critical requirement just starting to become best practice, hopefully Veeam will move to a newer provider with support for TLS1.2 in the future.
phil.p
Novice
 
Posts: 5
Liked: 1 time
Joined: Thu May 14, 2009 11:37 am
Full Name: Phil P

PreviousNext

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: EIvanov, Hauke and 20 guests