VMware Communities
HaimD
Contributor
Contributor

Can't start vmware environment - "Dictionary Problem"

Hi,

I working with Workstation Host Win2008, During work the sapce on the host HD was over and the environment stopped.

Since that I fail to start the env with error : "Could not open virtual machine: ... Dictionary Problem"

I have search for a solution and I all talk about problems with vmx file but i see not problem with mine (no double lines, no junk in it)

I attach the vmx file maybe i'm missing something:

.encoding = "windows-1255"

config.version = "8"

virtualHW.version = "4"

scsi0.present = "TRUE"

memsize = "384"

ide0:0.present = "TRUE"

ide0:0.fileName = "Windows Server 2003 Enterprise Edition.vmdk-000006.REDO_a00764"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.fileName = "A:"

Ethernet0.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

displayName = "Server 6.00 MySQL"

guestOS = "winnetenterprise"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

sound.virtualDev = "es1371"

ide1:0.startConnected = "TRUE"

Ethernet0.addressType = "generated"

uuid.location = "56 4d 34 21 07 bd 01 fb-47 71 06 8d ec a2 71 75"

uuid.bios = "56 4d 34 21 07 bd 01 fb-47 71 06 8d ec a2 71 75"

ethernet0.generatedAddress = "00:0c:29:a2:71:75"

ethernet0.generatedAddressOffset = "0"

tools.syncTime = "FALSE"

undopoints.seqNum = "0"

ide0:0.mode = "persistent"

undopoint.restoreFromCheckpoint = "FALSE"

undopoint.checkpointedOnline = "TRUE"

ide0:0.redo = ""

undopoint.protected = "FALSE"

gui.restricted = "FALSE"

redoLogDir = "."

Ethernet0.connectionType = "bridged"

Ethernet0.vnet = "VMnet3"

ide0:0.deviceType = "disk"

usb.present = "TRUE"

sound.autodetect = "TRUE"

ide1:0.autodetect = "TRUE"

nvram = "Windows Server 2003 Enterprise Edition.nvram"

extendedConfigFile = "Windows Server 2003 Enterprise Edition.vmxf"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

ide0:1.present = "TRUE"

ide0:1.fileName = "Windows Server 2003 Enterprise Edition-0-000006.vmdk"

ide0:1.redo = ""

vmotion.checkpointFBSize = "16777216"

checkpoint.vmState.readOnly = "FALSE"

checkpoint.vmState = ""

Thanks!!!

Tags (1)
Reply
0 Kudos
19 Replies
a_p_
Leadership
Leadership

I'm not too familiar with the REDO stuff, however if you attach a file list (containing names, sizes, time stamps) and the latest vmware.log, I will take a look at it.

André

Reply
0 Kudos
HaimD
Contributor
Contributor

Not sure I understand list of what you reffered to but the log is attahced.

Thanks!

Haim

Reply
0 Kudos
a_p_
Leadership
Leadership

What I meant with file list is a list of the files (dir .) of the VM's folder.

What size is your 😧 drive and how much free space do you have currently?

The logs say:

Jun 16 07:44:50.710: vmx| \[msg.vmxaiomgr.retryabort.diskfull\] Operation on file "D:\Working envs\EranM\Server 6.00 MySQL - Win2003 R2 SP2 (With TimeZone and New Security Update)\Windows Server 2003 Enterprise Edition.vmdk-000006.REDO_a00764" failed (There is not enough space on the disk)

-

Jun 16 07:44:50.710: vmx| The file system where disk "D:\Working envs\EranM\Server 6.00 MySQL - Win2003 R2 SP2 (With TimeZone and New Security Update)\Windows Server 2003 Enterprise Edition.vmdk-000006.REDO_a00764" resides is full

André

Reply
0 Kudos
HaimD
Contributor
Contributor

Currently I have more than 5GB of free space.

attached is the list you requested.

I know the reason for the env to stop was the lack of space in partition D. this happens from time to time and I have more than env up on the vmware workstation, but this env is the only one affected in such way.

Haim

Reply
0 Kudos
continuum
Immortal
Immortal

Very strange - you have REDOs AND snapshots ....

Is this a very very old VM that was used on older platforms ?




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
HaimD
Contributor
Contributor

This is a copy of an old VM that might have been used on older versions of workstation.

The error comes on workstation v6.5 but i think that this env was used on also workstation v6.03.

