Error while opening the virtual machine insufficient permission to access the file

Insufficient permission to access file

I receive an error while powering on a VM:

Unable to open file «D:Virtual MachinesRed Hat Enterprise Linux 6Red Hat Enterprise Linux 6.vmdk»:

Insufficient permission to access file.

My system: Windows 7 32-bit with VMware Player. some days it works but I (edited) did services run manually? Now am getting above error. What can I do?

3 Answers 3

Same error, I had taken over the PC from a past developer and tried local Admin logon, no help.

I first tried setting ‘Full Control’ security permissions in Properties for the project and file it was complaining about, no luck.

So I went up to the parent dir of all the VM’s on the box, set ‘Everyone’ full control, and the VM opened right up.

I encountered the same issue, and neither ‘Full Control’ security permissions, nor running as admin fixed it.

It turned out the «Read-only» attribute of the file was checked and I only needed to uncheck it to fix it.

This read-only attribute tends to be set automatically when you burn the file on an optical media or when using disk imaging tools like Win32Disk Imager

You must give the VMware application «admin permissions» using your Mac’s user admin account. At first, I tried adding permission to the virtual hard drive. That does not work. It must be added to the VMware application.

1. Go to the Applications folder.
2. Go to the VMware application.
3. Right-click VMware and go to «Get Info«.
4. The Info window with «Permissions» (allowed users) for VMware will pop up.
5. Go to the bottom of the window and add a permission to list.
6. Enter your Mac password when prompted.
7. Click the + (add) button at the bottom of the window.
8. Add your username (user must be an «admin» user account) to the permissions list and set it to Read & Write.
9. Lock the permissions.
10. Reopen the VMware application.

You will find the error gone and your virtual machine will open. This worked for me after getting the «Vmware — insufficient permission» error.

Источник

Error while opening the virtual machine insufficient permission to access the file

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

The error (Insufficient permission to access file.) continues to occur, regardless of what is attempted.

• Windows 10 v1703 (with current updates)
• RAM: 32GB
• OnLine Storage: 20.5TB
• VM Client Location: Non-OS Drive
  • D:Virtual MachinesWindows 10 x64

The connection of the Hard Drive is intended to be for a specific partition which shall be shared between 2+ VM Clients.

Initial setup is failing with the above message.

Instructions used to build the accessible Hard Drive were pulled from the Workstation Pro 12 User Guide, Chapter 8; Section: Adding a Physical Disk to a Virtual Machine; Sub-Section: Prepare to Use a Physical Disk or Unused Partition, Procedure(1).

The HDD drive used is not defined as a system drive, not defined as an accessible drive by the OS, and is configured as defined in the Procedure(1) specific to Windows 10.

A multitude of attempts have been made, using the same steps as defined.

What is wrong with the approach, and why is it not working.

I have attached an image which depicts the configuration following the layout defined in the procedures used.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Have you run Workstation «As Admin» when trying to create the physical disks?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Have you run Workstation «As Admin» when trying to create the physical disks?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

«Add Disk» built using Admin profile.

Launch of Client using Admin profile.

End-state shall be Client run as standard user, though testing has not moved that far yet.

End-state intended to protect Host from current virus/malware/ransomware now proliferating around the world.

Client’s not intended to operate with confidential information, and may be created should infection occur.

Storage space needed though for MS Office Pro suite of applications, and working for client.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Yes, I’d used my Administrator profile while doing the work.

No, I did not run VMWare «As Administrator».

Took a bit for it to dawn on me what was being asked.

Conclusion: Multi-tasking doesn’t work well for me as it used to.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

On a more serious note.

I want to thank you for your time, guidance and help!

It was just the prompt I needed, and the work was completed and with the expected results (it works).

Further testing is now needed as I shall determine if the drive is accessible by my standard profile, when starting VMWare under normal log-in.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I believe you can run Workstation normally, not launch it «as admin». You will get a UAC prompt when starting that VM each time, I believe, due to the physical disk — this is expected behavior according to other posts I have read here on the forum.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Don’t know if you received my email — — —

I do want to thank you for your recommendation and support!

Sadly, though, VMWare Workstation Pro only permits access to the HDD (defined from the partition) to be accessed when VMWare is launched «Run as Administrator».

I’ve checked the authorities on the drive, in both VMWare and in Disk Management.

