dictionary problem on Linux, but not on Windows host?

[GeroldGruber]

Hi,

I have one VM Worktation (6.5.1, 64bit) on (debian) Linux, another on Vista64.

When I try to start a team, that run the last time a few weaks ago on the same system on the same linux host under 6.5.0, I get now:

Unable to open "[path_to_vmtm]": Dictionary problem

The same effect for every single machine of the the team and the respective .vmx

Then I moved that team to the vista host, had to confirm the changed location of the single machines of the team, and everything runs fine.

Other (single) machines that had run under 6.5.0 on the linux host run, as they did before.

Any ideas what might be the problem?

Gerold

[wila]

Hi,

Open the .vmx file in a text editor and check the parameters. Sounds like it is using the wrong path/device somewhere.

For example a floppy disk on linux would be "/dev/fd0" while on windows it is the "A: " drive... Of course that won't be your issue, but it seems that one of your virtual harddisks uses a non local path ... As you talk about teams, it might be in one of the other small files (can't recall from the top of my head now which one is the team config)

--

Wil

_____________________________________________________

Visit the new VMware developers wiki at http://www.vi-toolkit.com

[GeroldGruber]

Hi Wil, thanks for replying,

but I'm quite sure this is not a matter of wrong paths.

They are definitely wrong after copying the whole team to the windows host, and vmware handles that situation gentle:

Throws messages, has disconnected devices, which can be new assigned and so on. But it starts the machines and does not complain about "dictionary problems" .

As I wrote: I can start that team after copying it to another platform/host.

So I suspect a problem in parsing the vmtm/vmx files on the 64 bit Linux host.

Best regards

Gerold

[leSasch]

Exactly the same problem here... unable to open the .vmx file on Ubuntu 64, but no problem on Vista 64 (both VMware Workstation 6.5)

[wila]

Strange, another thing that might be biting you is line endings (The CR-LF issue) but I would find it peculiar if that would throw errors.

Can you upload the vmware.log file so that we might see some more details?

--

Wil

_____________________________________________________

Visit the new VMware developers wiki at http://www.vi-toolkit.com

[Ahegazy]

i solve this issue by copy and paste vmx file in the same folder

[leSasch]

Sorry, don't know what you mean .. copy and paste in the same folder?!

[Kovax]

Hi,

make sure that snapshot descriptor file ( virtual-machine-name .vmsd) doesn't contain any non-UTF8 characters (like 'ő' or 'ű') in snapshot0.displayName value. It's strongly recommended to use English characters only.

Also check virtual-machine-name .vmx file not to contain these characters in annotation value.

I had the same problem, I cleared these non-UTF8 characters, and there's no Dictionary problem any more.

Hope this helps!

Kovax

[leSasch]

Hi,

Kovax was right - I had some german Umlauts in the description file..

Thanks!!

[jxadro]

In my case I could run the vmware removing the content of the vmsd file.