![]() The provider was unable to perform the request. Windows explicitly rejected being able to perform a shadow copy at this time. ![]() ![]() VSS_E_PROVIDER_VETO (0x80042306): The shadow copy provider had an error. The shadow copies tab on disk properties will also not load. This issue can only be resolved by registry repair. VSS_E_PROVIDER_NOT_REGISTERED (0x80042304): The volume shadow copy provider is not registered in the system. Customers should perform chkdsk /F on impacted volumes followed by SFC and DISM scans. This error typically is associated with filesystem damage. VSS_E_UNEXPECTED (0x80042302): A volume shadow copy service (VSS) component encountered an unexpected error. May be prevalent on CSV storage that is not deployed to Microsoft standards. A reboot may resolve temporarily but may also be caused by raw volumes being present in the server in an offline state. This indicates that Microsoft's VSS framework and/or perhaps some of the VSS writers are in a bad state. VSS_E_BAD_STATE (0x80042301): A function call was made when the object was in an incorrect state. Should Unitrends support make such a recommendation, we will provide access to a senior engineer who will participate in 3rd party calls to Microsoft initiated by the customer to help accelerate resolution. Unitrends Support staff will have limitations on the amount of windows troubleshooting that can be done such to be able to provide guidance or recommendations when errors within windows itself are found, which will include researching Microsoft native errors to help determine potential root causes, but will typically recommend engagement of Microsoft support if the issue is not easily resolved. The below information is to provide general guidance. Unitrends software may or may not encounter all of these codes. Often the best troubleshooting of VSS errors is done by locating the "0x8" or href code in addition to related Windows EVT event IDs and search them online. Also suggested common root causes or resolutions equally are not all-inclusive. The list of errors below is not all inclusive. No code or settings changes to Unitrends or our agent can by itself resolve these issues, they typically require repairing the OS itself or addressing infrastructure concerns. When VSS has failed it is because Windows itself cannot internally perform the requested operation. No custom code is used by Unitrends to manage VSS, it is a native core component of Microsoft's OS. Unitrends does not cause VSS errors (though the act of attempting a snapshot will often have the result of encountering the error). If VSS is non-functional, Unitrends will not be able to take safe backups of the server until the issue is resolved. Though a restart of services or windows itself will often temporarily solve a VSS issue, understand that if the underlying condition or event that caused VSS to enter a failed state re-occurs, the VSS error will also reoccur. VSS failures can sometimes be trivially solved and are transient, in other cases thay are related to improper deployment or configuration of the windows OS or applications within, and sometimes indicate catastrophic damage to windows has occurred often requiring rollback to prior known good states, disaster recovery, or complete server rebuild. If the VSS service cannot operate properly, it will produce specific errors visible to and collected by Unitrends, as well as log events in the Windows Event Viewer, and result in backup failure. VSS (Volume Shadowcopy Services) is a core component of windows that permits backup operators like Unitrends to safely protect a windows system while it is running. Quick link to RESOLUTION Steps About VSS Errors: ![]() Windows Volume Shadow copy Services (VSS) Problem Determination
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |