A vss writer has rejected an event with error 0x800423f4

This error has been on going and I finally gave some time to it…

Issue occurs when trying to create a Restore Point.

There are 3 errors with the same time stamp in my windows logs.

Applications — The first one on the list in event viewer is «Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy.  Check the Application and System event logs
for any related errors».

Applications — The second one is «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».

System — The last one «An I/O operation initiated by the Registry failed «unrecoverably».The Registry could not flush hive (file): ‘DeviceHarddiskVolume1BootBCD'»  — The research on this one led to resolution.

In my case the resolution was to move the BootBCD on the 100 mb Reserve Drive to C: drive. I found it easier to use easy bcd. Once windows rebooted it came up fine with C: Active. I was able to successfully create a restore point and implement with 100%.

This solution may be a problem if Bitlocker is being used. I finished off with formatting 100 mb hidden reserve partition in ext4.

Host Machine:

• Intel Core i3 3120M @ 2,50Ghz 2,50Ghz
• 12GB RAM
• Windows 10 Enterprise 64Bit
• 750GB HD
• 250GB SSD

Virtual Machine:

• Windows Server 2008 R2 Enterprise
• 4 virtual processors
• 8GB RAM

I’m having some problems to create checkpoints on my VM. When i try to do it, Hyper-V goes until 19% of the creating progress, and then this error screen appears:

I’ve analyzed Event Viewer’s logs, and on the Hyper-V Worker > Admin section, it shows the following messages:

‘PNSP2013’ could not initiate a checkpoint operation: %%2147754996 (0x800423F4). (Virtual machine ID 69EAA8C6-E8E9-4585-97AE-5633F400BB89)[

And I also collected VSSDiag’s log, which contains no relevant information (at least for me)

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.
Log:

Operation:    PostSnapshot  Event
Context:
Execution Context: Writer
Writer Class Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Name: NTDS 
Writer Instance ID: {2b09511a-25fd-47cd-929f-4f1f60cc1594}
Command Line: C:Windowssystem32lsass.exe
Process ID: 636NTDS

Some important points to consider:

1. I have enough space on the SSD drive to store the checkpoint file.
2. I’ve tried to stop all non-Microsoft services on the VM and restart it, but no success
3. If i turn off the VM, the checkpoint can be created with no errors.
4. According to this article, i’ve also checked the KB982018, and it’s already installed on the VM.

I can’t figure out what the hell is going on… Some help?

PC running slow?

Improve the speed of your computer today by downloading this software — it will fix your PC problems.

Recently, some of our readers reported that they encountered error 0x800423f4. 0x800423F4 means VSS error “VSS_E_WRITERERROR_NONRETRYABLE” or “Writer encountered a permanent error. If you try to back up again, the error is likely and will repeat. ” This error expresses a typical error that occurs in a backup. the process can also be repeated.

• 3 minutes to read.

This article is a replacement for an issue where Microsoft Server Windows Backup fails with an error: The shadow copy operation failed Volume. For:

applies to Windows Server 2012 R2, Windows Server 2016
Original Knowledge Base Number: 2615182

Symptoms

Server type backups may fail with the above error message:

The volume shadow copy service operation failed. Detailed error: Failed to organize volume shadow copy with error 0x800423F4. More information can be found in the experience log.

The following point of failure is logged in the application problem log:

  Protocol application name:Source: Microsoft Windows Backup.Event ID: 521Level: errorDescription:A backup that started at "*   *" was aborted because the volume shadow copy process failed for the backup volumes with the following error message "2155348129". Please restart the backup as soon as the problems are resolved. 

If you look closely at the application event log, you will see many errors from the SQLWriter and SQLVDI pipes.

  protocol name: applicationSource: SQLWRITEREvent ID: 24583Level: errorDescription:Sqllib error: OLEDB error when calling ICommandText :: Run. h = 0x80040e14. SQLSTATE: 42000, Native Error: 3013Error status: single message, severity: 16Source: Microsoft Server SQL Native Client 10.0Error message: BACKUP DATABASE crashes.SQLSTATE: 42000, Error: Native 3271Error status: one, severity: 16Source: Microsoft SQL Server Native Client 10.0Error message: A fatal I / O error occurred with the file inch DF1DD65F-F8AD-4946-A764-F62166C541E222: “995 (An I / O operation has already been canceled due to a thread terminated or an application request.). 

  protocol name: applicationSource: SQLVDIEvent ID:Level: errorKeywords: classicUser: N / AComputer: CONTOSERVER.contoso.localDescription:SQLVDI: Loc = TriggerAbort. Desc = called. Error code = (0). Process = 3720. Thread = 9404. Server. Instance = SBSMonitoring. VD = GlobalDF1DD65F-F8AD-4946-A764-F62166C541E210_SQLVDIMemoryName_0. 

Reason

When Windows Server attempts to back up a set of volumes due to a disaster, a shadow copy of the volume is created for that volume. Usually, when a snapshot is taken, any writer connectedpassed to the Volume Shadow Copy Service (VSS) will be with the volume. If any of the vss writers encounter an error, the entire backup job may well fail. In this example, the vss of the SQL writer fails and the backup job fails.

Resolution

The error can usually be caused by a problem with a specific instance of SQL Server. To resolve this issue, you must first find out which SQL Server scenario is causing the problem. Typically, the problematic SQL Server instance is mentioned in this first logged SQLVDI error.

  protocol name: applicationSource: SQLVDIEvent ID: oneLevel: errorDescription:SQLVDI: Loc = SignalAbort. Desc = Client initiates completion. Error code = (0). Process = 4772. Subject = 10300. Customer. Instance = SBSMONITORING. VD = Global3AB8F080-950C-4EF9-B637-0F37B2428F171_SQLVDIMemoryName_0. 

In this example, the SQL Server instance named SBSMONITORING cannot create a snapshot.

The error of the source of the SQLWRITER message may also remain, which, in turn, occurs at about the same time as the first SQLVDI error. Sqlwriter Error message m It can determine the name of the database that has a problem with the entire snapshot. Name:

 log app Source: SQLWRITEREvent ID: 24583Description:Sqllib error: OLEDB error when calling ICommandText :: Run. hr means 0x80040e14. sqlstate: 42000, native error: 3013Error status: 1, severity: '07Source: Microsoft SQL Server Native Client 10.0Error message: BACKUP DATABASE crashes.SQLSTATE: 42000, Native Error 945:Error status: 2, severity: 12Source: Microsoft SQL Server Native Client 10.0 Post:error The "SBSMonitoring" database could not be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server Common Errors Log for more information. 

In this example, the database named SBSMonitoring has a nice problem.

After you have identified the problematic SQL Server event, the first step is to check for support when stopping the SQL Server instance. In our example with the SBSMonitoring instance, individuals would shut down the SQL server (SBSMonitoring) involved in server maintenance. It would be

Then you run each task Having a backup with the affected instance of SQL Server stopped. When the backup is complete and you know that the failure is mainly caused by a non-functional instance of SQL Server. You will then examine the SQL Server error log files and review the logs to see if we can influence what is wrong with this particular linked SQL Server instance.

If you cannot identify the problematic SQL Server instance from a person from the activity logs, you can always stop all SQL Server instances displayed on the server and try to backup using SQL Stop. Although instances of SQL Server are usually shut down, the SQL VSS writer is far from being used.

Using the Small Business Server 2008 installation standard, you will stop the following services:

• SQL Server (SBSMonitoring)
• Windows Internal Database

For this year’s Small Business Server installation standard, you will stop the following services:

• SQL Server (SharePoint)
• SQL Server (SBSMonitoring)
• Windows Internal Database

Improve the speed of your computer today by downloading this software — it will fix your PC problems.

Die Beste Möglichkeit, Probleme Mit Dem Fehler 0x800423f4 Zu Beheben
Beste Manier Om Fout 0x800423f4-problemen Te Herstellen
Il Miglior Piano Per Risolvere I Problemi Di Errore 0x800423f4
Meilleur Moyen De Résoudre Les Problèmes De Faux Pas 0x800423f4
감독 0x800423f4 문제를 해결하는 가장 좋은 방법
Bästa Sättet Att Hantera Fel 0x800423f4 Problem
Melhor Maneira De Resolver Problemas De Erro 0x800423f4
Лучшее решение для устранения проблем с ошибкой 0x800423f4
La Mejor Forma De Solucionar Problemas De Error 0x800423f4
Najlepszy Kurs Rozwiązywania Problemów Z Błędem 0x800423f4

The SBS 2011 (Exchange is at SP1) Windows 2008 R2 suddenly stopped making backups with error

Backup unsuccessful. A Volume Shadow Copy Service operation failed. Unknown error (0x800423f4).

When manually starting the backup from SBS console, the backup will fail after 52 seconds.

Hardware setup

The source of the backup are two RAID-1 volumes connected to a P420:

• 2 x 128GB Samsung SSD 840 — 78 GB out of 119 GB available
• 2 x 300GB ATA WDC WD3000HLFS — 218 GB out of 279 GB available

The backup destination is a USB drive with 298 GB of (free) space.

System State backup fails

> wbadmin start systemstatebackup -backuptarget:\?Volume{3956a561-b129-11e3-805c-7446a0f49555}
...(203.18 MB)...

Failure in a Volume Shadow Copy Service operation.

ERROR - Volume Shadow Copy Service operation error (0x800423f4)
The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.

I could not read .etl files

The wbadmin command output also points to log files that should be available at C:WindowsLogsWindowsServerBackup, however there are no .log files there (only .etl files).

NTDS writer is in state «[11] Failed»

> Vssadmin list writers

The only item with an error is the NTDS writer:

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {d88809aa-a5ef-460e-84c0-4dd8a8350184}
   State: [11] Failed
   Last error: Non-retryable error

Event viewer

In the event viewer Application event log the wbadmin start systemstate command registers

• an error for application Backup with Event-ID 521 and error number 2155348129.
• After starting the command the ESENT event-IDs occur is this order: 2001, 2001, 2003, 2006, 2003, 2006,
• then there is the VSS event 8229 with error 0x800423f4,
• then there are 18264 events (MSSQL database backup succeeded for MICROSOFT##SSEE, SBSMONITORING and SHAREPOINT),
• and finally there is the Backup event 521 with error 2155348129.

Regression

• Reboot
• Disable CrashPlan backup service
• Disable SQL Server VSS Writer
• C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN>PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

• Clear Volume Shadow Copy files for boot volume

  > vssadmin delete shadows /for=c: /all

• Set Volume Shadow Copy to use unlimited space on both volumes

• Delete backup catalog

  > wbadmin delete catalog

• Restart the Com and DCOM services

• Restart the Volume Shadow Copy Service
• Uninstall Windows Backup component; reboot; install Windows Backup component
• Install Update Rollup 4 for Windows Small Business Server 2011 Standard (KB2885319)
• Re-registering Vss Dlls
• Install Sharepoint 2010 Foundation SP2
• cd "C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN";PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
• increase swap file from 32MB to 1.5x RAM (90000 MB)
• Run dcdiag /fix; remove old domain controller; reboot; run dcdiag /fix again

Command «dcdiag /fix» fails

Starting test: NCSecDesc
    Error NT AUTHORITYENTERPRISE DOMAIN CONTROLLERS doesn't have
       Replicating Directory Changes In Filtered Set
    access rights for the naming context:
    DC=DomainDnsZones,DC=CONTOSO,DC=COM
    Error NT AUTHORITYENTERPRISE DOMAIN CONTROLLERS doesn't have
       Replicating Directory Changes In Filtered Set
    access rights for the naming context:
    DC=ForestDnsZones,DC=CONTOSO,DC=COM
    ......................... Contoso-DC1 failed test NCSecDesc 

FRS evntvwr

File Replication Service log shows some errors with id 13568, De File Replication-service de volgende fout aangetroffen in de replicaset DOMAIN SYSTEM VOLUME (SYSVOL SHARE): JRNL_WRAP_ERROR.

How do I let this backup complete its backups again?