DSX Desktop v1.2.3 Install Fails
Closed this issue · 9 comments
--
[2018-04-13 09:07:11:0739] [error] exec error: Error: Command failed: docker-machine start ibm-dsx
Error setting up host only network on machine start: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm ibm-dsx --nic2 hostonly --nictype2 82540EM --nicpromisc2 deny --hostonlyadapter2 VirtualBox Host-Only Ethernet Adapter #2 --cableconnected2 on failed:
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 525 of file VBoxManageModifyVM.cpp
[2018-04-13 09:07:11:0739] [error] stderr: Error setting up host only network on machine start: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm ibm-dsx --nic2 hostonly --nictype2 82540EM --nicpromisc2 deny --hostonlyadapter2 VirtualBox Host-Only Ethernet Adapter #2 --cableconnected2 on failed:
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 525 of file VBoxManageModifyVM.cpp
[2018-04-13 09:07:11:0739] [error] Had trouble starting ibm-dsx docker machine
Hi @cgoo4, thanks for reporting this issue.
Based off of this line:
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 525 of file VBoxManageModifyVM.cpp
it seems like the VM is locked, preventing any changes. We can try to remove the VM and start over.
Steps
- Open VirtualBox and verify that there is a VM named
ibm-dsx - Open a command prompt and enter
docker-machine rm -y ibm-dsx - Open VirtualBox again and the
ibm-dsxVM should be gone - Try to install DSX Desktop again
If that doesn't work, could you provide your:
- Log files (with the DSX Desktop open, in the menu: Help > Open log folder > dsx-desktop.log)
- Docker Toolbox version (open command prompt and enter
docker -v) - VirtualBox version (with VirtualBox open, in the menu: VirtualBox > About VirtualBox)
Thanks.
Jerry hi - I tried steps 1-4. I could verify ibm-dsx. After step 2, VM was gone. The install then failed. I've attached the log. Kind regards,
Docker version 18.02.0-ce, build fc4de447b5
VB version 5.2.8 r121009 (Qt5.6.2)
dsx-desktop.log
After doing these three things it installed at the second attempt:
docker-machine rm -y ibm-dsx- Disable network threat protection
- Run as administrator
The first attempt got stuck at 86%. The second worked.
I'm still unable to load the lubridate and other packages per #57. Please could you comment on that one?
Hi @cgoo4, sorry for the lack of response, we've been pretty busy preparing for this upcoming release.
Just out of curiosity, was the network protection software you disabled Symantec Endpoint Protection? Symantec was giving me issues when I was testing it on Windows 7. Unfortunately, I didn't get a chance to figure out how to make it work without disabling Symantec. Let me know if you figure something out.
I'm not sure if running as administrator contributed to the success, or if disabling the network protection was all that was needed. I'll have to test it out.
Hi Jerry - yes, it is Symantec Endpoint Protection, and unfortunately it doesn't allow itself to stay disabled (rightly really) for more than a few minutes, so it's possibly "hit and miss" as to whether it's off at the crucial point.
I see. I just tried to install v1.2.3 with Symantec enabled and it failed (albeit with a different error). Disabling Symantec allowed it to finish.
Interestingly enough, when I was testing the latest internal build, the installation completed even with Symantec enabled. I don't know what changed that fixed it, but the behavior is consistent. That said, it might be worth waiting until we release v1.2.4 (sometime this week) to see if your error goes away with that version.
Hi @cgoo4, we just released v1.2.4. Please give that a try and let me know if it works.
Thanks. Resolved with v1.2.4.
Glad to hear. :)