The security settings appear to be good, in particular for both Group authorities, and explicitly define for user profile authorities.

The authorities were setup prior to the creation of the HDD for VMWare, assigned to a full disk partition.

In this case, as long as I access the partition (Disk 1, Partition 2) under a «Run as administrator» launch, everything works great, up to and including the encryption using BitLocker.

Unfortunately, the client launch in a VMWare host session, NOT launched as «Run as administrator» fails every time with the message as shown in the subject line here.

Since the root-cause for this thread was answered, I’ll be launching a new thread, and maybe another kind member shall provide the time and guidance necessary to overcome this next step in the evolution of this effort.

Источник

Error while opening the virtual machine insufficient permission to access the file

I just did a clean install of my Mac OS X (10.6.5), and installed a fresh copy of Fusion 3.1.1. Now when I try to open any of my virtual machines (that I made a copy of before I formatted the drive, and then restored into my Documents/Virtual Machines folder) I get the error message: Unable to open file «/Volumes/VMware Fusion/Virtual Dell/Virtual Dell.vmdk»: Insufficient permission to access file.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

This is not a VMware Fusion issue. It is a Mac OS X User Permissions Issue.

Finder (menu bar) > Help > type «permissions» and select «If you can’t open a file or folder» or select «Setting permissions».

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

It looks like your VM’s .vmx has the full path for the .vmdk; that is, for example:

scsi0:0.fileName = «/Volumes/VMware Fusion/Virtual Dell/Virtual Dell.vmdk»

instead of simply (as it should be):

scsi0:0.fileName = «Virtual Dell.vmdk»

I had the same problem, when I restored a VM: so, I edited the .vmx (with TextEdit), as above, to solve the problem; the .vmx is inside the VM package (accessible with a right-click on the VM, and then «Show Package Contents»).

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

It looks like your VM’s .vmx has the full path for the .vmdk; that is, for example:

scsi0:0.fileName = «/Volumes/VMware Fusion/Virtual Dell/Virtual Dell.vmdk»

instead of simply (as it should be):

scsi0:0.fileName = «Virtual Dell.vmdk»

FYI Fully Qualified Pathnames are absolutely okay providing it exists and the user has read and write permissions along the path. I have many Virtual Machines that are using FQP’s without any issues whatsoever.

Also even if using the normal value for that parameter the error message will still show the FQP in the messages and it’s normal and expected.

The bottom line here is the OP is using a copy made under one install of Mac OS X and copied it back to a clean build and in all likelihood used a different User Account Name then what the original Virtual Machine was copied under and hence a permissions issue which is not a VMware Fusion issue and even if it was the resolution to permission issues under Mac OS X are resolved under it, not the VMware Fusion application although in some cases VMware Fusion (the ‘fusionRepairPermissionsTool’) can try to resolve permissions issues however not in all cases.

In the case of you editing the .vmx configuration file and if it did have a FQP it would fail if it didn’t exist or you didn’t have read and write permissions along the path and in either case the resolution is independent of the VMware Fusion application and is nothing more then an End User Error.

Источник

Error while opening the virtual machine insufficient permission to access the file

I installed the VMware player 4.0.1 update and now I cannot run any of my Linux guests. Get lots of permission errors, even though I have full control over the files and directories as user and administrator. So I look in the log file and find lots of error messages like the following:

The problem here is that I am running WMware Player, NOT VMware Workstation.

The «VMware Workstation» folder is empty, the config.ini file is in the «VMWare Player» folder.

Anybody know how to fix this.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Further to the above, I ran the VMware installer again to repair the installation. Then I started VMware Player and was able to start one of my linux guests, everything worked fine, then as soon as I shutdown the guest the permission errors start popping up again and I cannot start any of the linux guests.

I also noticed that the error popups have «VMware Workstation» in the title bar, not «VMware Player».

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

. then I uninstalled 4.0.1 and installed 4.0, but same thing happens, first startup of a linux guest everything works fine, then after shutting down the guest a big load of permission errors. Will try reverting to 3.1.5 next.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

So I install VMware Player 3.1.5, start up ubuntu, everything works fine, shutdown ubuntu and try to restart and get messages like this:

Error while opening the virtual machine: No permission to access this virtual machine.

Unable to lock user preference file

