Содержание
- Windows Server backup may fail because of the SQL Server VSS writer
- Symptoms
- Cause
- Resolution
- Резервное копирование Windows Server может завершиться сбоем из-SQL Server модуля записи VSS
- Симптомы
- Причина
- Решение
- Sqlstate 42000 native error 3271
- Asked by:
- Question
- Sqlstate 42000 native error 3271
- Answered by:
- Question
- Sqlstate 42000 native error 3271
- Answered by:
- Question
Windows Server backup may fail because of the SQL Server VSS writer
This article provides a solution to an issue where Microsoft Windows Server backup fails with an error: A Volume Shadow Copy Service Operation failed.
Applies to: В Windows Server 2012 R2, Windows Server 2016
Original KB number: В 2615182
Symptoms
A backup of the server may fail with the following error message:
A Volume Shadow Copy Service Operation failed. Detailed Error: The volume shadow copy operation failed with error 0x800423F4. View the event log for more information.
The following error message will be recorded in the application event log:
If you examine the application event log more, you will notice numerous errors from sources SQLWriter and SQLVDI.
The errors will be similar to the following:
Cause
When Windows Server backup attempts to back up a disk volume, a Volume Shadow Copy Snapshot is created for the volume. When the snapshot is created, any Volume Shadow Copy Service (VSS) writer associated with the volume is called. If any of the VSS writers encounter an error, the entire backup job will fail. In this example, the SQL VSS writer is encountering an error and causing the backup job to fail.
Resolution
The error is typically caused by a problem with one of the SQL Server instances. In order to troubleshoot the problem, you must first figure out which SQL Server instance has the problem. Usually, the problematic SQL Server instance will be named in the first recorded SQLVDI error.
In this example, the SQL Server instance named SBSMONITORING is failing the snapshot.
There may also be an error message from source SQLWRITER that occurs at about the same time as the first SQLVDI error. The SQLWRITER error message may identify the database name that is having a problem with the snapshot.
In this example, the database named SBSMonitoring is having a problem.
Once you have identified the SQL Server instance that is having a problem, the first step would be to test the backup with that SQL Server instance stopped. In our example of the SBSMonitoring instance, you would stop the SQL Server (SBSMonitoring) service on the server.
You would then run the backup job with the affected SQL Server instance stopped. If the backup completes, then you know the failure is caused by the SQL Server instance that is not running. You would then examine the SQL Server error log files and the event logs to see if we can determine what is wrong with that particular instance of SQL Server.
If you can’t determine the problematic SQL Server instance from the event logs, you can always stop all the SQL Server instances on the server and try to run backup with SQL stopped. If all the SQL Server instances are stopped, the SQL VSS writer will not be used.
On a default installation of Small Business Server 2008, you would stop the following services:
- SQL Server (SBSMonitoring)
- Windows Internal Database
On a default installation of Small Business Server 2011 Standard, you would stop the following services:
- SQL Server (SharePoint)
- SQL Server (SBSMonitoring)
- Windows Internal Database
Источник
Резервное копирование Windows Server может завершиться сбоем из-SQL Server модуля записи VSS
В этой статье описано решение проблемы, из-за которой резервное копирование Microsoft Windows Server завершается ошибкой: сбой операции службы теневого копирования томов.
Применимо к: Windows Server 2012 R2, Windows Server 2016
Исходный номер базы знаний: 2615182
Симптомы
Резервное копирование сервера может завершиться сбоем со следующим сообщением об ошибке:
Не удалось выполнить операцию службы теневого копирования томов. Подробная ошибка. Сбой операции теневого копирования тома с ошибкой 0x800423F4. Дополнительные сведения см. в журнале событий.
В журнале событий приложения будет записано следующее сообщение об ошибке:
Если подробнее изучить журнал событий приложения, вы заметите множество ошибок из источников SQLWriter и SQLVDI.
Ошибки будут выглядеть примерно так:
Причина
Когда служба архивации Windows Server пытается создать резервную копию тома диска, для этого тома создается моментальный снимок теневого копирования тома. При создании моментального снимка вызывается любой модуль записи службы теневого копирования томов (VSS), связанный с томом. Если какой-либо из модулей записи VSS столкнется с ошибкой, все задание резервного копирования завершится ошибкой. В этом примере модуль записи VSS SQL обнаруживает ошибку и вызывает сбой задания резервного копирования.
Решение
Ошибка обычно вызвана проблемой с одним из SQL Server экземпляров. Чтобы устранить проблему, необходимо сначала выяснить, какой SQL Server экземпляр имеет проблему. Как правило, проблемный SQL Server именуется в первой записанной ошибке SQLVDI.
В этом примере экземпляр SQL Server SBSMONITORING завершает сбой моментального снимка.
Также может появиться сообщение об ошибке из источника SQLWRITER, которое возникает примерно в то же время, что и первая ошибка SQLVDI. Сообщение об ошибке SQLWRITER может идентифицировать имя базы данных, в котором возникла проблема с моментальным снимком.
В этом примере возникла проблема с базой данных SBSMonitoring .
После того как вы определили SQL Server, в котором возникла проблема, первым шагом будет тестирование резервной копии с SQL Server экземпляра. В нашем примере экземпляра SBSMonitoring вы остановите службу SQL Server (SBSMonitoring) на сервере.
Затем вы запустите задание резервного копирования с остановленным SQL Server затронутым экземпляром. Если резервное копирование завершится, вы узнаете, что сбой вызван SQL Server экземпляра, который не выполняется. Затем вы изучите файлы SQL Server ошибок и журналы событий, чтобы определить, что не так с этим экземпляром SQL Server.
Если не удается определить проблемный экземпляр SQL Server из журналов событий, вы всегда можете остановить все экземпляры SQL Server на сервере и попытаться выполнить резервное копирование с остановкой SQL. Если все SQL Server остановлены, модуль записи VSS SQL не будет использоваться.
При установке по умолчанию small Business Server 2008 вы остановите следующие службы:
- SQL Server (SBSMonitoring)
- Внутренняя база данных Windows
При установке по умолчанию small Business Server 2011 Standard вы остановите следующие службы:
- SQL Server (SharePoint)
- SQL Server (SBSMonitoring)
- Внутренняя база данных Windows
Источник
Sqlstate 42000 native error 3271
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I’m getting these errors whenever I run windows backup on I get these errors for each of the six SQL databases. Below are two examples of the errors that I get. This is causing my backups to fail.
Log Name: Application
Source: SQLWRITER
Date: 7/1/2014 1:18:05 PM
Event ID: 24583
Task Category: None
Level: Error
Keywords: Classic
User: N/A
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «3:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘SharePoint_ConfigurationDatabase’, file ‘SharePoint_ConfigurationDatabase’ on file 1.
Log Name: Application
Source: SQLVDI
Date: 7/1/2014 1:18:05 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2488. Thread=10456. Server. Instance=SHAREPOINT. VD=Global7_SQLVDIMemoryName_0.
Anybody knows what is causing this and how do I resolve these errors.
Источник
Sqlstate 42000 native error 3271
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Several days ago the Veeam backup for my SQL Server 2008 R2 server started to fail with SQLVDI errors. I originally thought it was a Veeam issue, but last night I tried running Windows Server Backup and had the same issue. I get multiple of the below errors. I’ve rebooted the server to no avail.
EventId = 1
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1652. Thread=2192. Client. Instance=. VD=Global1_SQLVDIMemoryName_0.
And one of the below for each of the databases.
EventId = 3041
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Then one of these for each of the databases.
EventId = 24583
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 10.0 Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0 Error message: A nonrecoverable I/O error occurred on file «<6113dc44-3bf4-4b61-828f-00a46365b33a>23:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0 Error message: Processed 0 pages for database ‘master’, file ‘master’ on file 1.
Источник
Sqlstate 42000 native error 3271
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I found the following error in the event log:
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 1.
Below is the «Detail»:
Log Name: Application
Source: SQLWRITER
Date: 4/6/2015 6:03:44 PM
Event ID: 24583
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ***-APP2.Domain.***
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 1.
24583
2
0
0x80000000000000
123773
Application
***-APP2.Domain.***
ICommandText::Execute
0x80040e14
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 1.
53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000
This would seem to be something that needs addressing, but what I don’t understand is there is no error in the event log or the Windows BackUP system. Am I on the road to a disaster?
Источник
- Remove From My Forums
-
Question
-
I found the following error in the event log:
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 1.Below is the «Detail»:
Log Name: Application
Source: SQLWRITER
Date: 4/6/2015 6:03:44 PM
Event ID: 24583
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ***-APP2.Domain.***
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 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=»2015-04-07T01:03:44.000000000Z» />
<EventRecordID>123773</EventRecordID>
<Channel>Application</Channel>
<Computer>***-APP2.Domain.***</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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file «{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0
Error message: Processed 0 pages for database ‘Net2Archive’, file ‘Net2Archive_Data’ on file 1.
</Data>
<Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
</EventData>
</Event>This would seem to be something that needs addressing, but what I don’t understand is there is no error in the event log or the Windows BackUP system. Am I on the road to a disaster?
Answers
-
Error message: A nonrecoverable I/O error occurred on file «{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Hi Mike,
The above error is a general error that occurs when the operating system raises an error while performing I/O during a backup or restore operation. In most situations the cause is simply that the backup medium is full.
You can take below actions to troubleshoot this issue:
• Review SQL Server error messages to identify the cause of the failure.
• Ensure that the backup and restore medium has sufficient space.
• Correct any errors raised by third-party backup and restore software.
Lydia Zhang
TechNet Community Support
-
Edited by
Friday, April 10, 2015 8:48 AM
-
Proposed as answer by
Lydia ZhangMicrosoft contingent staff
Thursday, April 16, 2015 1:33 AM -
Marked as answer by
Lydia ZhangMicrosoft contingent staff
Friday, April 17, 2015 10:15 AM
-
Edited by
Group: Forum Members
Posts: 88,
Visits: 469
I have just noticed that the regular scheduled FULL image backups I’d created to run weekly for a Win10 desktop machine I’d placed in the guard house of the community I live in have been failing for quite a while. The machine runs (1) BuildingLink on one monitor for front gate access handling, as well as (2) Avigilon on a second monitor for output of the 54 security cameras).
VSS shadow backups have failed, so that the image backup proceeding without the shadow backup has errors with the primary BuildingLink and Avigilon data files not backedup because of «in use, busy».
The primary error is:
The output of the VSS log is as follows:
(Gathering writer metadata…)
(Waiting for the asynchronous operation to finish…)
Initialize writer metadata …
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
— Get exclude files
— Enumerate components
— Get file list descriptors
— Get database descriptors
— Get log descriptors
— Get exclude files
— Enumerate components
Discover directly excluded components …
— Excluding writer » since it has no selected components for restore.
— Excluding writer » since it has no selected components for restore.
— Excluding writer ‘BITS Writer’ since it has no selected components for restore.
— Excluding writer ‘Shadow Copy Optimization Writer’ since it has no selected components for restore.
— Excluding writer ‘MSSearch Service Writer’ since it has no selected components for restore.
Discover components that reside outside the shadow set …
Discover all excluded components …
Discover excluded writers …
Discover explicitly included components …
Verifying explicitly specified writers/components …
Select explicitly included components …
* Writer ‘Task Scheduler Writer’:
— Add component TasksStore
* Writer ‘VSS Metadata Store Writer’:
— Add component WriterMetadataStore
* Writer ‘Performance Counters Writer’:
— Add component PerformanceCounters
* Writer ‘SqlServerWriter’:
— Add component M910TCONCIERGELINKSQLmaster
— Add component M910TCONCIERGELINKSQLmodel
— Add component M910TCONCIERGELINKSQLmsdb
— Add component M910TCONCIERGELINKSQLCL_AUTHENTICATION_0551a4115297481e89c71499449dc299
— Add component M910TCONCIERGELINKSQLC:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF
— Add component M910TCONCIERGELINKSQLCL_Building_e351b65fae194c1585b6810a5fa99fb0.mdf
* Writer ‘WMI Writer’:
— Add component WMI
* Writer ‘Registry Writer’:
— Add component Registry
* Writer ‘COM+ REGDB Writer’:
— Add component COM+ REGDB
Creating shadow set {6916ab89-b3c1-4ad4-88d4-a6fa2103bef3} …
— Adding volume \?Volume{95dfaac8-ad52-4ddc-ab21-45ab1a3ac88e} [C:] to the shadow set…
— Adding volume \?Volume{0002215f-4040-a4a9-60f9-f713be420400} [E:] to the shadow set…
Preparing for backup …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
ERROR: Selected writer ‘SqlServerWriter’ is in failed state!
— Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
— Writer Failure code: 0x800423f4 (<Unknown error code>)
— Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
— Instance ID: {064513d9-e3cb-442e-b4ce-3527514e8b52}
Completing the backup (BackupComplete) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
ERROR: Selected writer ‘SqlServerWriter’ is in failed state!
— Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
— Writer Failure code: 0x800423f4 (<Unknown error code>)
— Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
— Instance ID: {064513d9-e3cb-442e-b4ce-3527514e8b52}
— Setting the VSS context to: 0x00000010
Creating shadow set {e4c6f22c-34e2-44da-b126-24cdf6785d49} …
— Adding volume \?Volume{95dfaac8-ad52-4ddc-ab21-45ab1a3ac88e} [C:] to the shadow set…
— Adding volume \?Volume{0002215f-4040-a4a9-60f9-f713be420400} [E:] to the shadow set…
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Shadow copy set successfully created.
Saving the backup components document …
List of created shadow copies:
Querying all shadow copies with the SnapshotSetID {e4c6f22c-34e2-44da-b126-24cdf6785d49} …
* SNAPSHOT ID = {a795ab71-f782-4f1f-9421-cc805e058eaa} …
— Shadow copy Set: {e4c6f22c-34e2-44da-b126-24cdf6785d49}
— Original count of shadow copies = 2
— Original Volume name: \?Volume{95dfaac8-ad52-4ddc-ab21-45ab1a3ac88e} [C:]
— Creation Time: 8/5/2021 5:55:58 PM
— Shadow copy device name: \?GLOBALROOTDeviceHarddiskVolumeShadowCopy10
— Originating machine: M910t
— Service machine: M910t
— Not Exposed
— Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
— Attributes: Auto_Release No_Writers Differential
* SNAPSHOT ID = {3231342d-9537-4e1a-bb6a-8aeb52a3b070} …
— Shadow copy Set: {e4c6f22c-34e2-44da-b126-24cdf6785d49}
— Original count of shadow copies = 2
— Original Volume name: \?Volume{0002215f-4040-a4a9-60f9-f713be420400} [E:]
— Creation Time: 8/5/2021 5:55:58 PM
— Shadow copy device name: \?GLOBALROOTDeviceHarddiskVolumeShadowCopy11
— Originating machine: M910t
— Service machine: M910t
— Not Exposed
— Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
— Attributes: Auto_Release No_Writers Differential
Windows Events
*****************************
Date: 8/5/2021 5:55:19 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3201
Error state: 7, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Cannot open backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}5’. Operating system error 0x80070002(The system cannot find the file specified.).
*****************************
Date: 8/5/2021 5:55:19 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE CL_Building_e351b65fae194c1585b6810a5fa99fb0.mdf. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:19 PM
Type: Error
Event: 3201
Source: MSSQL$CONCIERGELINKSQL
Cannot open backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}5’. Operating system error 0x80070002(The system cannot find the file specified.).
*****************************
Date: 8/5/2021 5:55:19 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(2)The system cannot find the file specified.
. Process=5968. Thread=10508. Server. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}5_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:19 PM
Type: Warning
Event: 8229
Source: VSS
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: Microsoft SQL Server 2014:SQLWriter
Writer Instance ID: {064513d9-e3cb-442e-b4ce-3527514e8b52}
Command Line: «C:Program FilesMicrosoft SQL Server90Sharedsqlwriter.exe»
Process ID: 6188
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Write on «{26A46BF5-20FF-410A-BF45-D649CBA1DD23}6» failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{26A46BF5-20FF-410A-BF45-D649CBA1DD23}2:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Write on «{26A46BF5-20FF-410A-BF45-D649CBA1DD23}3» failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{26A46BF5-20FF-410A-BF45-D649CBA1DD23}1:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=5968. Thread=12660. Server. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}6_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=5968. Thread=14928. Server. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}3_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=5968. Thread=8336. Server. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}2_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=5968. Thread=9816. Server. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}1_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupIoRequest::ReportIoError: write failure on backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}6’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupIoRequest::ReportIoError: write failure on backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}3’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE CL_AUTHENTICATION_0551a4115297481e89c71499449dc299. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{26A46BF5-20FF-410A-BF45-D649CBA1DD23}2’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}6_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}5_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}4_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}3_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}2_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6188. Thread=9796. Client. Instance=CONCIERGELINKSQL. VD=Global{26A46BF5-20FF-410A-BF45-D649CBA1DD23}1_SQLVDIMemoryName_0.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 945
Error state: 2, Severity: 14
Source: Microsoft SQL Server Native Client 11.0
Error message: Database ‘C:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
SQLSTATE: 42000, Native Error: 5120
Error state: 101, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Unable to open the physical file «C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf». Operating system error 32: «32(The process cannot access the file because it is being used by another process.)».
SQLSTATE: 42000, Native Error: 5120
Error state: 101, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Unable to open the physical file «C:ProgramDataBuildingLinkConciergeLinkCL_Authentication.mdf». Operating system error 32: «32(The process cannot access the file because it is being used by another process.)».
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE C:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF. Check the backup application log for detailed messages.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 5105
Source: MSSQL$CONCIERGELINKSQL
A file activation error occurred. The physical file name ‘C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf’ may be incorrect. Diagnose and correct additional errors, and retry the operation.
*****************************
Date: 8/5/2021 5:55:18 PM
Type: Error
Event: 17204
Source: MSSQL$CONCIERGELINKSQL
FCB::Open failed: Could not open file C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf for file number 2. OS error: 32(The process cannot access the file because it is being used by another process.).
*****************************
Date: 8/5/2021 5:55:16 PM
Type: Error
Event: 17204
Source: MSSQL$CONCIERGELINKSQL
FCB::Open failed: Could not open file C:ProgramDataBuildingLinkConciergeLinkCL_Authentication.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
The output of «VSSASMIN LIST WRITERS» is as follows:
Microsoft Windows [Version 10.0.19043.1110]
(c) Microsoft Corporation. All rights reserved.
C:WINDOWSsystem32>vssadmin list writers
vssadmin 1.1 — Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: ‘Task Scheduler Writer’
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: ‘VSS Metadata Store Writer’
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: ‘Performance Counters Writer’
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: ‘System Writer’
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {d018b7fa-ad07-4c70-9db1-c234ba2ebb25}
State: [1] Stable
Last error: No error
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {064513d9-e3cb-442e-b4ce-3527514e8b52}
State: [8] Failed
Last error: Non-retryable error
Writer name: ‘ASR Writer’
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {c9da2c83-fbcb-412a-bc8a-3fdfb549c2b3}
State: [1] Stable
Last error: No error
Writer name: ‘Registry Writer’
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f3fb8171-215e-4eb6-b0fd-af8bc5c1320a}
State: [1] Stable
Last error: No error
Writer name: ‘COM+ REGDB Writer’
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {408625eb-c487-4157-a35e-2081533383e2}
State: [1] Stable
Last error: No error
Writer name: ‘WMI Writer’
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {5236f822-eb61-4731-a324-7fc8cc1a7292}
State: [1] Stable
Last error: No error
Writer name: ‘Shadow Copy Optimization Writer’
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {611673b3-77bd-49c3-906c-9571defc6127}
State: [1] Stable
Last error: No error
Writer name: ‘MSSearch Service Writer’
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {da9a8834-c106-480c-ba19-24ab175bdfd4}
State: [1] Stable
Last error: No error
C:WINDOWSsystem32>
I’ve looked at the Windows Event Log and BuildingLInk itself is presenting errors, about some central files can’t be created because they already exist under the intended name. I will contact their support number tomorrow, as this might be the result of a previous machine crash and emergency reboot perhaps. Don’t know yet. But obviously this, too, needs to be resolved.
However I’m more concerned right now about VSS Shadow backups failing for Macrium Reflect. What is the solution here? In particular, what is the problem with writer ‘SQLServerWriter’? I’ve rebooted multiple times and that has not resolved the issue.
If you need me to present additional clues and forensic information, please ask.
Thanks for any help you can provide.
Edited
6 August 2021 4:15 AM by
DSperber
Group: Forum Members
Posts: 88,
Visits: 469
Well, «user error».
The problem is that SQLServerWriter is not installed, but is required because there is a 3rd-party app which is installed on this machine which actually uses SQL Server. Strangely, SQL Server clearly was installed, because the SQL database folders were created and are used by the application. But during the install of SQL Server the SQLServerWriter required for VSS is also supposed to be installed. And yet, somehow it was not. even though SQL Server was.
My theory is that I ran the install of the app while logged into Windows as a «user», rather than «administrator». I’m sure I must have replied with the admin password anytig UAC prompted me for it during the app install, but I have to conclude it perhaps really needed full admin authority to install SQLServerWriter and activate it. Or, there was some other explanation. But whatever the explanation, it does seem tied to a flawed install of the app. And VSSADMIN LIST WRITERS does not show SQLServerWriter as active.
I’ve now performed presumably the exact same app install on another PC, which only has an admin login for me. And I carefully watched as SQL Server Lite 2014 got installed, and also noticed that SQLServerWriter got installed. And sure enough, VSSADMIN LIST WRITERS now shows SQLServerWriter whereas it was not present before the app install. This install was obviously 100% correct and successful. The install I did on the other machine obviously was not.
So, doesn’t have anything to do with Macrium Reflect.
User error. My fault.
Case closed.
Group: Forum Members
Posts: 88,
Visits: 469
Well, hold your horses here… not so fast with this «user error» explanation…
I was actually mistaken in concluding that SQLServerWriter was «not installed» along with the 3rd-party app which required it. This was clearly incorrect, as the app itself works fine meaning SQLServer IS actually installed. The problem is actually that the VSS shadow copy initiated by MR failed, because SQLServerWriter failed… not that it wasn’t present.
To sort this all out and be sure I wasn’t missing something (since the original «production» machine environment, using licensed MR Home, was built back in February) I decided to repeat the entire process all over again, from absolute scratch, on one of my available laptop PCs, which had NONE OF THIS previously installed. No app (i.e. BuildingLink Concierge, which is the app that uses SQLServer) and nor previously installed SQLServer. Nothing previously present, so everything would be going in brand new from the vendor software download site.
(1) Run MR Backup before installing app/SQLServer, just to see what components get invoked for VSS shadow copy without SQL:
And the VSS log showed no need for SQLServerWriter:
Discover explicitly included components …
Verifying explicitly specified writers/components …
Select explicitly included components …
* Writer ‘Task Scheduler Writer’:
— Add component TasksStore
* Writer ‘VSS Metadata Store Writer’:
— Add component WriterMetadataStore
* Writer ‘Performance Counters Writer’:
— Add component PerformanceCounters
* Writer ‘Registry Writer’:
— Add component Registry
* Writer ‘WMI Writer’:
— Add component WMI
* Writer ‘COM+ REGDB Writer’:
— Add component COM+ REGDB
Creating shadow set {16f234dc-1796-44e4-a160-77e3aee68bff} …
— Adding volume \?Volume{49f853c8-c175-4ea3-85bc-253091ab7df0} [C:] to the shadow set…
Preparing for backup …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Shadow copy set successfully created.
Saving the backup components document …
(2) Install BuildingLInk Concierge on the laptop, which triggers a supporting download/install of SQLServer 2014 Lite. All goes perfectly.
And SQLServerWriter is added to available services supporting VSS shadow copy:
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {970f909e-51f2-4a00-8de1-7d2a680a1956}
State: [1] Stable
Last error: No error
(3) Run MR Backup again, which produces «catastrophic failure» error due to VSS shadow copy failure due to SQLServerWriter failure:
And now when I look at VSSADMIN LIST WRITERS it shows SQLServerWriter in a «failed» state
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {970f909e-51f2-4a00-8de1-7d2a680a1956}
State: [8] Failed
Last error: Non-retryable error
And the VSS log from MR Backup shows the failure of SQLServerWriter:
Discover explicitly included components …
Verifying explicitly specified writers/components …
Select explicitly included components …
* Writer ‘Task Scheduler Writer’:
— Add component TasksStore
* Writer ‘VSS Metadata Store Writer’:
— Add component WriterMetadataStore
* Writer ‘Performance Counters Writer’:
— Add component PerformanceCounters
* Writer ‘SqlServerWriter’:
— Add component T495T2CONCIERGELINKSQLmaster
— Add component T495T2CONCIERGELINKSQLmodel
— Add component T495T2CONCIERGELINKSQLmsdb
— Add component T495T2CONCIERGELINKSQLCL_AUTHENTICATION_89ee301266b04d3d813d77a03d7b20a4
— Add component T495T2CONCIERGELINKSQLC:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF
— Add component T495T2CONCIERGELINKSQLCL_Building_e351b65fae194c1585b6810a5fa99fb0.mdf
* Writer ‘WMI Writer’:
— Add component WMI
* Writer ‘Registry Writer’:
— Add component Registry
* Writer ‘COM+ REGDB Writer’:
— Add component COM+ REGDB
Creating shadow set {a5413bd7-8834-4885-b82d-9c534bcc9279} …
— Adding volume \?Volume{49f853c8-c175-4ea3-85bc-253091ab7df0} [C:] to the shadow set…
Preparing for backup …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
ERROR: Selected writer ‘SqlServerWriter’ is in failed state!
— Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
— Writer Failure code: 0x800423f4 (<Unknown error code>)
— Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
— Instance ID: {970f909e-51f2-4a00-8de1-7d2a680a1956}
Completing the backup (BackupComplete) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
ERROR: Selected writer ‘SqlServerWriter’ is in failed state!
— Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
— Writer Failure code: 0x800423f4 (<Unknown error code>)
— Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
— Instance ID: {970f909e-51f2-4a00-8de1-7d2a680a1956}
— Setting the VSS context to: 0x00000010
Creating shadow set {ebd80e5c-10f1-4ee3-829e-4e827771b22a} …
— Adding volume \?Volume{49f853c8-c175-4ea3-85bc-253091ab7df0} [C:] to the shadow set…
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Shadow copy set successfully created.
Saving the backup components document …
Apparently something is either wrong with MR Backup as far as invoking VSS shadow copy for SQLServer database, or something is wrong with what the BuildingLink Concierge app is doing. And the VSS shadow copy failure is identical both with MR Home as well as MR Free.
I have not upgraded from my Version 7 to new Version 8, as I didn’t think I needed to. Didn’t see any value to me of the new features. I suppose I could try it just to see if they’ve done anything which might directly address this current failure. But for now, the always reliable Version 7 MR Home/Free appears not to be able to work when SQLServer is in the environment.
Is there something uniqueabout SQLServer and MR that I should know??
Group: Forum Members
Posts: 766,
Visits: 7.2K
A bit of an overview about the role of the SqlServerWriter; when MR creates a backup, it first creates a snapshot of the current state of the file system. It doesn’t know about the state of SQL Server database files, so it calls the SqlServerWriter, whose job it is to communicate with the SQL Server database server; in your case it told the server to prepare for a snapshot, i.e. get to a logical stopping point and stop I/O, prior to creating a snapshot of your files. This step failed.
It looks to me like your backup of other files proceeded without the results from SqlServerWriter. So you have a consistent backup of your file system EXCEPT your database files might not have been in a consistent state when they were backed up. This continuation without the failed writer, I think, is the default for MR, but it can be overridden. But the other choice is to abort the entire backup.
Researching the MR KB reveals a post that emphatically states that this is NOT a Reflect problem, but instead a problem with the database provider that failed to act on a quiescence request from SqlServerWriter. Unfortunately, I didn’t find a post about any fix for your application that uses SQL Server.
Two avenues for you to follow: 1) contact your database application provider to see if they have seen the problem before; 2) seek help by creating a ticket for Macrium Reflect support to confirm my analysis.
L W «Dan» Danz, Overland Park KS
MR v8.1.7367 Win11.22H2-22621.1194+ === MR v8.1.7367+ Win10.22H2-19045.2564+
Edited
7 August 2021 2:56 PM by
L. W. «Dan» Danz
Group: Forum Members
Posts: 88,
Visits: 469
Thank you for your insights.
Yes, it definitely was clear that the remainder of the image backup was still going to be fine. However if I did truly want to backup and/or restore the complete C-partition as expected when using MR for «system image», having to deal with a non-imaged SQL database for this application would at least be of concern.
I was on the phone yesterday for 2 hours with a very savvy tech guy at BuildingLink. However he was not familiar with Macrium Reflect. I also didn’t think he was familiar with the concept of «shadow copies» normally performed by typical software backup products, in order to then run the backup off of the shadow copy instead of the live active possibly open files.
I am going to re-contact their tech support again on Monday, to see if I can talk with someone who would be more knowledgeable specifically about their Concierge app which interfaces to SQLServer. They also have another app that also involves SQL, so presumably they have an appropriate programming group and tech support related to that component. They surely are famliar with «shadow copy» and «quiesce» etc., and the purpose of SQLServerWriter with VSS.
Hopefully I will make at least some progress here.
And, on a parallel front, I have in fact early this morning also opened a formal ticket with Macrium support. While they may not in theory be the «cause» here (although who knows, really, unless they look into it first), surely they must have some good insights. Perhaps they could suggest some further steps or provide some special diagnostic tools or techniques to produce further in-depth diagnostic or forensic debug-level output that might help get to the true root cause. I’m sure I will hear back from them by early next week.
As far as what else appeared in the VSS log that is of interest (although it may be irrelevant perhaps, probably because it would be expected if the «quiesce» were not performed successfully):
Windows Events
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{4C3FD2E0-37D0-4D21-BA49-901553FB1580}6:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Warning
Event: 8229
Source: VSS
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: Microsoft SQL Server 2014:SQLWriter
Writer Instance ID: {970f909e-51f2-4a00-8de1-7d2a680a1956}
Command Line: «C:Program FilesMicrosoft SQL Server90Sharedsqlwriter.exe»
Process ID: 7364
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{4C3FD2E0-37D0-4D21-BA49-901553FB1580}5:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=7344. Thread=13476. Server. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}6_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4C3FD2E0-37D0-4D21-BA49-901553FB1580}6’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{4C3FD2E0-37D0-4D21-BA49-901553FB1580}3:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=7344. Thread=7724. Server. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}5_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4C3FD2E0-37D0-4D21-BA49-901553FB1580}5’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{4C3FD2E0-37D0-4D21-BA49-901553FB1580}2:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}6_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE CL_Building_e351b65fae194c1585b6810a5fa99fb0.mdf. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}5_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=7344. Thread=11988. Server. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}3_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file «{4C3FD2E0-37D0-4D21-BA49-901553FB1580}1:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE CL_AUTHENTICATION_89ee301266b04d3d813d77a03d7b20a4. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}4_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=7344. Thread=12576. Server. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}2_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4C3FD2E0-37D0-4D21-BA49-901553FB1580}3’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}3_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4C3FD2E0-37D0-4D21-BA49-901553FB1580}2’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=7344. Thread=12256. Server. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}1_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 18210
Source: MSSQL$CONCIERGELINKSQL
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4C3FD2E0-37D0-4D21-BA49-901553FB1580}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}2_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:06 AM
Type: Error
Event: 1
Source: SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=7364. Thread=10208. Client. Instance=CONCIERGELINKSQL. VD=Global{4C3FD2E0-37D0-4D21-BA49-901553FB1580}1_SQLVDIMemoryName_0.
*****************************
Date: 8/7/2021 5:07:05 AM
Type: Error
Event: 24583
Source: SQLWRITER
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: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 945
Error state: 2, Severity: 14
Source: Microsoft SQL Server Native Client 11.0
Error message: Database ‘C:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
SQLSTATE: 42000, Native Error: 5120
Error state: 101, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Unable to open the physical file «C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf». Operating system error 32: «32(The process cannot access the file because it is being used by another process.)».
SQLSTATE: 42000, Native Error: 5120
Error state: 101, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Unable to open the physical file «C:ProgramDataBuildingLinkConciergeLinkCL_Authentication.mdf». Operating system error 32: «32(The process cannot access the file because it is being used by another process.)».
*****************************
Date: 8/7/2021 5:07:05 AM
Type: Error
Event: 3041
Source: MSSQL$CONCIERGELINKSQL
BACKUP failed to complete the command BACKUP DATABASE C:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF. Check the backup application log for detailed messages.
*****************************
Date: 8/7/2021 5:07:05 AM
Type: Error
Event: 5105
Source: MSSQL$CONCIERGELINKSQL
A file activation error occurred. The physical file name ‘C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf’ may be incorrect. Diagnose and correct additional errors, and retry the operation.
*****************************
Date: 8/7/2021 5:07:05 AM
Type: Error
Event: 17204
Source: MSSQL$CONCIERGELINKSQL
FCB::Open failed: Could not open file C:ProgramDataBuildingLinkConciergeLinkCL_Authentication_log.ldf for file number 2. OS error: 32(The process cannot access the file because it is being used by another process.).
*****************************
Date: 8/7/2021 5:07:04 AM
Type: Error
Event: 17204
Source: MSSQL$CONCIERGELINKSQL
FCB::Open failed: Could not open file C:ProgramDataBuildingLinkConciergeLinkCL_Authentication.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
Group: Forum Members
Posts: 88,
Visits: 469
Well, now I’m baffled.
I remembered that I had deleted all old logs and MRIMG backup image file from the original «production» machine last night, before trying a complete uninstall/reinstall of the Concierge software product (which should also install SQL Server if still necessary, as it does the very first time) but this time ensuring that I was actually logged in as ADMIN rather than USER account. And after this when I retried the backup and it still failed with this SQLServerWriter error I simply canceled the backup job. So I hadn’t actually taken even one mostly-good image in the current condition, and I hadn’t retained any very old backup image at all.
So right now, I just connected to the machine and ran the backup again. I fully expected the same old SQLServerWriter error but was prepared for that. I just wanted a current image backup of the rest of C, as it looks right now.
Well imagine my surprise when somehow, for some reason, IT WORKED FINE!!!!!!!
NO SQLSERVER WRITER ERROR!!!
And VSSADMIN LIST WRITERS shows SQLServerWriter stable and normal!!!
I have absolutely no idea how things could have somehow «fixed themselves», since overnight when it had failed. I’d done absolutely nothing since last night’s uninstall/reinstall and re-test which failed the same way. And yet, just now, IT WORKED WITHOUT AN ERROR!! Somehow SQLServerWriter «came to life» in successfully accomplishing the required «quiesce» when MR Backup starts and VSS shadow copy is needed!
No idea how to explain this. Of course I also have no complaint, because this is exactly what is supposed to have happened all along. So whatever the story, I think I’m happy. I hope this will continue next week when the regularly scheduled weekly image backup is again taken.
And VSSADMIN LIST WRITERS as appears right now, AFTER the backup job.completes:
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {3bd0ca7a-5bbd-4349-8b55-f43e92df67a6}
State: [1] Stable
Last error: No error
And here is the VSS log from the backup job just run. Note that SQLServerWriter responds correctly and obviously accomplishes the required «quiesce»:
Discover explicitly included components …
Verifying explicitly specified writers/components …
Select explicitly included components …
* Writer ‘Task Scheduler Writer’:
— Add component TasksStore
* Writer ‘VSS Metadata Store Writer’:
— Add component WriterMetadataStore
* Writer ‘Performance Counters Writer’:
— Add component PerformanceCounters
* Writer ‘SqlServerWriter’:
— Add component M910TCONCIERGELINKSQLmaster
— Add component M910TCONCIERGELINKSQLmodel
— Add component M910TCONCIERGELINKSQLmsdb
— Add component M910TCONCIERGELINKSQLC:PROGRAMDATABUILDINGLINKCONCIERGELINKCL_AUTHENTICATION.MDF
* Writer ‘Registry Writer’:
— Add component Registry
* Writer ‘WMI Writer’:
— Add component WMI
* Writer ‘COM+ REGDB Writer’:
— Add component COM+ REGDB
Creating shadow set {78eb56c7-ce5e-4444-91cf-a85beb267e7c} …
— Adding volume \?Volume{95dfaac8-ad52-4ddc-ab21-45ab1a3ac88e} [C:] to the shadow set…
— Adding volume \?Volume{0002215f-4040-a4a9-60f9-f713be420400} [E:] to the shadow set…
Preparing for backup …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Creating the shadow (DoSnapshotSet) …
(Waiting for the asynchronous operation to finish…)
(Waiting for the asynchronous operation to finish…)
Shadow copy set successfully created.
Saving the backup components document …
Group: Forum Members
Posts: 88,
Visits: 469
Note that this seems to contradict the theoretically identical situation on my «laboratory laptop» that I was using to experiment with, and that just earlier this morning still failed with SQLServerWriter presenting its error.
Can’t explain this difference of behavior.
I will see what happens on the laptop «as time moves forward», perhaps seeing that it «fixes itself» without my further intervention, as it has seemingly done on the original «production» machine.
Still puzzled.
Group: Forum Members
Posts: 766,
Visits: 7.2K
When it failed, did you by any chance have two instances of the app running. I noticed an error message in the failure that the DB couldn’t complete I/O because the «file is in use by another process».
L W «Dan» Danz, Overland Park KS
MR v8.1.7367 Win11.22H2-22621.1194+ === MR v8.1.7367+ Win10.22H2-19045.2564+
Group: Forum Members
Posts: 88,
Visits: 469
Well, I decided to retry the backup on the «lab laptop» again. And wouldn’t you know it, IT TOO WORKED FINE THIS TIME!!! Hmmm…
Under the «numerology theory» that something was not properly started by default in SQL Server immediately after boot such that the very first post-boot SQLServerWriter’s «quiesce» request is unsuccessful but each request two and beyond IS successful, I tested this out on the laptop. If true, it would also explain how last night’s surprising success on the «production machine» actually happened, since it was the second time post-boot that I’d attempted a backup on that machine, after the first post-boot had failed.
And sure enough, it seems true. First post-boot Macrium Reflect backup job use of SQLServerWriter fails. Second and subsequent Macrium Reflect jobs work fine.
I checked Services, to see if maybe there is something that is required for success but not active and running by default immediately post-boot, and that’s not happening. All SQL-related services that are active or not immediately after right boot and before that first MR job remain unchanged in their status after the first MR job and beyond. So nothing here is getting kick-started by the first failing job in order to then be active only for the second and subsequent jobs. So this isn’t the explanation as to why the first VSS shadow copy fails for SQLServerWriter but later jobs are successful.
I also tried actually launching the Concierge program right after boot, just to see if somehow it «wakes up» SQL Server and gets it «active» in some way, before the first SQLServerWriter usage is attempted with the first MR job. But this too made no difference. That first MR job still exhibits the VSS shadow copy failure for SQL, and second and later jobs work fine.
So, under the theory that Macrium Reflect itself invokes VSS the exact same way no matter first or subsequent jobs, all the clues and experiments seem to suggest an actual bug in first-time use of SQLServerWriter that is responsible for the first-time failure, which somehow «corrects itself» as a result of the first-time failure and gets things into the proper state so that second and later use actually now does work.
I know, this is «numerology» which normally isn’t an explanation or a solution. But the empirical evidence does describe what is clearly a first-time-use failure, with a second-and-later-use success. It appears completely unrelated to the Concierge application itself, since it doesn’t matter if the program is ever actually launched or not that SQLServerWriter works or not. It is simply a first-time failure, which points to an SQLServer-related bug. It looks like Macrium Reflect is also not the culprit.
Fascinating. I point out that it is SQL Server 2014 Lite which got installed along with the BuildingLink Concierge app. I will contact BuildingLink tech support on Monday to inquire if perhaps a more recent «runtime» release version might not be available for installation, and which perhaps might fix the problem (since SQLServerWriter for VSS get installed along with the main SQL Server product). Perhaps in the past 7 years this first-time VSS anomaly has been reported and corrected.
Group: Forum Members
Posts: 766,
Visits: 7.2K
Did the failure on the first time have the error indicating «the file is in use by another process»? I’m mulling over the possibility that there is some indexing or other processioning going on right after boot that takes a little time. Watch it with Task Manager or Resource Monitor (link is at the bottom of Task Manager’s Performance tab).
In the failure logs, there is a reference to BACKUP DATABASE operation — that’s NOT a Reflect Operation — but something that was interrupted by a Reflect quiescence request and failed. Internally, SQL Server can create backups of the MDF files to another directory. I wonder if, on startup, your application is initiating that type of BACKUP. Again, Resource Monitor should give you some clues, and so should SQL Server logs.
L W «Dan» Danz, Overland Park KS
MR v8.1.7367 Win11.22H2-22621.1194+ === MR v8.1.7367+ Win10.22H2-19045.2564+
So I started getting strange backup reports on a server last week saying that it had failed with some VSS error. So I went investigating and found the following errors in the event viewer:
Event 518, Microsoft-Windows-Backup
Backup started at ’11/12/2013 12:00:22 PM’ failed as another backup or recovery is in progress. Please re-run backup.
Event 1, SQLVDI
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3352. Thread=7288. Client. Instance=MICROSOFT##SSEE. VD=Global{8E68F739-4463-4710-A965-02CB141F7345}1_SQLVDIMemoryName_0.
Event 3041, MSSQL$MICROSOFT##SSEE
The description for Event ID 3041 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
BACKUP DATABASE model
The specified resource type cannot be found in the image file
Event 24583, SQLWRITER
The description for Event ID 24583 from source SQLWRITER cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ICommandText::Execute
0x80040e14
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file “{8E68F739-4463-4710-A965-02CB141F7345}2:” 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database ‘msdb’, file ‘MSDBData’ on file 1.
the message resource is present but the message is not found in the string/message table
Event 3041, MSSQL$SBSMONITORING
BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
Event 18210, MSSQL$SBSMONITORING
BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device ‘{7D8BEEF1-F3C5-48B9-804E-58B5DC189C4A}1’. Operating system error 995(error not found).
Event 3041, MSSQL$SBSMONITORING
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Event 2007, ESE
Information Store (900) Shadow copy instance 10 aborted.
Event 24583, SQLWRITER
The description for Event ID 24583 from source SQLWRITER cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ICommandText::Execute
0x80040e14
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file “{7D8BEEF1-F3C5-48B9-804E-58B5DC189C4A}3:” 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database ‘SBSMonitoring’, file ‘SBSMonitoring’ on file 1.
Event 3355, Windows SharePoint Services 3
Cannot connect to SQL Server. np:\.pipeMSSQL$Microsoft##SSEEsqlquery not found. Additional error information from SQL Server is included below.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
So I followed my nose and found this Microsoft technet article on Windows Server Backup May Fail Because of the SQL VSS Writer which basically says that this error may be caused by an error in a different database and gives an example of the SBSMonitoring database has errors in it.
In my event logs there were some errors with the SBSMonitoring database(event id 3041 and 18210).
So then I found an technet article on how to recreate the SBSMontitoring database so I followed the steps on there and ran the Powershell script that is attached to the article.
That nights backups still had the same problems and still through out a heap of errors in the event logs.
I thought it could be the SharePoint database which I was a bit worried about because I have spent hours fixing a SharePoint installation about a year ago. Refer to this post on SharePoint cannot connect to configuration database error for more information on that saga.
I then thought what would happen if I recreated the backup job. So I deleted the backup job that was running and made a new one.
That nights backup on the Small Business Server worked!!
I am not sure if the recreation of the SBSMonitoring database had anything to do with the problem but those were the steps I used to fix the backup problem. Hopefully this doesn’t reoccur but if it does I will update this post with more information.
If you have had the same problem please comment with how you fixed it and if you needed to recreate the SBSMonitoring database.
You may also like:
SBS2011 – Administrator “Administrator Name” Does not have Exchange administrator rights.
SharePoint cannot connect to configuration database error after installing KB2687442 update on SBS Server 2008
Hi Everyone, I’m Jake. I have created this site basically as my own knowledge base, hopefully you find some of the information on here useful.
I work with businesses across South West Victoria to leverage technology to improve the way they work & keep their data safe.
If you want to connect with me look me up on LinkedIn.
I haven’t been able to back up my vCenter machine for the past 6 days and I would really appreciate your help in resolving my issue.
Our setup:
-5x VMWare 4.1 hosts
-Veeam Backup & Replication 5.0.0.179 (64-bit) running on a Windows Server 2008 SP2 x64 virtual machine
-vCenter running on a Windows Server 2008 SP2 x64 virtual machine
-vCenter server is hosting the vCenter database on a local SQL 2005 Express instance (can’t tell which version, but definitely pre-SP4)
My simple and short story:
Last Friday we changed the passwords for our domain user account and for the account that Veeam uses to connect to vCenter. All Veeam jobs started failing immediately but I was able to resolve this by recreating the backup jobs. All jobs are successfully backing up except for one: the vCenter Server job. This job backs up the vCenter Server only.
Code: Select all
Backup: vCenter Server (Full)
Created by (domain)(user) at 6/04/2011 6:13:24 PM.
Session Details
Status Error Start time 7/04/2011 1:14:52 PM Details
Total VMs 1 End time 7/04/2011 1:17:42 PM
Processed VMs 1 Duration 0:02:50
Successful VMs 0 Total size 80.00 GB
Failed VMs 1 Processed size 0.00 KB
VMs in progress 0 Processing rate 0 KB/s
Processed Objects
VM name Status Start time End time Total size Processed size Processing rate Duration Details
ic-pra-wsv-08 - vCenter Error 7/04/2011 1:15:45 PM 7/04/2011 1:17:41 PM 80.00 GB 0.00 KB 0 KB/s 0:01:56
Freezing guest operating system
VSSControl: Failed to freeze guest, wait timeoutAs a result of the Veeam job failure, the following issues occur on the vCenter server:
1. SQLWriter, MSSQL$SQLEXP_VIM and SQLVDI errors are logged:
Code: Select all
Level,Date and Time,Source,Event ID,Task Category
Error,7/04/2011 4:41:30 PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file ""{1B33943E-8636-4D54-A20B-D3A9F8606A4D}2:"" 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database 'msdb', file 'MSDBData' on file 1.
"
Error,7/04/2011 4:41:30 PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file ""{1B33943E-8636-4D54-A20B-D3A9F8606A4D}3:"" 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database 'VIM_UMDB', file 'VIM_UMDB_dat' on file 1.
"
Error,7/04/2011 4:41:30 PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file ""{1B33943E-8636-4D54-A20B-D3A9F8606A4D}1:"" 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database 'model', file 'modeldev' on file 1.
"
Error,7/04/2011 4:41:30 PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file ""{1B33943E-8636-4D54-A20B-D3A9F8606A4D}4:"" 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database 'VIM_VCDB', file 'VIM_VCDB_dat' on file 1.
"
Error,7/04/2011 4:41:30 PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file ""{1B33943E-8636-4D54-A20B-D3A9F8606A4D}5:"" 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database 'master', file 'master' on file 1.
"
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,18210,(2),BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{1B33943E-8636-4D54-A20B-D3A9F8606A4D}2'. Operating system error 995(error not found).
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,18210,(2),BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{1B33943E-8636-4D54-A20B-D3A9F8606A4D}3'. Operating system error 995(error not found).
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1248. Thread=292. Server. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}2_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,3041,(6),BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,3041,(6),BACKUP failed to complete the command BACKUP DATABASE VIM_VCDB. Check the backup application log for detailed messages.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,3041,(6),BACKUP failed to complete the command BACKUP DATABASE VIM_UMDB. Check the backup application log for detailed messages.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,3041,(6),BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,3041,(6),BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1248. Thread=2700. Server. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}3_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,18210,(2),BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{1B33943E-8636-4D54-A20B-D3A9F8606A4D}4'. Operating system error 995(error not found).
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1248. Thread=2720. Server. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}4_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,18210,(2),BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{1B33943E-8636-4D54-A20B-D3A9F8606A4D}1'. Operating system error 995(error not found).
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1248. Thread=2780. Server. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}1_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,MSSQL$SQLEXP_VIM,18210,(2),BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{1B33943E-8636-4D54-A20B-D3A9F8606A4D}5'. Operating system error 995(error not found).
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1248. Thread=2640. Server. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}5_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2412. Thread=3168. Client. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}5_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2412. Thread=3168. Client. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}4_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2412. Thread=3168. Client. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}3_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2412. Thread=3168. Client. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}2_SQLVDIMemoryName_0.
Error,7/04/2011 4:41:30 PM,SQLVDI,1,None,SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2412. Thread=3168. Client. Instance=SQLEXP_VIM. VD=Global{1B33943E-8636-4D54-A20B-D3A9F8606A4D}1_SQLVDIMemoryName_0.
2. VSS breaks forcing a restart to bring VSS back to an operational state:
Code: Select all
C:Usersuser>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {5f746417-0701-4387-9e06-9b64da9a1403}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {86b82811-aba1-4eaa-963f-95677202f21c}
State: [9] Failed
Last error: Timed out
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {32443eb2-3527-4790-ad66-d2089679fa55}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {063c4be6-7b23-41b3-9bb2-9e3537a0c13a}
State: [9] Failed
Last error: Timed out
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {2b786c56-d1f3-4017-b1a6-2fc330b9b333}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {6ef9d58e-b7d7-48de-84d8-6ef2cde5e018}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {43723a54-d04f-41e9-b02a-a1b187d89a67}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {6d484c62-f228-4e8a-949e-4ef1fbb50ae9}
State: [1] Stable
Last error: No error
Writer name: 'ADAM (VMwareVCMSDS) Writer'
Writer Id: {dd846aaa-a1b6-42a8-aaf8-03dcb6114bfd}
Writer Instance Id: {b06949ce-c507-48ef-83a1-a463c4e5073e}
State: [9] Failed
Last error: Timed outSo for some reason, every time I run the vCenter Server backup job, VSS fails to freeze the vCenter SQL database and breaks, forcing a restart of the vCenter server which only fixes VSS until the backup job is run again.
I have tried restarting both the Veeam and vCenter server to try and resolve the issue but I’m really at a loss and not sure how to continue troubleshooting.
Thanks in advance.
I have the job to run on weekdays at night.
Yet every [backup] day around 4PM, I get errors logged in EventViewer. There are many of each of these.
Source: SQLVDI, EventID: 1
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1108. Thread=1288. Client. Instance=BKUPEXEC. VD=Global{87743554-1D7A-4F60-B6B2-1F288592A7D2}4_SQLVDIMemoryName_0.
Source: MSSQL$BKUPEXEC, EventID: 18210
BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device ‘{87743554-1D7A-4F60-B6B2-1F288592A7D2}2’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Source: SQLWRITER, EventID: 24583
The description for Event ID ( 24583 ) in Source ( SQLWRITER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ICommandText::Execute, 0x80040e14, SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file «{87743554-1D7A-4F60-B6B2-1F288592A7D2}1:» 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database ‘model’, file ‘modeldev’ on file 1.
Source: MSSQL$MICROSOFT##SSEE, EventID: 3041
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Source: MSSQL$SOAPBOX, EventID: 18210
BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device ‘{60AF6F96-3358-47B2-A25F-D57C38777E4A}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).