Thanks.  I submitted a ticket.  And yes, everything I was doing was as the 
admin user.


On Thursday, January 2, 2020 at 7:44:17 AM UTC-5, Alvaro Miranda Aguilera 
wrote:
>
> Hello
>
> Vagrant vmware plugin support is done by email to support @ hashicorp.com
>
> basically reinstall the utility:
>  https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
>
> are you login by this admin user and you running the commands under this 
> user?
>
> if you have issues, email support and we will assist you there
>
> thanks
> alvaro.
>
> On Thu, Jan 2, 2020 at 12:23 AM craig bowser <[email protected] 
> <javascript:>> wrote:
>
>>
>> I'm totally new to vagrant AND I'm using a utility that depends on 
>> vagrant, so there is a layer of abstraction I'm dealing with to figure out 
>> why things aren't working. 
>>
>> For context, I'm trying to install and use DetectionLab (
>> https://github.com/clong/DetectionLab) which uses Vagrant.  
>>
>> At this point, I don't know if the error is with Vagrant or with 
>> DetectionLab, so I beg your indulgence while I try to determine where the 
>> issue is.
>>
>> I have a Windows 10 laptop with 16GB RAM and VMware Workstation 15.x and 
>> everything is done under the admin account via an admin cli.
>>
>> Vagrant is installed on C: but the vagrantfile is located on E: (which 
>> has a ton of space).  
>>
>> To prep, I downloaded and installed vagrant and purchased the vmware 
>> plugin as well.  But when I ran the command to build the Detectionlab 
>> machines I got the following error:
>>
>> <snip>
>> [preflight_checks] Checking for bad packer version..
>> [preflight_checks] Checking if Vagrant is installed
>> [preflight_checks] Checking for pre-existing boxes..
>> [preflight_checks] Checking for vagrant instances..
>> Vagrant encountered an error while attempting to load the utility
>> service key file. This error can occur if the Vagrant VMware Utility
>> has not yet been installed, or if it was installed incorrectly. If
>> this error persists after running the Vagrant VMware Utility installer
>> again, please contact support at: support email for hashicorp.com
>>
>> Information about the Vagrant VMware Utility, including installation
>> instruction, can be found here:
>>
>>   https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
>>
>>   Path:  
>> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>>   Error: No such file or directory @ rb_sysopen - 
>> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>> preflight_checks : You appear to have already created at least one 
>> Vagrant instance. This script
>> does not support already created instances. Please either destroy the 
>> existing instances or follow
>> the build steps in the README to continue.
>> At E:\DetectionLab-master\build.ps1:391 char:1
>> + preflight_checks
>> + ~~~~~~~~~~~~~~~~
>>     + CategoryInfo          : NotSpecified: (:) [Write-Error], 
>> WriteErrorException
>>     + FullyQualifiedErrorId : 
>> Microsoft.PowerShell.Commands.WriteErrorException,preflight_checks
>>
>> E:\>
>>
>>
>> So I started checking vagrant to figure out if I did that part right:
>>
>>
>> E:\DetectionLab-master>vagrant -v
>> Vagrant 2.2.6
>>
>> C:\>vagrant plugin list
>> vagrant-reload (0.0.1, global)
>> vagrant-vmware-desktop (2.0.3, global)
>>
>> E:\DetectionLab-master>vagrant global-status
>> id       name   provider state  directory
>> --------------------------------------------------------------------
>> There are no active Vagrant environments on this computer! Or,
>> you haven't destroyed and recreated Vagrant environments that were
>> started with an older version of Vagrant.
>>
>> E:\DetectionLab-master>vagrant destroy
>> Vagrant encountered an error while attempting to load the utility 
>> service key file. This error can occur if the Vagrant VMware Utility
>> has not yet been installed, or if it was installed incorrectly. If
>> this error persists after running the Vagrant VMware Utility installer
>> again, please contact support at: support email for hashicorp.com
>>
>> Information about the Vagrant VMware Utility, including installation
>> instruction, can be found here:
>>
>>   https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
>>
>>   Path:  
>> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>>   Error: No such file or directory @ rb_sysopen - 
>> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>>   
>>   E:\DetectionLab-master>vagrant box list
>> There are no installed boxes! Use `vagrant box add` to add some.
>>
>> E:\DetectionLab-master>vagrant box prune
>> There are no installed boxes! Use `vagrant box add` to add some.
>>
>>
>> I uninstalled vagrant, rebooted, and re-installed Vagrant and got the 
>> exact same error.  I've googled "Vagrant encountered an error while 
>> attempting to load the utility service key file." and only got one hit and 
>> that was for a permission denied issue.  My Error is: "No such file or 
>> directory @ rb_sysopen"
>>
>> I had tried to do the DetectionLab install some months ago without 
>> purchasing the vmware plugin license, but it didn't work.  I deleted that 
>> directory when I started anew.  But it seems that Vagrant is still seeing 
>> that previous attempt?  
>>
>> So my question is this:  Is there some process I should try to clean up 
>> Vagrant or do these errors point to something with DetectionLab?
>>
>> Thanks
>>
>> Craig
>>
>> NOTE: searching on "vagrant "No such file or directory @ rb_sysopen" 
>> vagrant-utility.client.crt" yields a hit at 
>> https://github.com/hashicorp/vagrant/issues/9004, but again it was 
>> resolved by changing the unix permissions.
>>
>>
>> -- 
>> 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] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/cb8d3a7d-dc8c-46d8-91a6-15ef7f96a921%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/cb8d3a7d-dc8c-46d8-91a6-15ef7f96a921%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> Alvaro
>
>

-- 
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/155a7503-77c4-4381-9704-bf41b0fbc16a%40googlegroups.com.

Reply via email to