Most sanpshots were done on the newer version.

Haim

Reply
0 Kudos
continuum
Immortal
Immortal

do you still need all those snapshots ?

i would try to consolidate the disk with vmware-vdiskmanager using commands like this ...

for the first disk:

vmware-vdiskmanager -r "Windows Server 2003 Enterprise Edition.vmdk-000006.REDO_a00764" -t 0 "newdisk1.vmdk"

and for the second one

 vmware-vdiskmanager - r "Windows Server 2003 Enterprise Edition-0-000006.vmdk" -t 0 "newdisk2.vmdk"

This may need more free disk space then you have available now - so it would be best to create the consolidated disk on another drive with more free space.

I am not sure if this will work with the first disk - REDO vmdks usually either appear along with the "nonpersistent" flag or with very old VMware versions such as GSX or Workstation 3. ... or with very clever but unusual configs like I describe in the more experimental parts of sanbarrow.com - see

http://sanbarrow.com/vmx/vmx-undoable-mode-for-vmserver.html

The last mentioned site also may be necessary to fix your dictionary problems if the vdiskmanager can not handle this.

Any way - strange case - thanks for showing it Smiley Wink




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
admin
Immortal
Immortal

None of the redo/snapshot stuff would trigger a "dictionary problem" error, which means that we weren't able to parse the .vmx file (or maybe the .vmxf file) at all.

Could you please attach the .vmx and .vmxf files? (Please upload them rather than copying-and-pasting their contents.)

Reply
0 Kudos
continuum
Immortal
Immortal

the vmx-file seems to be ok - I can load it here - after setting the disk to be not present of course




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
admin
Immortal
Immortal

The .vmx file looks okay, but you have to see the actual file to make sure it didn't get sanitized during copy/paste. (For example, you wouldn't know if the original file were saved as UTF-16.)

@HaimD: Could you additionally attach your .vmsd file and your UI log? The UI log location is shown in Help > About. Do you get this error message when you try to open the VM or only when you try to power it on? If the latter, please attach the VMX log too (the vmware.log file in the VM's directory).

Reply
0 Kudos
HaimD
Contributor
Contributor

I apologize but I can't attach any of the files you requested. this environment contains sensitive information.

If you can tell me what you plan to do with it, maybe I can try it.

Thank you for your and sorry I can't provide the files.

regarding your question, I get the error once i try to open the VM.

Thanks, Haim

Reply
0 Kudos
continuum
Immortal
Immortal

You already posted the vmx file - so if your company holds a death sentence for leaking sensitive information you are already guilty Smiley Wink

Seriously - neither the vmx nor the vmxf file contain any sensitive data - we just want to look at it to find syntax problems




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
admin
Immortal
Immortal

I apologize but I can't attach any of the files you requested. this environment contains sensitive information.

If you can tell me what you plan to do with it, maybe I can try it.

Thank you for your and sorry I can't provide the files.

If you don't want to post them publicly, you can send them to me in a private message. You're also free to examine the contents of the files first (and you probably should). But I can't help you without looking at the logs to see if there might be additional details there about the cause of the error.

Reply
0 Kudos
HaimD
Contributor
Contributor

Hi,

I apologize for the long wait, I was out of the office for a few days...

I attach the requested files...have i missed anything?

Reply
0 Kudos
HaimD
Contributor
Contributor

here is the vmx file

Reply
0 Kudos
continuum
Immortal
Immortal

you are running out of diskspace and probably that is why

Windows Server 2003 Enterprise Edition-0-000006.vmdk" : failed to open (The specified virtual disk needs repair).

first thing to do - get enough free space

then try a repair of the vmdk with vdiskmanager -R option




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
HaimD
Contributor
Contributor

Hi,

I was unable to run the vmware-vdiskmanager.

I could not find any relevant info that can assist me in the link you specified.

When running the command on the REDO i get:

Failed to convert disk: The specified virtual disk needs repair (0xe00003e86).

and on the second one:

Failed to convert disk: The called function cannot be performed on partial chains. Please open the parent virtual disk (0x500003e83).

Thanks!

Reply
0 Kudos
continuum
Immortal
Immortal

The called function cannot be performed on partial chains.

that looks like a bad vdiskmanager version.

The one that comes with WS 7.1 is broken - use the one from 7.0.1




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
HaimD
Contributor
Contributor

I'm using WS 6.5.

Reply
0 Kudos