Hy Guys,
We got the following Error using VCB on Proxy Server running Windows Server 2003 Standard 32-bit SP2:
"Vmount2.Vmount2WinVolume: Unable to get volume size for
.\vstor3Bus-15A415A4007E00000000000067000000: Windisk_Open failed with err=2"
The problem occurs during the mounting phase.
On the Virtual Center side we checked out that the snapshot on the Virtual
Machine has been created and completed correctly.
We got the same error (just once) also using command:
vcbmounter -h pvvcisp1.asl5.vi -u UserName -p pwd -a name:PVFSVSP2
-r c:\mnt\PVFSVSP2 -t fullvm >> c:\mnt\PVFSVSP2.log
We also try to Stop/Start the "Vmware Virtual Mount Service Extended"
windows service but the error still present.
Does anybody else faced with this error signature ?
Thanks for any suggestion.
Here below the the Vmware Infrastructure 3 profile:
- Host Hypervisor: Vmware ESX 3.0.2 (Build 52542; + Path Release Nov/15th/2007)
- Vmware Consolidation Backup (VCB) 1.0.3 Update-1 (Build 58377)
- Vmware Virtual Center 2.0.2 (Build 50618)
- Legato Networker 7.4 SP1
. LNIM: VMware-legato-networker-integration-51389_ESX302.zip
And the excerpt from the VCB Proxy Log file fron the last run (May/15th 14.30)
....
Status: (VmountDisk:233) disk blklst://snapshot-6476[StSysAppl1] PVFSVSP2/PVFSVSP2.vmdk@pvvcisp1.asl5.vi:902 was opened
Status: (VmountDisk:233) disk blklst://snapshot-6476[StSwapGuest1] PVFSVSP2/PVFSVSP2_SwapGuest.vmdk@pvvcisp1.asl5.vi:902 was opened
Status: (VmountDisk:233) disk blklst://snapshot-6476[StDataFsv1] PVFSVSP2/PVFSVSP2_data1.vmdk@pvvcisp1.asl5.vi:902 was opened
Status: (VmountDevice:1513) device of type volume with offset 32256 was created
Status: (VmountDevice:1513) device of type volume with offset 32256 was created
Status: (VmountDevice:1513) device of type volume with offset 32256 was created
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2Device: no drive letter currently assigned
Error: (VmountLocator:111) Vmount2.Vmount2WinVolume: Unable to get volume size for
.\vstor3Bus-15A415A4007E00000000000064000000: Windisk_Open failed with err=2
Error: (VmountLocator:111) Vmount2.Vmount2WinVolume: Unable to get volume size for
.\vstor3Bus-BE97DD26007E00000000000065000000: Windisk_Open failed with err=2
Error: (VmountLocator:111) Vmount2.Vmount2WinVolume: Unable to get volume size for
.\vstor3Bus-BC97DD26007E00000000000066000000: Windisk_Open failed with err=2
Status: (VmountDevice:143) device of type volume with offset 32256 was closed
Status: (VmountDevice:143) device of type volume with offset 32256 was closed
Status: (VmountDevice:143) device of type volume with offset 32256 was closed
Status: (VmountDisk:413) disk blklst://snapshot-6476[StSysAppl1] PVFSVSP2/PVFSVSP2.vmdk@pvvcisp1.asl5.vi:902 was closed
Status: (VmountDisk:413) disk blklst://snapshot-6476[StSwapGuest1] PVFSVSP2/PVFSVSP2_SwapGuest.vmdk@pvvcisp1.asl5.vi:902 was closed
Status: (VmountDisk:413) disk blklst://snapshot-6476[StDataFsv1] PVFSVSP2/PVFSVSP2_data1.vmdk@pvvcisp1.asl5.vi:902 was closed
We submitt an SR to Vmware and we got an answer that successfully solved our problem,
hereafter the solution that we applied:
Re-Installation of the VCB which are in detail:
- Remove the VCB (by using VCB executable, not by "Control Panel >Add Remove Program")
- In addition we removed also the VMware Converter 3.0.
- Installation of the VCB Framework.
Problem disappear.