Did you get any solution to this issue? I'm having similar issue.
On Friday, November 10, 2017 at 12:11:44 AM UTC+5:30, Eric Beach wrote:
>
> Attempting to install the plugin on a domain-joined computer with a domain
> account fails. I was able to install to the same computer running a local
> account.
>
> PS C:\> vagrant plugin install vagrant-vmware-workstation
> Installing the 'vagrant-vmware-workstation' plugin. This can take a few
> minutes...
> Fetching: vagrant-share-1.1.9.gem (100%)
> Fetching: vagrant-vmware-workstation-5.0.3.gem (100%)
> Building native extensions. This could take a while...
> Administator failed to take ownership of install directory
> Bundler, the underlying system Vagrant uses to install plugins,
> reported an error. The error is shown below. These errors are usually
> caused by misconfigured plugin installations or transient network
> issues. The error from Bundler is:
>
> ERROR: Failed to build gem native extension.
>
> current directory:
> C:/Users/xxxx/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.3/ext/vagrant-vmware-desktop
> C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r
> ./siteconf20171109-5712-114qzcn.rb extconf.rb
>
> Folder: \
> TaskName Next Run Time Status
> ======================================== ======================
> ===============
> vagrant-vmware-desktop-xxxx-xxxx N/A Ready
> A subdirectory or file
> C:\ProgramData\HashiCorp\VagrantVMware\xxxx-xxxx\bin already exists.
> A subdirectory or file
> C:\ProgramData\HashiCorp\VagrantVMware\xxxx-xxxx\UserData already exists.
> 1 file(s) copied.
> 1 file(s) moved.
> processed file: C:\ProgramData\HashiCorp\VagrantVMware\xxxx-xxxx\UserData
> Successfully processed 1 files; Failed processing 0 files
> No mapping between account names and security IDs was done.
> Successfully processed 0 files; Failed processing 0 files
> 'Administrator"' is not recognized as an internal or external command,
> operable program or batch file.
> *** extconf.rb failed ***
> Could not create Makefile due to some reason, probably lack of necessary
> libraries and/or headers. Check the mkmf.log file for more details. You
> may
> need configuration options.
>
> Provided configuration options:
> --with-opt-dir
> --without-opt-dir
> --with-opt-include
> --without-opt-include=${opt-dir}/include
> --with-opt-lib
> --without-opt-lib=${opt-dir}/lib
> --with-make-prog
> --without-make-prog
> --srcdir=.
> --curdir
> --ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE_NAME)
>
> extconf failed, exit code 1
>
> Gem files will remain installed in
> C:/Users/xxxx/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.3
> for inspection.
> Results logged to
> C:/Users/xxxx/.vagrant.d/gems/2.4.2/extensions/x64-mingw32/2.4.0/vagrant-vmware-workstation-5.0.3/gem_make.out
>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/fe0ce4db-b45c-448a-912f-1167559987bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
