Table of Contents
PC running slow?
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.
PC running slow?
ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!
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.
How to fix error 0x800423F4?
Log into our Hyper-V Guest (VM).Delete the registry key HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services VSS Suppliers 74600e39-7dc5-4567-a03b-f091d6c7b092.Restart the Hyper-V Volume Shadow Copy Requestor service, possibly restart the guest.
What is VSS error in event viewer?
Windows events can be logged by the system and can be used to troubleshoot issues during exposure or backing up files and folders. Microsoft Windows Shadow Copy Service (VSS) logs warning and error events when a VSS interrupt occurs. These events are a valuable reservoir for troubleshooting system problems. …
What is Vssadmin list writers?
A list of currently available writers can be found on the command line on any Windows computer. Run Command Prompt asadministrator and run the command: vssadmin list folks. This command lists all recording devices currently available on the computer and displays the status of each.
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