So this could be Windows 7 craptacular access control system, anyway I have wasted enough of my life on it. Goodbye VMware, hello VirtualBox.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I’m using VMware Workstation 8.0.0-471780 and having the exact same problem. Have you made any progress?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Cheers, Yours Udin

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Not exactly the same error message as the OP (vmware workstation unable to open file vmdk insufficient permission to access file) but since this is the first hit from Google . I found that in Windows server 2012 even though I had permissions from the ‘Administrators’ group that I had to for some reason add myself specifically to the vmdk file.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I realise this thread has been around for a long time but since I had the same problem today (trying to open VM left behind by ex-colleague) and it doesn’t seem to have been answered yet. the solution that worked for me is to take ownership of the folder and files:

1. Right click on the top-level folder containing the VM folders and files, select Properties

2. Select Security tab

3. Click on Advanced button

4. Select Owner tab

5. Click on Edit

6. Select your user name if present in the «Change owner» section, or click on Other users and groups button to enter it

7. Click on Apply and then «OK» your way out of the various dialogues

Once I’d done that it worked fine
.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

The issue is with the permissions on the folder and file. You can address it by changing the owner and group of the file to match your new user. You can get into this state when moving a vm from one user to another on the same system. When copying from one system to another this should be taken care of for you.

open the os x terminal app

cd to the folder that holds your VMware folder

sudo chown -R username:groupname vm_foldername

This will change the owner and group to the correct owner and group for your vmware folder and all it’s contents.

To find the username and group-name do the following

open the os x terminal app

The output should be something like

drwx——+ 5 username group-name 170 Mar 23 10:33 Desktop

user those the username and group-name to set them to your user and group.

You can also do this by typing

whoami — this will give you your username

groups — this will give you all the groups and the first group is the one you want to use.

Источник

В этой статье мы расскажем о возможных причинах, по которым не запускается виртуальная машина VMware Workstation. Мы рассмотрим самые распространённые ошибки, а также разберём, почему они возникают и как их исправить.

Ошибка VMware Workstation and Device/Credential Guard are not compatible

При включении VMware Workstation на Windows 10 может возникнуть ошибка со следующим текстом:

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please visit http://www.vmware.com/go/turnoff_CG_DG/ for more details

Чаще всего эта ошибка возникает из-за того, что включено ПО Device Guard — оно помогает защитить систему от вредоносных файлов. Device Guard позволяет настроить список файлов, которые Windows будет считать безопасными. Если на компьютер попадут файлы, которые не входят в список, система автоматически удалит их. Работе VMware в таких случаях мешает компонент Hyper-V.

Как исправить

Чтобы исправить ошибку, отключите Hyper-V с помощью функционала «Выполнить».

Ошибка Cannot open the disk

Ещё одна распространенная ошибка при запуске виртуальной машины в VMware — Cannot open the disk. Её текст следующий:

An unexpected error was received from the ESX host while powering on VM.

На следующей строке будет указана одна из причин этой ошибки. Разберём, что означает каждая:

1) Failed to lock the file. Это значит, что процесс, который вы используете, не может открыть файл. При этом файл используется другим процессом. Что может привести к ошибке:

• при работе с ВМ вы пытаетесь запустить вторую ВМ, используя тот же VMX-файл,
• вы запустили ВМ с подключенным диском при помощи утилиты vmware-mount,
• вы добавили виртуальный диск к ВМ, которая уже используется.

2) The parent virtual disk has been modified since the child was created. Эта ошибка возникает, если повреждён снимок ВМ.

3) The destination file system does not support large files означает, что на целевом хранилище невозможно открыть файл ВМ того же размера.

4) Could not open/create change tracking file. Эта проблема может возникнуть, если файл filename-ctk.vmdk создавался ранее и не очищался перед созданием новой ВМ. Здесь filename — это название вашего файла.

5) Cannot allocate memory. Тот случай, когда в модуле VMFS не хватает места.

6) The file specified is not a virtual disk возникает в случаях, если повреждён .VMDK-файл дескриптора.

7) Insufficient permission to access file. Такая проблема может возникнуть при использовании хранилищ типа NFS. Она сообщает о том, что экспорт NFS работает неправильно, так как права на чтение и запись файла не даны либо даны некорректно.

Как исправить

