Error V-79-57344-38721intrduced by SP1

[harsi]

The error V-79-57344-38721 has been introduced by BE 2010 R3 SP1, so you should carefully consider installing it or not esp. as Symantec seems not to have any intention to fix the problem in the current release.

http://www.symantec.com/business/support/index?page=content&id=TECH170723&key=15047

[harsi]

We made some test to find out which part of SP1 causes that issue.

It's Hotfix 164220.

So if you are affected by this problem uninstall SP1 and install all hotfixes except 164220.

[DevG]

Yes, the error mentioned and the article referred is acknowledged as an issue currently with BE 2010 R3 under investigation. I would not suggest to uninstall SP1 for BE 2010 R3 (as it cannot be uninstalled anyway) and suggest to log a case with support for users experiencing this issue as information is still being gathered.

[CraigV]

@harsi: please head on over to the Known Issues section on the link below. If your issue is listed there please give it a thumb's up...

https://www-secure.symantec.com/connect/backup-and-archiving/issues

[harsi]

I would not suggest to uninstall SP1 for BE 2010 R3 (as it cannot be uninstalled anyway)

Of course it can be uninstalled.

Why do you assume this is not possible?

What would you suggest instead? To live with a bug which wasn't there before installing this SP?

[Colin_Weaver]

I just checked that issue - the article you read, accidentally had the wrong disclaimer entered - it should have read as under investigation. This has been corrected but might take a few hours for this correction to be reflected on the public version.

One point to note however - the customer's case that was being investigated that is directly linked with the creation of that document shows they had the problem before SP1 and/or Hotfix 164220, as such we do not consider the problem in that article to have been introduced by SP1.

If you have something similar that was started by SP1 then you have a different issue and we would ask that you do log a formal support case for us to look into it further.

[harsi]

Thanks for the hint with the other customers case.

Maybe the problem exists pre 164220 and is only triggered/emphased by 164220.

Here it is reproducable. We chekced multiple times.

Install 164220 - problem exists, remove it - problem gone.

Interrestingly it always happens on the exact same two out of 25 VMs.

[Colin_Weaver]

Thanks for info - I have just linked this forum thread into the existing engineering escalation just so that our engineering team are aware of it.

[YvieD]

Do you have RAWS on those two VMs?  If so, uninstall and reinstall it then run the job again. Does that change the behavior?

Second, from the command prompt inside the guest machine type  

C:\> diskpart  

Then, in the Disk Partition Tool type

DISKPART> list disk

The 6th column reads "Gpt"   If there is an asterisk for any of the volumes of the virtual machine, see this technote:

http://www.symantec.com/docs/TECH167969