-
- Enthusiast
- Posts: 31
- Liked: 1 time
- Joined: Nov 18, 2013 6:10 pm
- Full Name: Sebastijan
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
The same probleme here, after v8 Patch2 ...
-
- Enthusiast
- Posts: 31
- Liked: 1 time
- Joined: Nov 18, 2013 6:10 pm
- Full Name: Sebastijan
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Nothing changed. Same problem.Andreas Neufert wrote:Just an Idea...
SQL2012 rights are too low, to allow truncation.
Please test it with the following.
SQL Management Studio - SQL-Secuity - Logins - NT Authority\system - Server Roles - Enable "sysadmin"
-
- Chief Product Officer
- Posts: 31607
- Liked: 6750 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hi Sebastijan - as explained earlier in this topic, issues with log truncation were simply not reported until Update 2, even if they existed. Update 2 merely started reporting those. If no suggestion in this topic help, feel free to open a support case for assistance in finding the issue with your SQL Server that prevents log from being truncated.
-
- VP, Product Management
- Posts: 6771
- Liked: 1417 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Jun 04, 2015 7:45 am
- Full Name: Thor Egil
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Thanks but we fixed it
Went for best practice and defined service accounts for Our SQL servers to fix it.
Went for best practice and defined service accounts for Our SQL servers to fix it.
-
- Service Provider
- Posts: 26
- Liked: 5 times
- Joined: Apr 05, 2015 8:27 am
- Full Name: Marco Broeken
- Location: Rotterdam
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
We also have the same issue at a client. Updated to U2 and lateest U2b patch yesterday.
Running in a lot of those errors on non SQL servers:
The server finds the MICROSOFT#SSEE registry key and tries to flush the logs of the non-SQL servers (and this fails)
Running in a lot of those errors on non SQL servers:
Code: Select all
Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate transaction logs for SQL instances: MICROSOFT##SSEE. Possible reasons: lack of permissions, or transaction log corruption.
Veeam Cloud Connect Provider
More info:
https://www.xtradesktop.com/backup/
More info:
https://www.xtradesktop.com/backup/
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Marco, looks like you have an instance of Windows Internal Database on this server. There's a fix available through support that allows to skip such instances during AAIP, since there's nothing to truncate there, anyway.
-
- Enthusiast
- Posts: 90
- Liked: 23 times
- Joined: Jun 17, 2012 1:09 pm
- Full Name: Nev
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
hi Foggy, will this fix be included in a future release? (We're currently using 8.0.0.2021). If so, we will put up with the warning.foggy wrote:Marco, looks like you have an instance of Windows Internal Database on this server. There's a fix available through support that allows to skip such instances during AAIP, since there's nothing to truncate there, anyway.
Thanks.
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
It should be included in the next major release, which is not a matter of the nearest future. So I recommend requesting the hotfix.
-
- Influencer
- Posts: 17
- Liked: 3 times
- Joined: Dec 11, 2012 9:11 pm
- Full Name: Luigi Rosa
- Location: Italy
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Same problem here on a 2003 Server with MICROSOFT##SSEE after applying v8 Patch2.
It's a production server that will be decommissioned in a few months, according to master.mdf date stamp, MICROSOFT##SSEE was up last time in 2012.
Really don't want to mess with a server that os going to die, isn't it possible to tell Veeam to skip instances that are not up and running?
It's a production server that will be decommissioned in a few months, according to master.mdf date stamp, MICROSOFT##SSEE was up last time in 2012.
Really don't want to mess with a server that os going to die, isn't it possible to tell Veeam to skip instances that are not up and running?
-
- Product Manager
- Posts: 20285
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
As foggy's mentioned, the fix should be available through support. So, you might want to open a ticket and refer to this topic. Thanks.
-
- Influencer
- Posts: 21
- Liked: 1 time
- Joined: Feb 06, 2013 7:39 pm
- Full Name: Mike Barnes
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hello, I had this issue on our SQL servers and resolved most of them using the recommended permission updates. However, I have a SQL 2012 server that still gives the error.
I can't figure out how to update the permissions on the MSSQLSERVERTAB database, anyone know how to do it?
Thanks!
I can't figure out how to update the permissions on the MSSQLSERVERTAB database, anyone know how to do it?
Code: Select all
9/30/2015 11:47:23 PM :: Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate transaction logs for SQL instances: MSSQLSERVER MSSQLSERVERTAB. Possible reasons: lack of permissions, or transaction log corruption.
-
- Chief Product Officer
- Posts: 31607
- Liked: 6750 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hi, please open a support case, and our engineers will help you to update permission on this database over a webex session. Thanks!
-
- Novice
- Posts: 6
- Liked: never
- Joined: Feb 21, 2011 5:41 pm
- Full Name: Mark Bell
- Contact:
[MERGED] error truncating SQL logs
Over the last couple of days I've been seeing this error message when trying to back up a SQL server:
Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption. (System.Runtime.InteropServices.COMException)
I'm not aware of any changes made on the server that would be causing this. All the databases appear to be working fine. Any thoughts?
Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption. (System.Runtime.InteropServices.COMException)
I'm not aware of any changes made on the server that would be causing this. All the databases appear to be working fine. Any thoughts?
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Mark, please contact technical support to get the newly available Veeam B&R v8 Update 3.
-
- Enthusiast
- Posts: 53
- Liked: 3 times
- Joined: Aug 09, 2015 5:48 pm
- Full Name: Chris Lane
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hi,
We upgraded to update 3 and the following is now happening on two servers with MICROSOFT##WID.
Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
Ideas?
We upgraded to update 3 and the following is now happening on two servers with MICROSOFT##WID.
Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
Ideas?
-
- VP, Product Management
- Posts: 27138
- Liked: 2727 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
What's your case ID, so that our dev team could take a look?
-
- Enthusiast
- Posts: 53
- Liked: 3 times
- Joined: Aug 09, 2015 5:48 pm
- Full Name: Chris Lane
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
No case ID I'm afraid, see: -
http://forums.veeam.com/veeam-backup-re ... 30710.html - post 6 so I assume you can't help me.
For what its worth (before my posts are removed) I have added sysadmin rights to the domain account used in the job and to NT AUTHORITY/SYSTEM but to no avail.
http://forums.veeam.com/veeam-backup-re ... 30710.html - post 6 so I assume you can't help me.
For what its worth (before my posts are removed) I have added sysadmin rights to the domain account used in the job and to NT AUTHORITY/SYSTEM but to no avail.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hello Chris,
We are asking you to contact Veeam support because it`s the fastest way to solve the problem. We`ve just released the 3rd update and haven`t faced the similar issue. Troubleshooting in the forums less effective and against forums rules. So, please contact them.
Thanks!
We are asking you to contact Veeam support because it`s the fastest way to solve the problem. We`ve just released the 3rd update and haven`t faced the similar issue. Troubleshooting in the forums less effective and against forums rules. So, please contact them.
Thanks!
-
- Enthusiast
- Posts: 53
- Liked: 3 times
- Joined: Aug 09, 2015 5:48 pm
- Full Name: Chris Lane
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hi Nikkita,
Firstly I believe I owe Veeam and my reseller an apology. I was unaware that the paid support was included as I didn't set up the Veeam install so was unaware of the existence of the Support ID etc.
Case ID = 01080564, please don't hesitate to let me know if you require more information/logs.
Firstly I believe I owe Veeam and my reseller an apology. I was unaware that the paid support was included as I didn't set up the Veeam install so was unaware of the existence of the Support ID etc.
Case ID = 01080564, please don't hesitate to let me know if you require more information/logs.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Thanks Chris,
All users on an active maintenance are eligible to obtain the support.
No more logs are needed here, your support engineer is to collect them. We will keep track of the issue investigation.
All users on an active maintenance are eligible to obtain the support.
No more logs are needed here, your support engineer is to collect them. We will keep track of the issue investigation.
-
- Veteran
- Posts: 338
- Liked: 35 times
- Joined: Jan 20, 2012 2:36 pm
- Full Name: Christensen Farms
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
I haven't opened a case yet, but I have the same issue. Right after I installed update 3 I now get this warning on one of our servers with the Windows Internal Database:
Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Our QA team is working on the issue solution. The explanation was given in the related topic:
Thanks!foggy wrote:The "unable to truncate" warnings do not actually mean that something is unsupported, they just tell that logs for the particular database were not truncated. Everything else is working fine and logs are truncated where they should be. It is just some changes in instance detection logic introduced by Update 3 (to fix other issues around this functionality) that result in improper processing of internal databases (where there are no logs to truncate, anyway). R&D is currently looking into this and I believe the solution will be found soon.
-
- Veteran
- Posts: 338
- Liked: 35 times
- Joined: Jan 20, 2012 2:36 pm
- Full Name: Christensen Farms
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
This is the explanation given to me by support:
Instance 'MICROSOFT##WID' is internal MS instance and doesn't require log truncation. If this is the only SQL instance on server, the solution is to chose 'Perform copy only' on setting of processing of that VM. You choose this in 'Guest Processing' step -> Applications -> choose VM, 'Edit' (this screen: http://helpcenter.veeam.com/backup/80/v ... ob_vss.png)
I told them I understand this, but up until I put on update 3 I never got this warning. So while there is no problem, it is a different behavior.
Case #01081234
Instance 'MICROSOFT##WID' is internal MS instance and doesn't require log truncation. If this is the only SQL instance on server, the solution is to chose 'Perform copy only' on setting of processing of that VM. You choose this in 'Guest Processing' step -> Applications -> choose VM, 'Edit' (this screen: http://helpcenter.veeam.com/backup/80/v ... ob_vss.png)
I told them I understand this, but up until I put on update 3 I never got this warning. So while there is no problem, it is a different behavior.
Case #01081234
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
That's why we are going to address this in a timely manner. Thanks for opening a case.
-
- Enthusiast
- Posts: 39
- Liked: 4 times
- Joined: Feb 26, 2014 4:42 am
- Full Name: Jed Parkes
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
I just updated to update 3 and i am also now getting the error.
14/10/2015 9:13:34 PM :: Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
Is there a fix for this ?
14/10/2015 9:13:34 PM :: Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate transaction logs for SQL instances: MICROSOFT##WID. Possible reasons: lack of permissions, or transaction log corruption.
Is there a fix for this ?
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Yes, please contact technical support to get it.
-
- Enthusiast
- Posts: 50
- Liked: 5 times
- Joined: Oct 14, 2015 10:12 pm
- Full Name: Tom Newman
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
We have just started evaluating the product and have the same problem. Is there any way to get the patch if you haven't yet purchased?
Thanks, Tom
Thanks, Tom
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Hello Tom and welcome to the community!
You can contact the technical support even having a trial version of the product.
Thanks!
You can contact the technical support even having a trial version of the product.
Thanks!
-
- Enthusiast
- Posts: 50
- Liked: 5 times
- Joined: Oct 14, 2015 10:12 pm
- Full Name: Tom Newman
- Contact:
Re: Truncating SQL transaction logs - SUDDENLY trouble
Thanks, will do
Who is online
Users browsing this forum: Andreas Neufert, Bing [Bot], Google [Bot] and 98 guests