Единого решения для этого типа ошибки нет. Чаще всего причина связана с локальными настройками компьютера. Рекомендации по исправлению ошибки описаны в официальной документации.

Code

Message

Recommended Action (in product)

Additional Troubleshooting Information

2600

Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged.

Review the event log and take appropriate action. Ensure that SQL Server is running.

2601

Unable to connect to the VMM database.

Ensure that the SQL Server is running and configured correctly.

2602

Database integrity is in question because of a hardware or software problem.

Contact an experienced SQL administrator whenever this error occurs. Look at Windows Event Log for troubleshooting. Run DBCC CHECKDB to determine
the extent of the damage. It is possible that the problem is in the cache only and not on the disk itself. If so, restarting SQL Server corrects the problem. Otherwise, use DBCC to repair the problem. In some cases, it may be necessary to restore the VMM database.

2603

Unable to connect to the VMM database because the database is in an inconsistent state.

Contact an experienced SQL administrator whenever this error occurs. In some cases, it may be necessary to restore the VMM database. If the
problem persists, contact Microsoft Help and Support.

2604

Database operation failed.

Ensure that the SQL Server is running and configured correctly, and try the operation again.

2605

Unable to connect to the VMM database because of a general database failure.

Ensure that the SQL Server is running and configured correctly, then try the operation again.

2606

Unable to perform the job because one or more of the selected objects are locked by another job.

To find out which job is locking the object, in the Jobs view, group by Status, and find the running or canceling job for the object. When
the job is complete, try again.

2607

The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).

Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS. For more information,
see «Some applications and APIs require access to authorization information on account objects» in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=121054.

2801

Operation timed out on the %ServerName; server.

BLANK

2802

Virtualization host is out of resources on the %ServerName; server.

BLANK

2803

Too many virtual machines started on the %ServerName; server.

BLANK

2804

The virtual machine must be running for this operation to take place on the %ServerName; server.

BLANK

2805

Could not find the specified virtual machine on the %ServerName; server.

BLANK

2806

A virtual machine could not be started because its resource allocation exceeds the amount of host resources available on the %ServerName;
server.

BLANK

2807

The operation could not be done because the virtualization service is shutting down on the %ServerName; server.

BLANK

2808

A script is already attached to this event on the %ServerName; server.

BLANK

2809

Preference was not found on the %ServerName; server.

BLANK

2810

Illegal preference value was specified on the %ServerName; server.

BLANK

2811

Preference cannot be changed for a running or saved virtual machine on the %ServerName; server.

BLANK

2812

Preference change was successful but will not take effect until the next time the virtual machine is started on the %ServerName; server.

BLANK

2813

The activation dictionary could not be loaded. This can be caused by a corrupted or missing saved state file.

BLANK

2814

The virtual machine’s saved state is not compatible with this version of Virtualization Service on the %ServerName; server.

BLANK

2815

The virtual machine’s saved state could not be accessed because the user has insufficient access rights on the %ServerName; server.

BLANK

2816

A virtual machine name was not specified on the %ServerName; server.

BLANK

2817

The name of the virtual machine is too long. The length of the name cannot be more than 256 characters.

BLANK

2818

The virtual machine name contains a character that is not allowed (*?:<>/|»).

Specify a valid virtual machine name.

2819

A virtual machine with this name already exists on the %ServerName; server.

BLANK

2820

Operation cannot be performed on a running virtual machine on the %ServerName; server.

BLANK

2821

Attempt to restore a virtual machine with no saved state on the %ServerName; server.

BLANK

2822

The drive specified on the %ServerName; host server on the %ServerName; server is not valid.

BLANK

2823

Attempt to attach a drive to a bus location that is already in use on the %ServerName; server.

BLANK

2824

Additions are not installed in this virtual machine, or the virtual machine has never been started on the %ServerName; server.

BLANK

2825

Additions feature is not available; either Additions are not installed or the feature has been disabled on the %ServerName; server.

BLANK

2826

The specified folder is not being shared by the Additions on the %ServerName; server.

BLANK

2827

Cannot execute a command in the guest because the virtual machine is paused on the %ServerName; server.

BLANK

2828

Attempt to unmount the media present in virtual machine DVD drive failed on the %ServerName; server.

BLANK

2829

Could not capture floppy drive image on the %ServerName; server.

BLANK

2830

Could not capture host floppy drive on the %ServerName; server.

BLANK

2831

Could not capture floppy drive image on the %ServerName; server.

BLANK

2832

The differencing drive parent path on the %ServerName; server is not valid.

BLANK

2833

Attempt to create a file larger than what the host volume supports on the %ServerName; server.

BLANK

2834

The file cannot be read-only on the %ServerName; server.

BLANK

2835

The hard drive image type cannot be used for this operation on the %ServerName; server.

BLANK

2836

The hard drive image could not be opened on the %ServerName; host server. Ensure that the file still exists and is not in use by any other
applications.

BLANK

2837

The host drive linked to by this virtual hard disk image cannot be found on the %ServerName; server. Ensure that the host drive for this virtual
hard disk image still exists.

BLANK

2838

An unknown error occurred attempting to access a virtual hard disk image %FileName; on the %ServerName; server.

Ensure the file %FileName; is actually a virtual hard disk image.

2839

The virtual hard disk image %FileName; is not valid on the %ServerName; server.

Ensure that the file has the «.vhd» virtual hard disk image extension and that the file is actually a virtual hard disk image. If you are
attaching it to an IDE bus, the maximum disk size is 127GB.

2840

A virtual hard disk image size cannot be larger than 2,088,960 MB. A FAT16 virtual hard disk image size cannot be greater than 2,000 MB on
the %ServerName; server.

BLANK

2841

An unformatted virtual hard disk image size must be at least 3 MB. A FAT16 virtual hard disk image size must be at least 3 MB. A FAT32 virtual
hard disk image size must be at least 514 MB on the %ServerName; server.

BLANK

2842

A differencing drive must be linked to the parent it was created with. If the parent virtual hard disk image was replaced, it could lead to
the child pointing at the wrong virtual hard disk image.

BLANK

2843

Host Ethernet adapter does not exist on the %ServerName; server.

BLANK

2844

A duplicate virtual network name was specified on the %ServerName; server.

BLANK

2845

A virtual network with the given ID could not be found on the %ServerName; server. This virtual network might be required as part of another
object.

Ensure that the virtual network has not been removed or deleted, and then try the operation again.

2846

A virtual NIC Ethernet address cannot be set if the NIC has a dynamic Ethernet address on the %ServerName; server. To set the Ethernet address,
first set the Ethernet dynamic address property to false.

BLANK

2847

The IP address string is not formed correctly on the %ServerName; server. A properly formed IP address follows the pattern «X.X.X.X», where
0 <= X <= 255.

BLANK

2848

The IP address string must be a class A, class B, or class C address on the %ServerName; server.

BLANK

2849

The network mask is not valid for the class of network address on the %ServerName; server.

BLANK

2850

The starting IP address is not in a valid range on the %ServerName; server.

BLANK

2851

The ending IP address is not in a valid range on the %ServerName; server.

BLANK

2852

The starting IP address must be less than the ending IP address on the %ServerName; server.

BLANK

2853

The Ethernet address for a network interface can either be generated dynamically by virtual server or can be set to a static address by the
user. This function cannot be called when the address is set to be generated dynamically.

BLANK

2854

Access to the requested drive failed because the drive is already in use on the %ServerName; server.

BLANK

2855

The media that is currently captured by this drive does not match the type that is required for the requested operation on the %ServerName;
server.

BLANK

2856

No license is available on the %ServerName; server.

BLANK

2857

The license installed on the %ServerName; host server is not valid.

BLANK

2858

The license key on the %ServerName; host server is not valid.

BLANK

2859

The license value on the %ServerName; host server is not valid.

BLANK

2860

Current limit on active virtual machines has been reached on the %ServerName; server.

BLANK

2861

Current limit on host memory has been reached on the %ServerName; server.

BLANK

2862

Current limit on virtual machine memory has been reached on the %ServerName; server.

BLANK

2863

Attempt to invoke trial license routines on a license that is not a trial license on the %ServerName; server.

BLANK

2864

The trial license installed either has not yet started or is already finished on the %ServerName; server.

BLANK

2865

The mouse device has not been powered up in the guest on the %ServerName; server.

BLANK

2866

The mouse device is currently set to use absolute mouse coordinates on the %ServerName; server.

BLANK

2867

