Failed to create/remove snapshots

Similar Questions

• «FAILED: failed to create a snapshot of the source volumes VSS.» Error code: 2147754758 (0 x 80042306). "Down to 1% with autonomous converted 5.5

  Hi all

  I'm trying to convert a physical Windows 2008 R2 (SP1) virtual, using Vmware vCenter Converter Standalone version 5.5 build 1362012, it fails at 1% (after around 40mins) with the following message

  Failed: Failed to create a snapshot VSS of the source volumes. Error code:
  

  2147754758 (0 x 80042306).

  
  

  Windows systems has some LUN (4 x each various size GB) San, being the GUID (GPT) Partition Table.  I went through the wizard as a general rule, by selecting "edited on the machine", a player selected vmware "vmware workstation" or another vmware virtual machine destination 6.0.x and the location of the target being a LUN with 500 GB of space.

  Now for the data to be copied I selected 3 LUN (on a database resides) and put the 'Size' option (but I tried to keep the size of the various passes) to save space.

  
  

  Looking through the logs, I see the following errors

  Server-convert-VMware - 1.log

  2014 01-16 T 19: 42:37.371 - 07:00 [info 08696 'Default'] [serviceWin32, 416] Server vmware-converter service started

  2014 01-16 T 19: 42:51.006 - 07:00 [08696 info "Libs"] username [ADS] Get failed: 1332

  2014 01-16 T 19: 42:51.006 - 07:00 [08696 info "Libs"] [ADS] subtle failed: 1312

  2014 01-16 T 19: 42:51.115 - 07:00 [info 08696 'Default'] [user, 874] successfully authenticated the user administrator of the local computer (by using pipe)

  2014 01-16 T 19: 43:38.898 - 07:00 [10116 info "Libs"] username [ADS] Get failed: 1332

  2014 01-16 T 19: 43:38.898 - 07:00 [10116 info "Libs"] [ADS] subtle failed: 1312

  2014 01-16 T 19: 43:39.023 - 07:00 [info 10116 'Default'] [user, 874] successfully authenticated the user administrator of the local computer (by using pipe)

  2014 01-16 T 19: 43:39.647 - 07:00 [info 07628 "ThreadPool"] Thread has enlisted

  2014 01-16 T 19: 44:26.152 - 07:00 [08696 error 'Ufa.HTTPService'] cannot read the request; flow: io_obj p:0x0141b84c, h:-1, < tube "\\.\pipe\vmware-converter-server-soap" >, < pipe "\\.\pipe\vmware-converter-server-soap" > >, error: class Vmacore::TimeoutException (operation timed out)

  2014 01-16 T 19: 47:32.

  Worker-converter-VMware - 1.log

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 "Default"] disk number 1 has been ignored due to errors when reading partition table

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 "Default"] disk number 1 has been ignored due to errors during playback of dynamic disks header or LDM database is corrupt

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 'Default'] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, error mntapi: 176

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 'Default'] score: Invalid magic number sector.

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 'Default'] score: Invalid magic number sector.

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 'Default'] [PopulateCapabilities] based on the Volume of cloning has been disabled due to: no volume is recognized >

  ..

  2014 01-16 T 19: 47:34.323 - 07:00 [warning 07248 "Default"] Partition: ERROR: MBR sector must be present and valid initialize to GPT disk.

  2014 01-16 T 19: 47:34.354 - 07:00 [info 07248 'Default'] signature of disk found 80a2884a-05e9-4c1b-81-3d-35-1b-a3-6c-4b-bc, drive to 225981112, sectors 512 sector size size

  2014 01-16 T 19: 47:34.354 - 07:00 [info 07248 "Default"] Partition found type Efi system / single 4078aaff-430e-4825-bf-07-67-c6-ab-a1-87-3f

  ...

  2014 01-16 T 19: 47:37.365 - 07:00 [info 07596 "ThreadPool"] wire removed from the list

  2014 01-16 T 19: 47:37.412 - 07:00 [10164 info "ThreadPool"] Thread has enlisted

  2014 01-16 T 19: 47:37.459 - 07:00 [info 07696 "Default"] MNTAPI: mounted volume \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:37.584 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:37.677 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:37.755 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:37.849 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:37.942 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:38.052 - 07:00 [info 07696 "Default"] error 0 when calling GetVolumeInformation for \\.\vstor2-mntapi20-shared-444D494F3A49443AFFAA78400E432548BF0767C6ABA1873F03000000\ FS: <>

  2014 01-16 T 19: 47:38.098 - 07:00 [10164 info "ThreadPool"] wire removed from the list

  2014 01-16 T 19: 47:38.098 - 07:00 [info 03736 "ThreadPool"] Thread has enlisted

  I wonder if the converter is not able to work on the GPT partitions?  (I think I saw some discussion of the community on this problem using v.5.1, but using 5.5 should be resolved?)

  Any help is appreciated. Thank you

  Your problem is with VSS, it is probably the lack of space, to seek solutions and similar problems.

  Errors that you see are expected, we need a full newspaper bundle for investigation and don't warry on GPT disks, they are supported with converter 5 +.

