Dictionary problem vmware как исправить

Hi,

The VM folder in the support bundle where info about your guest is supposed to be is completely empty. Not sure what happened there.

So I’m afraid the support bundle doesn’t help, as far as I’m concerned you can remove that file again (use the “edit” option on the forum)

The next step I would normally do is to verify if the virtual disks that are referred to in the vmx actually exists.

In your case there should be a:

Windows 7 x64-000013.vmdk

and

Windows 7 x64-0-000013.vmdk

and

Windows 7 x64-1-000012.vmdk

if ALL disks existed before you created your snapshots then it is a bit strange that one disk has a different suffix number, but without seeing the full snapshot chain that is difficult to say.

You can test the snapshots chains for the above files by running them via vmware-vdiskmanager while in the Virtual Machine folder.

Eg;

C:Program Files (x86)VMwareVMware Workstation>vmware-vdiskmanager -e "Windows 7 x64-000013.vmdk"

Repeat that for the other 2 files.

Then you can also verify your disks using the -R option.

See the following link for a printout of the help (or run the command without options)

http://www.vi-toolkit.com/wiki/index.php/Vmware-vdiskmanager

IMPORTANT: Before you apply ANY more rescue, troubleshooting steps do make a FULL copy of the virtual machine folder to another -preferably external- disk.

That way even if you end up making a mistake your data will still be there, albeit in another disk.

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

I’m pretty new to using vmware virtualization (been a virtualbox user) so I’m hoping you guys can help me out. I recently got an external usb disk containing a vm for a client, downloaded vmplayer, set it up with “Open a Virtual Machine”, ran it, easy as pie.

After working with it a bit this morning, I shut the VM down and now trying to start it back up again I get this:
Failed to open virtual machine: Dictionary problem.

I tried removing the vm from my library, now it happens whenever I try to add it back in. In the meantime, I can still access other virtual machines so it seems like the problem might be with the virtual disk.

So two questions:

  • This is obviously not a very helpful error message. Where can I go to get more information? My Application EventLog doesn’t contain anything from VMWare.
  • What steps can I take to fix the problem?

Edit: A couple more pieces of information.

  • I did not take any snapshots. I don’t think VM Player even has that ability.
  • I have a zip file of (what I assume) is the state of the VM when it was sent to me. I cannot unzip it as it is huge and simply requires more HD space than I have available but I did extract the vmx file and examine it. Other than the UUIDs and the fact that mine reads cleanShutdown = "FALSE" they are identical.
  • The log contains the following lines

    Jun 23 10:11:18.080: vmx| SNAPSHOT: SnapshotConfigInfoRead: Unable to load dict from ‘E:….MachineName.vmsd’.

    Jun 23 10:11:18.080: vmx| SNAPSHOT: SnapshotConfigInfoRead failed for file ‘E:….MachineName.vmx’: Dictionary problem (6)

    Jun 23 10:11:18.082: vmx| SNAPSHOT: Snapshot_TimeStampTiers failed: Dictionary problem (6)

asked Jun 23, 2011 at 19:23

George Mauer's user avatar

George MauerGeorge Mauer

4793 gold badges7 silver badges13 bronze badges

Have seen this in relation to snapshots creatiung this error. There are several threads in VMware community sites. VMware community
Another thread here speaks to it as well VM Discussions

answered Jun 23, 2011 at 20:10

Dave M's user avatar

Dave MDave M

4,51421 gold badges30 silver badges30 bronze badges

3

For the record I got this fixed by taking backups of my caches directory, vmsd, vmxf, vmx, nvram files and copying them over the files that I had. I guess some of them had been corrupted.

answered Jun 24, 2011 at 15:59

George Mauer's user avatar

George MauerGeorge Mauer

4793 gold badges7 silver badges13 bronze badges

Try at first load your virtual machine without any physical discs.

Then try to add it in VM->Settings->Add->Hard Disk->SCSI->Use physical disk->PhysicalDrive (your number, take a look at Disk management).

I had same problem, and solved it by adding physical disks on a loaded VM.

Citizen's user avatar

Citizen

1,1031 gold badge10 silver badges19 bronze badges

answered Jan 7, 2020 at 17:33

Jaime Asm's user avatar

Не получается установить. Пожалуйста, посмотрите, где ошибка

user@user-virtual-machine:/tmp/vmware-tools-distrib$ sudo ./vmware-install.pl -dThe installer has detected an existing installation of open-vm-tools packages
on this system and will not attempt to remove and replace these user-space
applications. It is recommended to use the open-vm-tools packages provided by
the operating system. If you do not want to use the existing installation of
open-vm-tools packages and use VMware Tools, you must uninstall the
open-vm-tools packages and re-run this installer.
The packages that need to be removed are:
open-vm-tools
Packages must be removed with the --purge option.
The installer will next check if there are any missing kernel drivers. Type yes
if you want to do this, otherwise type no [yes]
INPUT: [yes]  default

