Vssvc crashes after restoring a VMware VM

book

Article ID: 100052351

calendar_today

Updated On:

Description

Error Message

Log Name:      Application
Source:        Application Error
Date:          1/27/2022 12:18:58 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer_name
Description:
Faulting application name: vssvc.exe, version: 6.3.9600.18229, time stamp: 0x56b4b5d7
Faulting module name: vssvc.exe, version: 6.3.9600.18229, time stamp: 0x56b4b5d7
Exception code: 0xc0000005
Fault offset: 0x000000000008771a
Faulting process id: 0xe84
Faulting application start time: 0x01d8133d62e49192
Faulting application path: C:\Windows\system32\vssvc.exe
Faulting module path: C:\Windows\system32\vssvc.exe
Report Id: a0ab563d-7f30-11ec-80f9-005056b84a89
Faulting package full name: 
Faulting package-relative application ID:

 

Vssadmin list shadows command also fails.

C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.


Error: Unexpected failure: The remote procedure call failed.

 

Cause

'Veritas VSS Provider' has been installed to VSS. This provider should be removed after restoring a VM.

 

C:\> vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Veritas VSS Provider'
   Provider type: Software
   Provider Id: {5fdb6ef5-6ead-4610-995b-401c88626115}
   Version: 1.0

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Note: The information above is a description about the VSS provider. Each VMware VM should have the "Veritas VSS Provider" service with the same name.

 

Resolution

The issue is fixed in Backup Exec 22.

Workaround:

1. Download fixbevss.zip attached.

2. Extract the zip and get two bat files.

  1. post-thaw-script.bat
  2. pre-freeze-script.bat

3. Copy the two bat files to two locations on each VM.

  1. C:\Program Files\Veritas\Backup Exec\RAWS\VSS Provider (by default)
  2. C:\Windows

4. Get backup of the VM(s).
 

 

Issue/Introduction

Vssvc crashes after restoring a VMware VM.

Additional Information

ETrack: 4065126

Attachments

fixbevss.zip get_app