Vmware player file access error



[FIX] У вас нет прав доступа к этому файлу. Ошибка VMware.

[FIX] У вас нет прав доступа к этому файлу. Ошибка VMware.

VMware Workstation Player — популярное программное обеспечение для виртуализации, которое позволяет вам запускать одну виртуальную машину на вашем ПК с Windows. Однако иногда при работе с программным обеспечением для виртуализации вы можете столкнуться с ошибкой «У вас нет прав доступа к этому файлу VMware». Это не распространенная ошибка, поэтому любая информация о том, как устранить эту ошибку, пугает.

Если вас также беспокоит эта ошибка, вот несколько советов по устранению неполадок, которые помогут вам исправить. У вас нет прав доступа к этому файлу VMware в Windows Computers.

Как исправить у вас нет прав доступа к этому файлу VMware

1. Проверьте одновременное выполнение заданий

  1. Одна из причин этой ошибки связана с одновременным выполнением нескольких заданий. Проверьте, пытаются ли несколько заданий получить прямой или косвенный доступ к одним и тем же дисковым ресурсам.
  2. Если ограничение в VMWare разрешает открывать дисковые ресурсы только одним процессом за раз, многократные попытки задания вызовут проблемы с процессом.
  3. В качестве решения убедитесь, что задания не выполняются одновременно или слишком близко к каждому, где может произойти перекрытие.

2. Проверьте учетную запись пользователя для разрешения

  1. У вас нет прав доступа к этому файлу. Ошибка VMware также может возникнуть, если у учетной записи пользователя, выбранной для резервного копирования, нет всех необходимых разрешений.
  2. Проверьте документы VMware для получения списка всех необходимых необходимых разрешений.
  3. Убедитесь, что вы выбрали корневую учетную запись для виртуальных машин под хостом ESX в списке разделов резервного копирования.
  4. Если виртуальные машины выбираются из-под VCenter, вы можете вместо этого выбрать учетную запись администратора домена.

Другие решения, которые стоит попробовать

  1. Убедитесь, что коммуникационный сервер видит диски SAN и не помечен как автономный.
  2. Если возможно, попытайтесь пропинговать хост ESX по имени с медиа-сервера.
  3. Убедитесь, что медиасервер правильно распознает имя и UP хоста ESX.
  4. Если проблема не устранена, попробуйте создать новую учетную запись пользователя с правами администратора в VCenter или ESX Host. Затем повторите попытку резервного копирования, используя новую учетную запись администратора.
  5. Если на виртуальной машине установлено несколько поставщиков VSS, попробуйте удалить поставщик снимков VMWare.
  6. Если проблемы связаны с VMWare vSphere Cluster с 3 узлами, вам может потребоваться добавить соответствующую запись DNS для проблемного хоста.
  7. Если Backup Exec не может получить доступ к хостам ESX с помощью метода, предоставленного сервером VCenter, исправьте проблемы DNS, вызвавшие неудачное разрешение имен. Это должно помочь вам решить. У вас нет прав доступа к этому файлу. Ошибка VMware.

Вывод

У вас нет прав доступа к этому файлу. Обычно ошибка VMware вызвана незначительными проблемами, связанными с разрешением. Это также может произойти, если имя файла имеет синтаксис или цифры. Попробуйте выполнить действия, описанные в этой статье, чтобы увидеть, поможет ли это.

СВЯЗАННЫЕ ИСТОРИИ, КОТОРЫЕ ВЫ МОЖЕТЕ КАК:

Источник

Vmware player file access error

  • 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.

Читайте также:  Soap request error exception

  • Windows 10 v1703 (with current updates)
  • RAM: 32GB
  • OnLine Storage: 20.5TB
  • VM Client Location: Non-OS Drive
    • D:\Virtual Machines\Windows 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.

Источник

Vmware player file access error

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.

Источник

Оцените статью
toolgir.ru
Adblock
detector