A previous installation of VMware Tools has been detected.

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

You have a version of VMware Tools installed.  Continuing this install will
first uninstall the currently installed version.  Do you wish to continue?
(yes/no) [yes]
INPUT: [yes]  default

Uninstalling the tar installation of VMware Tools.

Stopping services for VMware Tools

Stopping VMware Tools services in the virtual machine:
   VMware User Agent (vmware-user):                                    done
   Unmounting HGFS shares:                                             done
   Guest filesystem driver:                                            done

Stopping Thinprint services in the virtual machine:
   Stopping Virtual Printing daemon:                                   done

depmod: WARNING: could not open /lib/modules/4.15.0-62-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-62-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-20-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-20-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-34-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-34-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-36-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-36-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-30-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-30-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-58-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-58-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-33-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-33-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-60-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-60-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-55-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-55-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-32-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-32-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-29-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-29-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-38-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-38-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-23-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-23-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-22-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-22-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-24-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-24-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-64-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-64-generic/modules.builtin: No such file or directory
The removal of VMware Tools 10.2.0 build-7259539 for Linux completed
successfully.

Installing VMware Tools.

In which directory do you want to install the binary files?
[/usr/bin]
INPUT: [/usr/bin]  default

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc]
INPUT: [/etc]  default

What is the directory that contains the init scripts?
[/etc/init.d]
INPUT: [/etc/init.d]  default

In which directory do you want to install the daemon files?
[/usr/sbin]
INPUT: [/usr/sbin]  default

In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
INPUT: [/usr/lib/vmware-tools]  default

The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
INPUT: [yes]  default

In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
INPUT: [/usr/share/doc/vmware-tools]  default

The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
INPUT: [yes]  default

The installation of VMware Tools 10.3.10 build-13959562 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
INPUT: [yes]  default

You have chosen to install VMware Tools on top of an open-vm-tools package. 
You will now be given the option to replace some commands provided by
open-vm-tools.  Please note that if you replace any commands at this time and
later remove VMware Tools, it may be necessary to re-install the open-vm-tools.

WARNING:  It appears your system is missing the required /usr/bin/vmhgfs-fuse

Initializing...

Making sure services for VMware Tools are stopped.

Stopping VMware Tools services in the virtual machine:
   VMware User Agent (vmware-user):                                    done
   Unmounting HGFS shares:                                             done
   Guest filesystem driver:                                            done

The module vmci has already been installed on this system by another installer
or package and will not be modified by this installer.

The module vsock has already been installed on this system by another installer
or package and will not be modified by this installer.

The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.

The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.

The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer.

The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment.  Do you wish
to enable this feature? [yes]
INPUT: [yes]  default

The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)

Skipping configuring automatic kernel modules as no drivers were installed by
this installer.

Skipping rebuilding initrd boot image for kernel as no drivers to be included
in boot image were installed by this installer.

The configuration of VMware Tools 10.3.10 build-13959562 for Linux for this
running kernel completed successfully.

Found VMware Tools CDROM mounted at /media/user/VMware Tools. Ejecting device
/dev/sr0 ...
Found VMware Tools CDROM mounted at /mnt/cdrom. Ejecting device /dev/sr0 ...
Enjoy,

--the VMware team

There are a lot of VMware errors 
out there. Way too many, right?

You as a sysadmin know that for sure – authorization service not running, internal errors, dictionary problems.
Your VMware setup sometimes drives you crazy.

Here’s a list of the most common errors around VMware and the proven solution to them:

  1. VMware authorization service is not running (1007131)
  2. Error while powering on: Internal error
  3. VMware dictionary problem
  4. VMware Workstation Unrecoverable Error: (vcpu-0)
  5. VMware error intel vt x disabled
  6. VMware esx problem hyperthreading unmitigated
  7. VMware mks error

And you’ll find the solution to get rid of ALL VMware errors – forever: Test PRTG and get started within minutes!

 1. VMware error: 

“VMware authorization service is not running (1007131)”

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors, i.e. by checking if vmware authorization service is running or not and alerts you immediately.

Since PRTG is a certified VMware partner tool, you get deep insights into your VMware setup, devices, bandwidth, traffic and applications.

Learn more about VMware Monitoring

 2. VMware error: 

“Error while powering on: Internal error”

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors. Since PRTG is a certified VMware partner tool, you get deep insights into your VMware set-up, devices, bandwidth, traffic and applications.

Information about VMware Monitoring

 3. VMware error: 

“VMware dictionary problem”

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors. Since PRTG is a certified VMware partner tool, you get deep insights into your VMware set-up, devices, bandwidth, traffic, applications, and of course files.

Information about VMware Monitoring

 4. VMware error: 

“VMware Workstation Unrecoverable Error: (vcpu-0)”

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors. Since PRTG is a certified VMware partner tool, you get deep insights into your VMware set-up, devices, bandwidth, traffic, and applications.