The mouse device is currently set to use relative mouse coordinates on the %ServerName; server.

BLANK

2868

Failed to set or release exclusive mode as requested on the %ServerName; server. This could be because the virtual machine is no longer running,
or because another process has already acquired exclusive mode on the virtual machine’s keyboard device.

BLANK

2869

Failed to find the video device for a virtual machine on the %ServerName; server.

BLANK

2870

An attempt was made to add a duplicate user or group to a security object on the %ServerName; server.

BLANK

2871

The value provided for the MAC address is not valid or is an incorrectly formatted address for the VM %VMName; on the %ServerName; server.

Enter a valid unicast MAC address in the format xx-xx-xx-xx-xx-xx.

2890

VMM cannot complete the Virtual Server operation on the %ServerName; server.

Check the Windows Event Log on the %ServerName; server to determine the cause of the error and make corrections. Then try the operation again.

2891

VMM cannot complete the Virtual Server operation on the %ServerName; server because of the error: %VMAsyncTaskErrorMessage;

Resolve the issue in Virtual Server and then try the operation again.

2900

An internal error has occurred.

Restart the agent on the machine %ServerName;, and then try the operation again.

2901

The operation did not complete successfully because of a parameter or call sequence that is not valid.

Ensure that the parameters are valid, and then try the operation again.

2902

There is not enough space on the disk to create %FileName; on the %ServerName; server.

Create additional disk space on the volume containing %FileName;, and then try the operation again.

2903

VMM could not locate the specified file %FileName; on the %ServerName; server. This file might be required as part of another object.

Ensure that you have specified a valid path parameter, and that all necessary files are present. Try the operation again.

2904

VMM could not find the specified path %FileName; on the %ServerName; server.

Ensure that you have specified a valid file name parameter, and then try the operation again.

2905

The file name, folder name, or volume label syntax %FileName; is incorrect on the %ServerName; server.

Ensure that the path name does not contain the characters ( / : * ? » < > | ), and then try the operation again.

2906

The specified path %FileName; is not valid on the %ServerName; server.

Ensure that you have specified a valid path, and then try the operation again.

2907

The file name of file %FileName; exceeds the maximum path length of 260 characters on %ServerName;.

Specify a valid path, and then try the operation again.

2908

The file %FileName; cannot be accessed because it is in use by another process on the %ServerName; server.

Wait until the other process is completed, and then try the operation again.

2909

VMM cannot create the file %FileName; because the file name already exists on the %ServerName; server.

Specify a unique file name, and then try the operation again.

2910

VMM does not have appropriate permissions to access the resource %FileName; on the %ServerName; server.

Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

2911

Insufficient resources are available to complete this operation on the %ServerName; server.

Ensure that the virtual machine host has sufficient memory and disk space to perform this action. Try the operation again.

2912

An internal error has occurred trying to contact an agent on the %ServerName; server.

Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

2913

A generic Virtual Server exception has occurred on the %ServerName; server.

Try the operation again.

2914

The connection to the %ServerName; server cannot be established.

Ensure the server is up and running along with the virtualization service.

2915

The WS-Management service cannot process the request. Object not found on the %ServerName; server.

Ensure that the agent is installed and running. If the error persists, reboot %ServerName; and then try the operation again.

2916

VMM is unable to complete the request. The connection to the agent %ServerName; was lost.

Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error
persists, reboot %ServerName; and then try the operation again.

2917

Virtual Machine Manager cannot process the request because an error occurred while authenticating %ServerName;. Possible causes are:n1) The
specified user name or password are not valid.n2) The Service Principal Name (SPN) for the remote computer name and port does not exist.n3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.

Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the
domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for %ServerName; by using
setspn.exe available from http://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make %ServerName; a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.

2918

The folder name %FileName; is not valid on the %ServerName; server.

Ensure that %FileName; is a valid folder name, and then try the operation again.

2919

The destination file %FileName; already exists or the destination device is not ready on the %ServerName; server.

Ensure that you have specified a valid path, delete the file if it exists, and then try the operation again.

2920

An I/O error occurred while opening the file %FileName; on the %ServerName; server.

Ensure that you have specified a valid path, delete the file if it exists, and then try the operation again.

2921

VMM cannot complete the operation on the file %FileName; on the %ServerName; server. One of the following system errors occurred: a file is
read-only, the specified path is a directory, or Virtual Machine Manager does not have the required permissions.

Ensure that the path is valid and VMM has the appropriate rights to perform this action.

2922

VMM is unable to create a temporary file on the %ServerName; server. A unique temporary file name is not available.

Ensure that the system has enough resources and the appropriate rights to proceed, and then try the operation again.

2923

A malformed response was received while trying to contact the VMM agent on %ServerName;.

1) Ensure the VMM agent is installed and that the VMMAgent service is running.n2) If the VMMAgent service is running, restart the service,
and then verify that WS-Management is installed correctly and that the WinRM service is running.n3) Check the manufacturers’ Web sites to ensure that you have the latest drivers for your network adapters and other devices.

2924

Unable to complete the request. Operation on the %ServerName; server timed out.

Try the operation again.

2925

The device used to access the specified path %FileName; is not ready on the %ServerName; server.

Insert the appropriate media into the available device or specify a different path, and then try the operation again.

2926

Logon failure. Unknown user name or bad password on the %ServerName; server.

Set a valid username and password and try the operation again.

2927

A Hardware Management error has occurred trying to contact server %ServerName;.

Check that WinRM is installed and running on server %ServerName;. For more information use the command «winrm helpmsg hresult».

2928

The specified logon credentials are not valid on the %ServerName; server.

Set a valid domain username and password and try the operation again.

2929

VMM could not resolve the specified file %FileName; on the %ServerName; server.

Ensure that you have specified a valid file name, then try the operation again.

2930

The network path %FileName; was not found on the %ServerName; server.

Ensure that the share name provided is valid and then try the operation again.

2940

VMM is unable to complete the requested file transfer. The connection to the HTTP server %BITSServerName; could not be established.

Ensure that the HTTP service and/or the agent on the machine %BITSServerName; are installed and running and that a firewall is not blocking
HTTPS traffic.

2941

VMM is unable to complete the request. The connection to the agent on machine %ServerName; has been lost.

Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic.

2942

VMM is unable to complete the requested file transfer. The HTTP server %BITSServerName; returned access denied.

Ensure that the HTTP service and/or the agent on the machine %BITSServerName; are installed and running.

2943

VMM is unable to complete the requested operation because there are no logon servers available.

Ensure that the domain controller is up and running and that you have access to it.

2944

VMM is unable to complete the requested operation because the server name %ServerName; could not be resolved.

Try the operation again. If the problem persists, contact your network administrator.

2945

Unable to connect to the Virtual Server service on the server %ServerName;.

Ensure that the Virtual Server service and the Virtual Machine Manager Agent are installed and running on the server %ServerName;.

2946

A malformed response was received trying to contact server %ServerName; (%DetailedErrorMessage;).

Ensure that the communication is set up properly.

2947

Virtual Machine Manager cannot complete the VirtualCenter action on the server %ServerName; because of the following error: %DetailedErrorMessage;.

Resolve the issue and then try the operation again.

2948

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;
(%Value;).

This error occurs when the key, name, or identifier for the element that you are trying to add already exists for an element in the collection.
Provide unique values for those parameters and then try the operation again.

2949

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;
(%Value;).

This error occurs when a function contains an invalid argument. Resolve the issue and then try the operation again.

2950

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;.

This error occurs when a referenced component of a managed object — either a data object type (such as a role or permission) or a primitive
(such as a string) — cannot be found. Resolve the issue and then try the operation again.

2951

Virtual Machine Manager cannot complete the VirtualCenter action on server %ServerName; because of the following error: %DetailedErrorMessage;
(%Value;).

This error occurs when an operation is denied access because of insufficient privileges on a managed object. Resolve the issue and then try
the operation again.

2952

%FileName; cannot be created on server %ServerName; because the target volume is not set to «Available for placement.»

Specify a different target volume or set the target volume to «Available for placement» and then try the operation again.

2953

VMware ESX Server host %ServerName; is not in the same VirtualCenter as host %VMHostName;.

Specify a different server and then try the operation again.

2971

The virtual machine %VMName; can not be started because the run under credentials are not valid on the %ServerName; server.

Set the run under credentials for %VMName; to valid credentials and try the operation again.

2972

The credentials supplied for the virtual machine to run under are not valid.

Enter a valid account and password, and then try the operation again.