• Another: failed: cannot create a snapshot VSS of the source volumes. Error 2147549183 but on XP Pro

  I am changing a laptop Windows XP Pro using the converter software 4.0.1.

  He will start the conversion process, but after 10 seconds or so, I get the error: failed: cannot create a snapshot VSS of the source volumes. Error 2147549183

  The strange thing is my images of box Vista successfully without problem.

  I'm in a corporate environment. I moved the laptop test I try the image of an OU restrictive and placed in a non-restrictive ORGANIZATIONAL unit (without firewalls and others). I always have the same question.

  I made sure all the VSS services and these are running and active. I even tried MS KB Article 941956 comes to do even if it said it was only for Server 2003.

  Any other pointers on this? It seems that a lot of people get this error, but the only ones I can find are for server operating systems... not XP.

  In the event under application Viewer I have errors of:

  Type: error

  Event ID: 12292

  The volume shadow copy Service error. Error creating the Shadow Copy Provider COM with CLSID {65ee1dba-8ffa-4a58-ac1c-3470ee2f376a} class

  Type: WARNING

  Event ID: 4356

  {The COM system + impossible to create an instance of the Subscriber partition:{41e90f3e-56c1-4633-81c3-6e8bac8bdd70}!new:{d3938ab0-5b9d-11d1-8dd2-00aa004abd5e}. CoGetObject returned HRESULT 80070005

  Type: WARNING

  Event ID: 4353

  The event of COM + a system attempted to raise the EventObjectChange::ChangedSubscription event but received a bad return code. HRESULT was80040201

  Type: error

  Event ID: 8193

  Volume Shadow Copy Service Error: Unexpected error calling routine CoCreateInstance. HR = 0 x 80004002

  You are able to start these three services; EventSystem, swprv, vss?

  What is this command returns; "vssadmin list writers"?

  Joakim

• More about "ERROR: failed to create a snapshot of a volume of the source.

  I saw the previous posts on this and have tried to follow all the advice, but nothing helped.  I am running XP and you have two hard drives, NTFS and both have plenty of space.  My destination is an external hard drive, FAT32, with plenty of room.  I get the ERROR message: failed to create a snapshot of a volume of the source. Ppossible causes include not seen all NTFS volumes on Windows XP or Windows 2003 source systems with no is not enough of disk space.

  I installed the converter as an administrator, I rebooted several times, I ran / f checkdsk on both hard drives and external drives, I have disabled all the services that I am uncomfortable, turn off, but just, I get this message.  I have attached the log file.

  Thanks for any help.

  drbking wrote:

  I see that a small part of my answer was missing - the microsoft running thing, I found I was missing vssui.dll.  Downloaded, ran the microsoft thing and am now running the converter again.  Know in the morning, if it works (takes about 9 hours).

  How is the conversion?

  -Ryan

• Failed to create a snapshot with 2 TB of virtual disk?

  I have a virtual file server with a 2 TB virtual disk (vmdk).  When I try to create a snapshot of the system (to save), I get the following error:

  < Unspecified file name > file is larger than the maximum size supported by the data store ' < unspecified datastore >.

  The data store located on the file server is formatted with 5.54 VMFS with size of 1 MB.  It's a data store of 12 TB with about 6 TB free.

  That is right.  If you want to take a snapshot, then the maximum size is GB 2032.   And this is the case even if thin you load the disc.

• VCB error: failed to create a snapshot suspended because the snapshot creation operation has timed out for holding off the coast of I/O in the frozen VM

  Hi all, I have a problem, creating a model by cloning the Live VM for Windows Server 2003 x 64 Standard edition and in fact it happens on my own install Windows Server 2008 R2 Enterprise x 64 as well?

  Here is the error message:

  Creating snapshot of the Virtual Machine

  * _Cannot

  create a suspended because the create snapshot snapshot operation

  timed for the outfit out of e/s in virtual jelly

  machine._*

  I installed the VMWare tools and make sure that the VSS service are all on but he failed.

  any help in this matter would be greatly appreciated.

  Thank you.

  Kind regards

  AWT

  Check out my Guide to proven practices VCB on the VI:OPS website-> http://viops.vmware.com/home/docs/DOC-1392

  Dave Convery

  VMware vExpert 2009

  http://www.dailyhypervisor.com

  http://Twitter.com/dconvery

  Prudent. We do not want to make of this.

  Bill Watterson, "Calvin and Hobbes".

• V2v error a server using Vmware Converter has FAILED: cannot create a snapshot VSS of the source volumes. Error code: 109 (0x0000006D)

  I have the above, when you try to v2v, a server or ESXi server as a workstation or a HARD drive.  I have a lot of space on the disk being cloned to, everyone had this before, can you please provide a resolution? #

  Thank you

  Chris

  Looks like what ive solved this now.  Ive disabled SQL VSS Writter and a product called Neverfail (we use to DR our servers).  Since ive done this im now able to create snapshots and images begin to generate.

• Deletion of snapshots failed, how to remove snapshots?

  Hello

  I tried to delete/merge snapshots to a server, and the operation has failed with an error saying that there is not enough disk space on the lun.

  In the snapshots via the vSphere client Manager, there is no more available snapshots, see the disk names:

  The virtual machine has two disks

  [xxx [lun-xxx-Server] Server] / 01-xxx-service - 000001.vmdk
  [xxx [lun-xxx-Server] Server] / 01-xxx-service_1 - 000006.vmdk

  He always uses the instant vmdk for two disks and more and more.

  How can I stop this and merge with basic disks?

  [xxx [lun-xxx-Server] Server] / xxx-01 - service.vmdk
  [xxx [lun-xxx-Server] Server] / xxx-01 - service.vmdk

  When I browse the data store there are still a few shots left and more... (see screenshot)

  
  

  Take also look at this article

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1002310

  It explains exactly what to do in your situation

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Disco of VmWare Converter problema su spazio - ERROR: failed to create a snapshot of a volume of the source. Possible causes include not seen all NTFS volumes on Windows XP or Windows 2003 source systems with no is not enough free space on the disk.

  Buongiorno,

  Devo connvertire con vmware converter one Nt Server con AC 450MO di spazio libero su disco C: ntfs file system e

  Ricevo this error:

  ERROR: Impossible to take snapshots of a volume of the source. Possible causes include not seen all NTFS volumes on Windows XP or Windows 2003 source systems with no is not enough free space on the disk.

  He problema e che no ho the possibility di līberō altro spazio.

  Some suggestions?

  Grazie in pre-empted.

  Anni fa it era questa versione di VMware Converter: https://dl.dropboxusercontent.com/u/2197180/coldclone.3.03.iso che permetteva the clonazione a freddo. :-)

• 2 VDR "impossible to create the snapshot for &lt; system &gt;, error-3960 (cannot suspend virtual machine).

  We test VDR on our ESXi 4.1.0 cluster 381591 and we have a few backups to a test Windows 2003 server and a Linux server and they backed up fine. We have a backup of a Windows 7 computer virtual test and we had a bunch of these errors...

  Failed to create the snapshot for systemname, error-3960 (can not suspend virtual machine)

  Which is strange because I can go in vSphere client and manually create a snapshot and remove without problem. Any ideas on why this is happening?

  Thank you

  You can try to set the 'disk. EnableUUID' to 'false '.

  Look here:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1031298

  Paul

• Failed to remove snapshot due to disk space

  Hello!

  I tried to delete a snapshot in 10 workstation, but it failed because I ran out of space - fair enough, BUT he DID remove the snapshot icon.

  Now, I have freed disk space in order to remove the snapshot, but how can I do when the icon is missing?

  I can't just clone the virtual computer to a new place because I need other snapshots!

  I have about 20 shots then how do I know which one it is?

  Best regards

  -Morten Hermansen, Fanitas Green

  I found the same thing. It is not a good behavior of the software, because it leaves doubts: it is not deleted, but how can I remove it?

  I think that if it fails it should leave the icon to try again after you free the space.

  Is a possible workaround: create another snapshot, and then delete it somewhere inside the machine snapshot tree.

  For what I could see by looking at the disk space, after this deletion, the used space is lower than before the creation. I guess this operation triggers the actual deletion of the snapshot has disappeared. In addition, this deletion takes a long time, all in one

  'create and delete soon' should be very fast.

• Remove Snapshot failed

  For one of my vhost migrate to another clusterfarm I need to merge/delete all snapshots beforehand.  I ' am aware that VC has a code in 15 hard minutes buildin timeout and snapshot process will still work in the background, even if a timeout error / in VC occurs.  SO today I tried to remove this snapshot of 30 GB to VI and he ran in this wait time, wait a few hours to let her finish in the background, but it seems that he failed and created a new snapshot file. I still see this snapshot to VI and filelevel (the first snapshot1, check below).

  If you know how to solve this problem?

  09:36:53.266 Jul 08: vmx\

  SnapshotVMX_Consolidate: from 09:36:53.410 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8 09:36:53.420 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed. 09:36:53.458 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8 09:36:53.476 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed. 09:36:53.510 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 3 09:36:53.522 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': closed. 09:36:53.522 Jul 08: vmx\

  ConsolidateOnlineCB: nextState = uid 0 0 09:36:53.524 Jul 08: vcpu-0

  Sync monModules (1). 09:36:53.524 Jul 08: vcpu-1\

  Sync monModules (1). 09:36:53.524 Jul 08: vcpu-1\

  Fact Sync monModules (1). 09:36:53.524 Jul 08: vcpu-0

  Fact Sync monModules (1). 09:36:53.534 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed. 09:36:53.534 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': closed. 09:36:53.534 Jul 08: vmx\

  Virtual device for scsi0:0 had already managed to destroy 09:36:53.534 Jul 08: vmx\

  ConsolidateOnlineCB: nextState = 1 uid 0 09:36:53.570 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8 09:36:53.584 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed. 09:36:53.601 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:53.610 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed.

  09:36:53.631 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 3

  09:36:53.644 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': closed.

  09:36:53.696 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:53.700 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed.

  09:36:53.756 Jul 08: vmx\

  TRUCK: Creating /vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-Snapshot2.vmsn file checkpoint

  09:36:53.771 Jul 08: vmx\

  FILEIO: pread received 0 out of 4 bytes.

  09:36:53.788 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:53.858 Jul 08: vmx\

  DISKLIB-VMFS_SPARSE: ExtentCreate ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': success

  09:36:53.887 Jul 08: vmx\

  DISKLIB-LINK: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk ': successful creation.

  09:36:53.916 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': (17) successfully opened size = 146707142656, hd = 0. Type 8

  09:36:53.963 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': closed.

  09:36:53.966 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed.

  09:36:54.048 Jul 08: vmx\

  VMXVmdb_LoadRawConfig: Loading of raw configuration

  09:36:54.056 Jul 08: vmx\

  ConsolidateOnlineCB: nextState = uid 1 2

  09:36:54.117 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:54.120 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': closed.

  09:36:54.132 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:54.142 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed.

  09:36:54.159 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:54.162 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': closed.

  09:36:54.173 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 8

  09:36:54.176 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': closed.

  09:36:54.190 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': open with success (21) size = 146707142656, hd = 0. Type 3

  09:36:54.193 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': closed.

  09:36:54.199 Jul 08: vmx\

  Checkpoint_Unstun: vm for 675661 us order

  09:36:54.302 Jul 08: vcpu-0

  Sync monModules (5).

  09:36:54.303 Jul 08: vcpu-0

  Fact monModules Sync (5).

  09:36:54.404 Jul 08: vcpu-1\

  Sync monModules (5).

  09:36:54.404 Jul 08: vcpu-1\

  Fact monModules Sync (5).

  09:36:54.407 Jul 08: vmx\

  DISC: Scsi0:0 OPEN vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk' R [(null) persistent]

  09:36:54.454 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002-delta.vmdk ': open with success (8) size = 282112, hd = 614466. Type 8

  09:36:54.455 Jul 08: vmx\

  DISKLIB-DSCPTR: open : ' vmsrv023-000002 - delta.vmdk ' (0 x 8)

  09:36:54.455 Jul 08: vmx\

  DISKLIB-LINK: open ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk' (0 x 8): vmfsSparse, 286537388 sectors / MB 139911.

  09:36:54.496 Jul 08: vmx\

  DISKLIB-LIB: open "/ vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk" (flags 0 x 8). 883C114

  09:36:54.530 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001-delta.vmdk ': open with success (8) size = 31088463360, hd = 385092. Type 8

  09:36:54.530 Jul 08: vmx\

  DISKLIB-DSCPTR: open : ' vmsrv023-000001 - delta.vmdk ' (0 x 8)

  09:36:54.530 Jul 08: vmx\

  DISKLIB-LINK: open ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001.vmdk' (0 x 8): vmfsSparse, 286537388 sectors / MB 139911.

  09:36:54.568 Jul 08: vmx\

  DISKLIB-LIB: open "/ vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000001.vmdk" (flags 0 x 8). 88FA684

  09:37:24.676 Jul 08: vmx\

  DISKLIB-VMFS: ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-flat.vmdk ': open with success (10) size = 146707142656, hd = 282694. Type 3

  09:37:24.676 Jul 08: vmx\

  DISKLIB-DSCPTR: open : 'vmsrv023 - flat hard' (0xa)

  09:37:24.676 Jul 08: vmx\

  DISKLIB-LINK: open ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023.vmdk' (0xa): vmfs, 286537388 sectors / MB 139911.

  09:37:24.681 Jul 08: vmx\

  DISKLIB-LIB: open "/ vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023.vmdk" (flags 0xa). 88FA684

  09:37:24.769 Jul 08: vmx\

  DRIVE: OPEN the ' / vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk' Geo (17836/255/63) BIOS Geo (0, 0, 0) freeSpace = Mo 245224, free

  09:37:24.772 Jul 08: vmx\

  Creating virtual dev for 0:0

  09:37:24.775 Jul 08: vmx\

  DumpDiskInfo: scsi0:0 = 11, 286537388 = capacity createType, numLinks = 3, allocationType = 0

  09:37:24.775 Jul 08: vmx\

  SCSIDiskESXPopulateVDevDesc: FS backend using

  09:37:24.775 Jul 08: vmx\

  VMMon_SetStorageSchedPolicy: Unsupported

  09:37:24.778 Jul 08: vmx\

  ConsolidateOnlineCB: nextState = 2 2 uid

  09:37:24.779 Jul 08: vmx\

  ConsolidateThread: Created the thread for scsi0:0 6

  09:37:24.779 Jul 08: SnapshotVMXCombiner\

  ConsolidateOnlineCB: nextState = 3 uid 2

  09:37:24.779 Jul 08: SnapshotVMXCombiner\

  ConsolidateOnlineCB: From scsi0:0 vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk cartel. 2 links from 1

  09:37:24.788 Jul 08: SnapshotVMXCombiner\

  DISKLIB-LIB: combine 2 links to 1 offset in the string 883C114.

  09:37:24.845 Jul 08: vcpu-0

  HBACommon: first write on scsi0:0.fileName='/vmfs/volumes/37997983-4fd6ffeb/vmsrv023/vmsrv023-000002.vmdk'

  09:37:24.853 Jul 08: vcpu-0

  STRING DISKLIB: UpdateContentID: old = 0xc1c14299 new = 0xae71ec6f

  10:48:08.134 Jul 08: mks\

  SOCKET recv 3 5 error: input/output error

  10:48:08.143 Jul 08: mks\

  SOCKET 3 destroying backend VNC on socket error: 5

  LS - ltrh Total 167G

  -rw - 1 root root 3.0 G Apr 9 12:37 vmsrv023 - 74efdabe.vswp

  -rw - rr 1 root root 45 K 3 Jun 10:39 vmware - 9.log

  -rw - rr 1 root root 3 Jun 10:52 vmware - 10.log 45 K

  -rw - rr 1 root root 3 Jun 11:12 vmware - 11.log 45 K

  -rw - rr 1 root root 3 Jun 17:26 vmware - 12.log 53 K

  -rw - rr 1 root root 3 Jun 17:41 vmware - 13.log 46 K

  -rw - rr 1 root root 37 3 Jun 18:25 vmsrv023 - 74efdabe.hlog

  -rw - 1 root root 252 3 Jun 18:25 vmsrv023 - 000001.vmdk

  -rw - rr 1 root root 3 Jun 18:25 vmware - 14.log 47 K

  -rw - 1 root root 8.5 K 3 Jun 18:25 vmsrv023.nvram

  -rw - 1 root root 263 3 Jul 23:11 vmsrv023.vmxf

  -rw - 1 root root 19 K 8 Jul 10:37 vmsrv023 - Snapshot2.vmsn

  -rw - 1 root root 29 G 8 Jul 10:37 vmsrv023-000001 - delta.vmdk

  -rwxr-xr-x 1 root root 2.2 K 8 Jul 10:37 vmsrv023.vmx

  -rw - 1 root root 494 8 Jul 10:37 vmsrv023.vmsd

  -rw - 1 root root 403 8 Jul 10:37 vmsrv023.vmdk

  -rw - 1 root root 233 8 Jul 10:37 vmsrv023 - 000002.vmdk

  -rw - rr 1 root root 53 K 8 Jul 11:49 vmware.log

  -rw - 1 root root 137G Jul 8 14:28 vmsrv023 - flat hard

  • -rw - 1 root root 1.3 G Jul 8 14:28 vmsrv023-000002 - delta.vmdk *.

  you collate vdf h?

  Get a WINSCP, connect to your ESX and check too.

  review the allocation of points for

  "Correct" or "useful."

• Error when you open Add or remove programs: "failed to create value" At Line 451 how this can be corrected?

  Once all updates completed, I now can't add remove programs to work.

  I get the following in a box error message: "failed to create value"at line 451.

  Someone knows how to fix this?

  Hi ZebWebb,

  1. What service pack is installed on the computer?
  2. You have security software installed on the computer?

  If you have recently installed Windows XP SP1 on the computer, then see the article and check if that helps.

  Error when you open Add or remove programs: ' failed 'at line 410' of value creation.

  http://support.Microsoft.com/?kbid=823768

  If you have not installed Service Pack 1 of Windows XP on the computer recently then check if the problem persists in the safe mode and after return details.

  A description of the options to start in Windows XP Mode

  http://support.Microsoft.com/kb/315222

• Failed to remove snapshot vCenter

  Try to remove snapshot of vCenter and get the following message "the aready object has been deleted or has not been completely created.  The only way to remove it is to go directly to the host.  That don't work is however a question withvcenter I need to know?  Thank you!!

  Perry

  This isn't a common thing but sometimes that happens. Unless this is the case on several occasions, I worry too much on this subject. There are also some additional information on the http://kb.vmware.com/kb/1039326

• Impossible to create capture instant for VM1, error-3941 (create the snapshot has failed)

  I vSphere 4.0.0 208111 using VDR 1.1.0.707 appliance for backup of a Windows Server 2003 SP2 with VMware tools installed (including the VSS component).

  I am unable to back up a VM, but can save all other virtual machines.

  Have tried to re - install VMware tools, ensuring Windows VSS patches are up to date.

  I can do a ntbackup to system within the virtual machine with success status.

  Impossible to find someone else suffer the same error with-3491, create the snapshot has failed.

  Any ideas?

  Paul

  To simulate a VDR initiated snapshot, try a manual snapshot of the virtual machine and see if it passes or fails.  If it fails, then that explains the error 3941.  Be sure to uncheck the memory status and check the comments of quiesce file system option during an attempt of the manual snapshot because it will mimic the snapshot operation that initiates the VDR.