Export (0) Print
Expand All
Expand Minimize
0 out of 1 rated this helpful - Rate this topic

VMMS

Updated: April 7, 2009

Applies To: Windows Server 2008

This is preliminary documentation and subject to change.

The Virtual Machine Management Service (Vmms.exe)  is the service that uses WMI to perform Virtual System Management related operations in Hyper-V and the Hyper-V Manager.

Events

Event ID Source Message

2000

Microsoft-Windows-Hyper-V-VMMS

Could not register service connection point - Result code: %1 - %2.

2001

Microsoft-Windows-Hyper-V-VMMS

Could not unregister service connection point - Result code: %1 - %2.

3060

Microsoft-Windows-Hyper-V-Worker

The operation failed because the virtual machine was not initialized.

3061

Microsoft-Windows-Hyper-V-Worker

The operation failed because the virtual machine was not initialized.

3062

Microsoft-Windows-Hyper-V-Worker

Virtual Machine Worker Process initialization has timed out, and will terminate.

3063

Microsoft-Windows-Hyper-V-Worker

Virtual Machine Worker Process initialization has timed out, and will terminate.

3064

Microsoft-Windows-Hyper-V-Worker

The requested operation has failed.

3065

Microsoft-Windows-Hyper-V-Worker

The requested operation has failed.

4096

Microsoft-Windows-Hyper-V-Config

The %1 configuration %2 at '%3' is no longer accessible: %4 (%5)

4097

Microsoft-Windows-Hyper-V-Config

The %1 configuration %2 at '%3' is no longer accessible: %4 (%5)

4098

Microsoft-Windows-Hyper-V-Config

The %1 configuration %2 at '%3' is now accessible.

10000

Microsoft-Windows-Hyper-V-VMMS

Failed to create NT VIRTUAL MACHINE security identifier mappings: %1 (%2)

10001

Microsoft-Windows-Hyper-V-VMMS

Failed to create NT VIRTUAL MACHINE security identifier mappings: %1 (%2)

10010

Microsoft-Windows-Hyper-V-VMMS

The security identifier S-1-5-83 is already mapped to another domain.

10011

Microsoft-Windows-Hyper-V-VMMS

The security identifier S-1-5-83 is already mapped to another domain.

10107

Microsoft-Windows-Hyper-V-VMMS

An error occurred while identifying the Hyper-V VSS writer. Check for any corrupt or invalid configuration files and try again.

13000

Microsoft-Windows-Hyper-V-VMMS

User '%3' failed to create external configuration store at '%4': %1 (%2)

13001

Microsoft-Windows-Hyper-V-VMMS

Failed to create external configuration store at '%4': %1 (%2)

14040

Microsoft-Windows-Hyper-V-VMMS

Failed to query domain information.

14041

Microsoft-Windows-Hyper-V-VMMS

Failed to query domain information.

14050

Microsoft-Windows-Hyper-V-VMMS

Failed to register service principal name.

14051

Microsoft-Windows-Hyper-V-VMMS

Failed to register service principal name.

14060

Microsoft-Windows-Hyper-V-VMMS

Failed to locate the default configuration store.

14061

Microsoft-Windows-Hyper-V-VMMS

Failed to locate the default configuration store.

14062

Microsoft-Windows-Hyper-V-VMMS

Failed to locate the default virtual hard disk directory. Please verify that the directory exists and try again.

14063

Microsoft-Windows-Hyper-V-VMMS

Failed to locate the default virtual hard disk directory.

14074

Microsoft-Windows-Hyper-V-VMMS

Virtual machine '%1' (ID=%2) was already running when the Hyper-V Virtual Machine Management service started.

14090

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service is shutting down while some virtual machines are running. All running virtual machines will remain running with no management access.

14091

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service is being shut down while some virtual machines are running. All running virtual machines will remain running with no management access.

14092

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service is shutting down.

14093

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service is shutting down.

14094

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service started successfully.

14095

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service started successfully.

14096

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service failed to start.

14097

Microsoft-Windows-Hyper-V-VMMS

Hyper-V Virtual Machine Management service failed to start.

14100

Microsoft-Windows-Hyper-V-VMMS

Shutting down physical computer. Stopping/saving all virtual machines...

14101

Microsoft-Windows-Hyper-V-VMMS

Shutting down physical computer. Stopping/saving all virtual machines...

15010

Microsoft-Windows-Hyper-V-VMMS

Failed to create a new virtual machine.

15011

Microsoft-Windows-Hyper-V-VMMS

Failed to create a new virtual machine.

15040

Microsoft-Windows-Hyper-V-VMMS

Failed to import a virtual machine.

15041

Microsoft-Windows-Hyper-V-VMMS

Failed to import a virtual machine.

15110

Microsoft-Windows-Hyper-V-VMMS

Failed to modify service settings.

15111

Microsoft-Windows-Hyper-V-VMMS

Failed to modify service settings.

15300

Microsoft-Windows-Hyper-V-VMMS

Failed to access configuration store: %1 (%2).

15310

Microsoft-Windows-Hyper-V-VMMS

Created configuration store for '%1'.

15320

Microsoft-Windows-Hyper-V-VMMS

Failed to create configuration store for '%3': %1 (%2).

15330

Microsoft-Windows-Hyper-V-VMMS

Virtual Machine Bus (VMBus) cannot start because the physical computer's PCI chipset does not properly support Message Signaled Interrupts.

15340

Microsoft-Windows-Hyper-V-VMMS