Information about VMware Monitoring

 5. VMware error: 

“VMware error intel vt x disabled”

time blueQuick Fix

This is the quick fix for VMware error “intel vt x disabled”.

  1. You will have to restart the computer and press either F10 or DEL to go to BIOS settings.
  2. Under Security -> System Security you will find the option to enable VT.
  3. Also can you tell the model of Computer so we can see model specific options.

Source: https://communities.vmware.com/thread/464586

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors. Since PRTG is a certified VMware partner tool, you get deep insights into your VMware set-up, devices, bandwidth, traffic, and applications.

Information about VMware Monitoring

6. VMware error: 

“VMware esx problem hyperthreading unmitigated”

time blueQuick Fix

he ESXi patches available in VMSA-2018-0020 to mitigate CVE-2018-3646 introduced a new notification to indicate remediation status of the ‘L1 Terminal Fault’ (L1TF – VMM) vulnerability.

When ESXi is updated before vCenter, either manually or through vSphere Update Manager, the internal reference for the message from the host instead of the intended one is displayed.

Best solution

https://kb.vmware.com/s/article/57374

https://communities.vmware.com/thread/594807

 Proper fix

Use PRTG’s VMware monitoring by using dedicated VMware sensors. Since PRTG is a certified VMware partner tool, you get deep insights into your VMware set-up, devices, bandwidth, traffic, applications, and of course files.

Additionally, PRTG offers a patch und update monitoring to keep you informed about current updates and your systems and applications.

Information about VMware Monitoring

Information about Update/Patch Monitoring

7. VMware error: 

“VMware mks error”

Choose your solution: Bugfix or replacement

prtg logo white

With PRTG you’ll never have to deal with
VMware errors again. Ever.

Trusted by 500,000 users and recognized
by industry analysts as a leader

trustpilot preview

“Fantastic network and infrastructure monitoring solution that is easy to deploy and easier still to use. Simply the best available.”

Read more reviews

gartner preview

“Software is absolutely perfect, Support is superior. Meets all needs and requirements, this is a must have solution if you are needing any form of monitoring.”

Read more reviews

pcmag preview

“The tool excels at its primary focus of being a unified infrastructure management and network monitoring service.”

Read more reviews

  • Home
  • Forum
  • Software
  • General & Business Software
  • [RESOLVED] VMWare Version 5.5.2

  1. May 28th, 2008, 03:56 AM


    #1

    Resolved [RESOLVED] VMWare Version 5.5.2

    I am currently building a test environment with VMWare to do software tests. I have created in one Environment 50 snapshots. Well when I went to save the 51 snapshot the VMWare hung up and crashed. I reset my system and started VMWare again and tried to open the main snapshot from my snapshot tree and I recieved the following error:

    Could not open virtual Machine: “Directory” Dictionary problem.

    I tried to start from other snapshots and I am recieving the same error message every time. I know it has nothing to do with the VMWare host because other environments I have built work fine.

    I would be very thankful to anyone that could give me some support in this area.

    I thank you wizards in advance
    Dave


  2. May 28th, 2008, 01:31 PM


    #2

    Welcome to VirtualDr

    Did you look on VMWare’s web site to see if there’s a solution?

    If you’re happy and you know it……it’s your meds.


  3. May 29th, 2008, 05:06 AM


    #3

    Resolved Thanks

    Hi Steve,

    That was the first thing I did. But they do not have that much information in regards to technical libraries. I found the dictionary and when it crashed it wrote a line of code that put a start number that wasnt correct. The library told it that it should start from 14 but the snapshot 43 was the starting point in the main image. I erased the line of code and the thing worked perfectly.

    For further knowledge I will paste the problem with the solution so all you wizards will have a bit of good info.

    Problem:
    Dictionary Failure ( with only the last bit of code out of the .vsmd data )

    snapshot43.uid = “17”
    snapshot43.filename = “win2000Pro-Snapshot17.vmsn”
    snapshot43.parent = “15”
    snapshot43.displayName = “User Rights”
    snapshot43.description = “User Name |22Test1|22, Password |22test|22”
    snapshot43.type = “1”
    snapshot43.createTimeHigh = “282146”
    snapshot43.createTimeLow = “-1713632512”
    snapshot43.numDisks = “1”
    snapshot43.disk0.fileName = “Windows 2000 Professional-000017.vmdk”
    snapshot43.disk0.node = “scsi0:0”

    snapshot14.createTimeHigh = “282163”

    Last line of code said snapshot 14 and the .vmx data had the entry 43 but when it tried to start it was getting confused because of the 14. I killed that last line and it worked perfectly.

    Thank you to all that tried to break there heads on this one.

    Have a good day.

    Dave


Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
  • BB code is On
  • Smilies are On
  • [IMG] code is On
  • [VIDEO] code is On
  • HTML code is Off

Forum Rules

Добавить комментарий