Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3299

January 20th, 2016 02:00

avamar 7.1-avvss Error <5953>: Unable to allocate wide string of length 0.

Hi, I encountered the below error on win 2K8.Anyone had experienced and solved  this issue before.Many Thanks.

2016-01-19 17:22:12 avvss Error <5953>: Unable to allocate wide string of length 0.
2016-01-19 17:22:12 avvss Info <10967>: Found System Provider GUID. Will be using the System Provider GUID to perform backup
2016-01-19 17:22:12 avvss Error <10972>: Unable to determine if volume \\?\globalroot\device\harddiskvolume1 is supported by Microsoft system provider GUID ={b5946137-7b9f-4925-af8051abd60b20}, error = 0x80042308
2016-01-19 17:22:12 avvss Error <12077>: VSS returned an error message exiting HR = 0x80042308
2016-01-19 17:22:12 avvss Info <7271>: Final summary generated subwork 0, cancelled/aborted 0, snapview 0, exitcode 536870919
2016-01-19 17:22:12 avvss Info <8394>: Deleting temporary stored metadata files...
2016-01-19 17:22:12 avvss Warning <8395>: File MetadataFilesList.txt can not be removed. Error code 2
2016-01-19 17:22:12 avvss Info <7753>: Exit main body...
2016-01-19 17:22:12 avvss Info <8330>: uvss returning with exitcode 536870919

6 Posts

February 1st, 2016 22:00

Hi Guys,

The solution on this issue is done by upgrading the client plugins to 7.0 since the Avamar 6 does not support EFI boot partition in VSS backups. Thanks

January 22nd, 2016 09:00

Hi tatan

Please find following suggestion:


In Order to troubleshoot this issue, please do the following steps:

Step 1-
Verify the number of VSS Providers listed.There should be only one provider as below-

1. Open cmd with "Run As" Administrator
2. At prompt type:vssadmin list providers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

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

VSS backups are not supported if you have more than one VSS providers listed.

Step-2
1. Open cmd with “Run As” Administrator
2. At prompt type:Diskshadow
3. At prompt type:add volume c:
4. At prompt type:create

If you get the following:  COM call "lvssObject4->GetRootAndLogicalPrefixPaths" failed.
Then Avamar is not the cause of the VSS backup failure.See the following Microsoft TechNet KB article for the process:  http://technet.microsoft.com/en-us/library/cc772172.aspx


If you are able to create dishshadow, please proceed with following to now delete it from cmd prompt:

1. Open cmd with “Run As” Administrator
2. At prompt type:Delete shadows volume c:
3. type:exit

Step-3
1. Open cmd with “Run As” Administrator
2. At prompt type:msinfo32.exe to get the system information report
3. Also at prompt type:bcdedit.exe and see the output.

C:\Users\Administrateur>bcdedit.exe

Gestionnaire de démarrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {current}
resumeobject            {3a0f009f-cd65-11e2-b4af-3440b5d6bda6}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Chargeur de démarrage Windows
-----------------------------
identificateur          {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows Server 2008 R2
locale                  fr-FR
inherit                 {bootloadersettings}
recoverysequence        {3a0f00a1-cd65-11e2-b4af-3440b5d6bda6}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {3a0f009f-cd65-11e2-b4af-3440b5d6bda6}
nx                      OptOut

You will see the root cause of the issue which is EFI partition in result.
The EFI partition is not supported by the VSS backup with Avamar client 6.x.
However this will be supported in version 7 of Avamar.
As a work around you can backup the EFI manually using the Microsoft backup tool and let the Avamar backup the file created by the backup.

The use of "Extended Firmware Interface" (EFI) is not supported when performing Windows VSS System State backups."

For DR backup, please use Windows Server Backup perform system recovery (bare-metal recovery) backup to a share folder or a non-critical volume, then use Avamar backup to backup that share folder or volume.

6 Posts

January 23rd, 2016 20:00

Hi Shridhar,

Thanks for your inputs..I will try these and give you feedback.

6 Posts

January 25th, 2016 00:00

Hi Shridhar,

I did not get this error: COM call "lvssObject4->GetRootAndLogicalPrefixPaths" failed upon creating the diskshadow.Any suggestions on how to eliminate the above errors I have posted since they are recurring on our 3 servers?

Thanks

2K Posts

January 25th, 2016 06:00

It sounds like these systems may be low on resources. A system that's low on disk space will not be able to create VSS snapshots.

6 Posts

January 25th, 2016 21:00

Hi Ian,

The system has enough free space.Is there any solution/s on this issue?Thanks

2K Posts

January 26th, 2016 06:00

There is not enough information here to determine the root cause of the problem. I would recommend that you generate a new set of logs in debug mode and open a service request.

No Events found!

Top