Comprehensive data protection for all workloads
foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » May 22, 2015 1:32 pm

Yes, please.

MAA
Enthusiast
Posts: 48
Liked: never
Joined: Apr 27, 2013 12:10 pm
Contact:

Re: Unable to truncate transaction logs.

Post by MAA » May 26, 2015 3:44 pm

After change vCenter Server from 5.5 (Windows) to 6.0 (appliance) on one of my SQL server job i get this warning:
Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MSSQLSERVER. Possible reasons: lack of permissions, or transaction log corruption.

foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » May 26, 2015 4:30 pm

Does this SQL server hold vCenter database or some unrelated one? Better contact support to take a look at guest logs.

jroot
Influencer
Posts: 15
Liked: never
Joined: Jan 29, 2010 2:30 pm
Full Name: Jim Root
Contact:

Re: Unable to truncate transaction logs.

Post by jroot » May 29, 2015 4:49 am

Foggy, I had the same error as MAA on a Windows 2003 server with SQL 2005 but I was able to correct it by editing the job, going to Guest Processing, clicking Applications, Highlighting the object, clicking Edit, Selecting the SQL tab, Checking "Do not truncate logs (requires simple recovery model), OK twice and Finish. The databases I have on this server all have circular logging and don't require truncation so it was blowing this warning every time the job ran. As soon as I made this change, the job completed successfully without this same warning. :D
Hope this helps,
Jim

foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » May 29, 2015 10:02 am

Jim, this is expected, if logs truncation is disabled, there's nothing to fail. ;)

DavidDarts
Novice
Posts: 9
Liked: never
Joined: Jul 09, 2015 3:03 am
Full Name: David Dartnell
Contact:

[MERGED] Receiving 'Failed to truncate transaction logs

Post by DavidDarts » Jul 09, 2015 3:10 am

Hi Everyone,

I am using VEEAM Backup & Replication 8 (v8.0.0.2030) to backup a Windows Server 2003 VM which is running MS SQL Server.

My backup job is failing with the warning message shown below -

Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MSSQLSERVER. Possible reasons: lack of permissions, or transaction log corruption.

If anybody can suggest how to fix this issue it will be greatly appreciated.

Kind Regards,

David

Vitaliy S.
Product Manager
Posts: 22517
Liked: 1469 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Unable to truncate transaction logs.

Post by Vitaliy S. » Jul 09, 2015 9:38 am

Did you have any successful job runs prior this failure? Can you please check that this SQL Server instance is up and running on the target VM?

DavidDarts
Novice
Posts: 9
Liked: never
Joined: Jul 09, 2015 3:03 am
Full Name: David Dartnell
Contact:

Re: Unable to truncate transaction logs.

Post by DavidDarts » Jul 09, 2015 10:47 pm

Hi Vitaliy,

I have checked, and the SQL Server instance is running. I have also determined that I am running Microsoft SQL Server 2000 (v 8.00.760).

Kind Regards,

David

alanbolte
Expert
Posts: 635
Liked: 172 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: Unable to truncate transaction logs.

Post by alanbolte » Jul 10, 2015 12:48 am 2 people like this post

SQL Server 2000 is not supported for log backup or truncation. If needed, you can create a support case to request a hotfix that will cause Veeam to skip unsupported and not-running instances of MS SQL. Otherwise, you can disable Application Aware Processing and use native SQL backup tools to deal with transaction logs. That said, you're talking about a SQL version that's End-of-Life, and an OS that's a week away, so if possible I'd recommend migrating the databases to something more recent.

dlieshout@client.nl
Service Provider
Posts: 42
Liked: 13 times
Joined: Dec 15, 2009 12:41 pm
Full Name: DaLi
Contact:

Re: Unable to truncate transaction logs.

Post by dlieshout@client.nl » Jul 14, 2015 2:31 pm

I did have a case ID# 00942559.
We do have lots of VM's at several customers with this warning since v8 Update 1/1a/1b. All VM's without any SQL or anything.

Final statement from Veeam: "So the workaround is to disable truncate for this particular VM. I realize that this is not good way to do this manually. This issue will be fixed in next release (or update)".
So we have to wait until Veeam will revert this warning-issue as it was before Update 1.

ITP-Stan
Service Provider
Posts: 96
Liked: 11 times
Joined: Feb 18, 2013 10:45 am
Full Name: Stan (IF-IT4U)
Contact:

Re: Unable to truncate transaction logs.

Post by ITP-Stan » Jul 15, 2015 2:22 pm

I had a similar issue on a couple of VM's that were terminal services hosts (RDP farm) after v8.0 Update2b. There was no SQL (express or standard) installed but there was a Windows Internal Database insalled together with the Server Resource Manager. The service was however disabled and not running, still VEEAM complained about the SQL transaction logs. I just set ignore SQL transaction log failures for these VM's since there is no real SQL on it.

Vitaliy S.
Product Manager
Posts: 22517
Liked: 1469 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Unable to truncate transaction logs.

Post by Vitaliy S. » Jul 16, 2015 12:22 pm

Stan,

I just had a quick discussion with our dev team regarding this issue. We should have a private hotfix that skips/ignores all stopped SQL Server instances and does not try to truncate logs for databases hosted on these instances. You can open a support case and try this hotfix in your infrastructure.

Thanks!

ITP-Stan
Service Provider
Posts: 96
Liked: 11 times
Joined: Feb 18, 2013 10:45 am
Full Name: Stan (IF-IT4U)
Contact:

Re: Unable to truncate transaction logs.

Post by ITP-Stan » Jul 20, 2015 9:40 am

I still have another (unrelated) support case open with VEEAM for a couple of weeks now. I'll have to wait for that one to get an update (if ever) before opening yet another case.

foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » Jul 20, 2015 11:07 am

dlieshout@client.nl wrote:I did have a case ID# 00942559.
We do have lots of VM's at several customers with this warning since v8 Update 1/1a/1b. All VM's without any SQL or anything.

Final statement from Veeam: "So the workaround is to disable truncate for this particular VM. I realize that this is not good way to do this manually. This issue will be fixed in next release (or update)".
I'd check with support regarding applicability of this hotfix (mentioned by Vitaliy above).

Tomsyr
Enthusiast
Posts: 27
Liked: 1 time
Joined: Jul 01, 2014 3:39 pm
Full Name: Tom Conklin
Contact:

Re: Unable to truncate transaction logs.

Post by Tomsyr » Oct 15, 2015 11:09 am

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.
It sounds like we're not alone with needing to implement this security best practice, so is there a work around?
TIA,
Tom

tsightler
VP, Product Management
Posts: 5328
Liked: 2175 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Unable to truncate transaction logs.

Post by tsightler » 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.

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

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

Post by macademy » 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

nielsengelen
Veeam Software
Posts: 2521
Liked: 526 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Updated to 8.0.0.2084, errors on one backup job

Post by nielsengelen » 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 Architect (VMCA)
http://foonet.be

Shestakov
Veeam Software
Posts: 6655
Liked: 665 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Unable to truncate transaction logs.

Post by Shestakov » 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!

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

Re: Unable to truncate transaction logs.

Post by macademy » 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

Gostev
SVP, Product Management
Posts: 24169
Liked: 3295 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Unable to truncate transaction logs.

Post by Gostev » Nov 12, 2015 9:55 pm

Could it be this issue > v8 Update 3 & SQL Log Truncation

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

[MERGED] Unable to truncate Microsoft SQL Server transaction

Post by stanleymok » 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

Shestakov
Veeam Software
Posts: 6655
Liked: 665 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Unable to truncate transaction logs.

Post by Shestakov » 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!

JosueM
Expert
Posts: 162
Liked: 10 times
Joined: Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado
Contact:

[MERGED] Unable to truncate log.

Post by JosueM » 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.

foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » Oct 27, 2016 2:25 pm

Josue, please review some hints provided in this thread and contact support in case nothing helps.

JosueM
Expert
Posts: 162
Liked: 10 times
Joined: Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado
Contact:

Re: Unable to truncate transaction logs.

Post by JosueM » Oct 27, 2016 2:35 pm

thanks foggy, will seek any help on this else I'll contact support

JosueM
Expert
Posts: 162
Liked: 10 times
Joined: Sep 01, 2012 2:53 pm
Full Name: Josue Maldonado
Contact:

Re: Unable to truncate transaction logs.

Post by JosueM » 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

foggy
Veeam Software
Posts: 17908
Liked: 1506 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to truncate transaction logs.

Post by foggy » 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.

the_mentor
Enthusiast
Posts: 48
Liked: 5 times
Joined: Jul 26, 2012 11:10 pm
Full Name: DeMentor
Contact:

[MERGED] Veeam job fails to truncate sql logs

Post by the_mentor » 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 ?
-DeMentor

phil.p
Novice
Posts: 5
Liked: 1 time
Joined: May 14, 2009 11:37 am
Full Name: Phil P
Contact:

Re: Unable to truncate transaction logs.

Post by phil.p » 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.

Post Reply

Who is online

Users browsing this forum: Exabot [Bot], Google [Bot] and 22 guests