error: Details: code E_INVALIDARG (0x80070057)

[Jonny64]

I have been researching and attempting to have this work half the day, so I had to come here for expert assist I haven't had a problem with VB for some time, but when I ran into this problem I did clean re-install of VirtualBox v4.3.26,
With VB GUI I built a VM 'shell' E:\VB_VM_64\test1\test1.vdi {test1.vbox} .................. host=Win7_64_pro ...... guest=no OS installed yet

vboxman is the full path to the vboxmanage executable
all files for each vm are kept in 1 folder
vmscfgdir is the path to directory that keeps vbox custom configuration data (bioses, tables etc)

"OPEN" test1c.bat

Code: Select all

set vmname=test1
set vboxman="C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"
set vmscfgdir="E:\VB_VM_64\test1\"
%vboxman% modifyvm "%1" --macaddress1 6CF0492A5E20

consistently get the following errors with VirtualBox running and VM test1 running + not running
&& same w VirtualBox not running && w or wo 'Run as Admin' on .bat [[ E:\VB_VM_64\ is shared w 'Everyone' and also R+W w 'Everyone' ]]

VBoxManage.exe: error: Argument aNameOrId is empty or an invalid pointer
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component VirtualBox, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 464 of file VBoxManageModifyVM.cpp

Code: Select all

%vboxman% startvm E:\VB_VM_32\w7ult-32-04-IE.00-000\w7ult-32-04-IE.00-000.vbox

results are as expected === w7ult-32-04-IE.00-000.vbox has been successfully started.

Code: Select all

%vboxman% list vms

results are as expected === all vm are listed INCLUDING "test1" {91d8f143-a7c7-4b2a-8210-96b3f1b80faa}

Code: Select all

%vboxman% list systemproperties

results as expected (including, but not limited to)
API version: 4_3
Minimum guest RAM size: 4 MB
Exclusive HW virtualization use: off
Default hard disk format: VDI
VRDE auth library: VBoxAuth

I searched in the forums and the only results (showing the various VBoxManage errors) were based on v 2.*

Feedback and solutions gratefully accepted,
Jon

[mpack]

The batch file looks odd. You set a symbol to contain the VM name, but the actual call to VBoxManage uses a command line parameter (%1) to contain the name. What was the intention?

In the first section you say that you consistently get several errors, but you don't give an example of what you actually typed.