The virtual machine bus is not running.

16000

Microsoft-Windows-Hyper-V-VMMS

The Hyper-V Virtual Machine Management service encountered an unexpected error: %1 (%2)

16001

Microsoft-Windows-Hyper-V-VMMS

An unexpected error occurred: %1 (%2)

16010

Microsoft-Windows-Hyper-V-VMMS

The operation failed.

16011

Microsoft-Windows-Hyper-V-VMMS

The operation failed.

16040

Microsoft-Windows-Hyper-V-VMMS

Cannot get information about available space for path: %3. Error: %1 (%2).

16041

Microsoft-Windows-Hyper-V-VMMS

Cannot get information about available space for path: %1.

16050

Microsoft-Windows-Hyper-V-VMMS

'%1' is about to run out of disk space on '%3'. (Virtual machine ID %2)

16051

Microsoft-Windows-Hyper-V-VMMS

'%1' is about to run out of disk space on '%3'.

16330

Microsoft-Windows-Hyper-V-VMMS

Cannot load a snapshot configuration because it is corrupt. (Snapshot ID %2)

18030

Microsoft-Windows-Hyper-V-VMMS

Import failed. Unable to create identifier while importing virtual machine under location '%3'. Error: %1 (%2)

18031

Microsoft-Windows-Hyper-V-VMMS

Import failed.

18040

Microsoft-Windows-Hyper-V-VMMS

Unable to rename file or directory from '%3' to '%4'. Error: %1 (%2)

18041

Microsoft-Windows-Hyper-V-VMMS

Unable to rename file or directory.

18050

Microsoft-Windows-Hyper-V-VMMS

Failed to stop the rename of the file or directory from '%3' to '%4'. Error: %1 (%2)

18051

Microsoft-Windows-Hyper-V-VMMS

Failed to stop the rename of the file or directory.

18060

Microsoft-Windows-Hyper-V-VMMS

Import failed. Unable to save the virtual machine under location '%3'. Error: %1 (%2)

18061

Microsoft-Windows-Hyper-V-VMMS

Import failed.

18080

Microsoft-Windows-Hyper-V-VMMS

Failed to import the virtual machine from import directory '%3'. Error: %1(%2)

18081

Microsoft-Windows-Hyper-V-VMMS

Failed to import the virtual machine from import directory '%3'.

18100

Microsoft-Windows-Hyper-V-VMMS

Failed to create export directory with the name '%5' with error '%3'(%4): %1 (%2)

18101

Microsoft-Windows-Hyper-V-VMMS

Failed to create export directory.

18110

Microsoft-Windows-Hyper-V-VMMS

Failed to copy file from '%3' to '%4': %1 (%2)

18111

Microsoft-Windows-Hyper-V-VMMS

Failed to copy file during export.

18120

Microsoft-Windows-Hyper-V-VMMS

Failed to import unknown device '%1'.

18121

Microsoft-Windows-Hyper-V-VMMS

Failed to import unknown device '%1'.

18250

Microsoft-Windows-Hyper-V-VMMS

Import completed with warnings. Please check the Admin events in the Hyper-V Virtual Machine Management service event log for more information.

18251

Microsoft-Windows-Hyper-V-VMMS

Import completed with warnings.

18300

Microsoft-Windows-Hyper-V-VMMS

Failed to delete the export directory '%1'. Please delete export directory manually.

18301

Microsoft-Windows-Hyper-V-VMMS

Failed to delete the export directory.

18310

Microsoft-Windows-Hyper-V-VMMS

Cannot export virtual machine with name '%1'. Please rename the virtual machine and try again.

18311

Microsoft-Windows-Hyper-V-VMMS

Cannot export virtual machine with name '.' or '..'. Please rename the virtual machine and try again.

18320

Microsoft-Windows-Hyper-V-VMMS

Import failed to configure network connection for network card '%1'. You must modify the connection of all affected network adapters to be able to run the virtual machine. If you imported snapshots and apply any of those snapshots after modifying the connection, you must modify the connection again to be able to run the virtual machine.

18321

Microsoft-Windows-Hyper-V-VMMS

Import failed to configure network connection for network card '%1'.

18330

Microsoft-Windows-Hyper-V-VMMS

Virtual network switch name was not found (%1). Network adapter will be disconnected from the network.

18331

Microsoft-Windows-Hyper-V-VMMS

Virtual network switch name was not found.

18340

Microsoft-Windows-Hyper-V-VMMS

Failed to create port during import for port name '%1'.

18350

Microsoft-Windows-Hyper-V-VMMS

Export failed for virtual machine '%3' with error '%1' (%2).

18351

Microsoft-Windows-Hyper-V-VMMS

Export failed for virtual machine '%3'.

18360

Microsoft-Windows-Hyper-V-VMMS

Import failed because the virtual machine configuration of '%1' is invalid.

18361

Microsoft-Windows-Hyper-V-VMMS

Import failed because the virtual machine configuration is invalid.

18370

Microsoft-Windows-Hyper-V-VMMS

Import failed. Virtual machine state was not copied for the virtual machine under '%1'.

18371

Microsoft-Windows-Hyper-V-VMMS

Import failed. Virtual machine state was not copied.

18380

Microsoft-Windows-Hyper-V-VMMS

Import failed. Required permissions are missing for directory '%1'.

18381

Microsoft-Windows-Hyper-V-VMMS

Import failed. Required permissions are missing.

Related Management Information

Services

Hyper-V

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.