Jump to content
Welcome to our new Citrix community!
  • 1

Issues With VSS Sqlwriter on 7.16


Chris Gregson1709155862

Question

Hi guys - After upgrading to 7.16 I am seeing a warning from Veeam Backup & Replication 9.5 Update 2 when performing a backup.

 

VSS: Backup job failed. Cannot notify writers about the 'BACKUP FINISH' event. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{95c90279-ea8b-4eae-8b01-c2dbb6484700}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f4].

 

When checking the state of SqlServerWriter with vssadmin list writers I see

 

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {95c90279-ea8b-4eae-8b01-c2dbb6484700}
   State: [12] Failed
   Last error: Non-retryable error

 

This issue only started happening after the 7.16 update - I'm using SQL 2012 Express Localdb which is updated to Service Pack 4.   This particular server is a delivery controller and also runs Citrix Studio.  Oddly - I noticed after the upgrade that SQL 2014 Express Localdb had been installed also - not entirely sure what the purpose of this is.

 

Any help, much appreciated

Link to comment

5 answers to this question

Recommended Posts

  • 0

Hi misan1834,

 

I have not found a solution yet, but have found a lot of potential causes. If you have resolved your problem do you mind posting it? If I find one later I'll do the same.

I noticed the same error from my other delivery controller (load balanced) a few weeks ago, and this one today.

It seems to be intermittent.

 

I am running 7.13, Server 2012 R2, SQL Server 2014 Express Localdb (2012 isn't installed for me)

 

VSS: Backup job failed. Cannot notify writers about the 'BACKUP FINISH' event. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{237f0ddd-2a35-4f8e-bb9e-ab19931f6d1b}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f4].

 

Writer name: 'SqlServerWriter'

Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

Writer Instance Id: {237f0ddd-2a35-4f8e-bb9e-ab19931f6d1b

State: [12] Failed

Last error: Non-retryable error

Link to comment
  • 0
14 hours ago, Lawrence Burford1709157535 said:

Hi misan1834,

 

I have not found a solution yet, but have found a lot of potential causes. If you have resolved your problem do you mind posting it? If I find one later I'll do the same.

I noticed the same error from my other delivery controller (load balanced) a few weeks ago, and this one today.

It seems to be intermittent.

 

I am running 7.13, Server 2012 R2, SQL Server 2014 Express Localdb (2012 isn't installed for me)

 

VSS: Backup job failed. Cannot notify writers about the 'BACKUP FINISH' event. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{237f0ddd-2a35-4f8e-bb9e-ab19931f6d1b}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f4].

 

Writer name: 'SqlServerWriter'

Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

Writer Instance Id: {237f0ddd-2a35-4f8e-bb9e-ab19931f6d1b

State: [12] Failed

Last error: Non-retryable error

I have not found a solution yet I'm afraid - I'll post on the Veeam forums as my guess is that it is related to SQL 2014 Express localdb as this was installed as part of the 7.16 upgrade for me.  Prior to that my delivery controllers were backed up without issue.

 

The databases appear to reside on SQL 2012 Express localdb in my case.  There were some cases of this issue with SQL 2012, however they were apparently resolved after applying the SP4 update.  There doesn't appear to be any service pack releases for SQL 2014 Express localdb from what I can see.

 

In the meantime I have disabled application aware processing for those VM's (Not ideal obviously, but it prevents the backup job throwing a warning)

 

Will keep you posted on my findings.   P.S - There's nothing written to the eventvwr at the time the error occurs either.

Link to comment
  • 0

OK - A little further information.  

 

These events are logged to the eventvwr at the time of the Veeam backup operation. 

 

Log Name:      Application
Source:        SQLWRITER
Date:          22/12/2017 01:41:27
Event ID:      8202
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     computer
Description:
SQL writer error: The backup completion state failed to be recorded in the database HaDatabaseName of instance computer\LOCALDB#A61D3558.  No new differential base has been established for the database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">8202</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-12-22T01:41:27.000000000Z" />
    <EventRecordID>496717</EventRecordID>
    <Channel>Application</Channel>
    <Computer>ANTIGONE.apollo.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>HaDatabaseName</Data>
    <Data>ANTIGONE\LOCALDB#A61D3558</Data>
    <Binary>5351575752545243313530340000000053515757525452433134303300000000</Binary>
  </EventData>
</Event>

 

Followed by

 

Log Name:      Application
Source:        SQLWRITER
Date:          22/12/2017 01:41:27
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: VERIFY DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3046
Error state: 2, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
SQLSTATE: 42000, Native Error: 3636
Error state: 2, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: An error occurred while processing 'BackupMetadata' metadata for database id 5 file id 1.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-12-22T01:41:27.000000000Z" />
    <EventRecordID>496715</EventRecordID>
    <Channel>Application</Channel>
    <Computer>computer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: VERIFY DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3046
Error state: 2, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
SQLSTATE: 42000, Native Error: 3636
Error state: 2, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: An error occurred while processing 'BackupMetadata' metadata for database id 5 file id 1.
</Data>
    <Binary>53514C434F4E4E43313238370000000053514C434F4E4E433132353200000000</Binary>
  </EventData>
</Event>

 

My initial thoughts were that this may be down to database corruption.  I have run DBCC CHECKDB against every database - all have checked out OK without errors.

 

My next thoughts are whether re-creating the Full-Text Catalog for the affected DB may resolve the issue.  I'll update this thread accordingly.  

 

I have also posted a thread on the Veeam forums - however the answer so far is 'fix your vss issues first'.

 

Regards

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...