Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
The following error is achieved on Vmware Installation when installing on an x64 Windows 7:
vmware
mcisocket64.msi failed
I don't know why... but in looking at the vmsetup.20120104134836.log within %TEMP% I noted:
20120104134909:INFO CPackageManager::GetFile: VMwareVmciSockets64.msi
20120104134909:INFO CMSIHelper::InitMsiParameters: MSI Parameters:
20120104134909:INFO CMSIHelper::InitMsiLogging: Successfully enabled logging to file C:\Users\dan\AppData\Local\Temp\vmsetup.20120104134836.vmwarevmcisockets64.msi.install.log, with mode 7967
20120104134909:INFO CInstallMSIOperation::Execute: Preparing to install VMwareVmciSockets64.msi, options: uninstall_on_rollback: 1, use_internal_ui: 0, parameters:
20120104134916:INFO CInstallMSIOperation::Execute: Finished installing msi [0]
20120104134916:INFO CBootstrapCmd::RunOperation: Operation 'InstallMSI' completed successfully with return code 65537
There is no user "dan" on my machine, so the above path would not work. I do not know why Vmware was looking for Dan... as far as I know Dan has never used my machine, and there is no reference in the registry to a "Dan".
However, creating the directory where it was trying to create the file allowed the installation to finish without an issue.
Hopefully this ends up helping someone else out as well.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Anybody else failing to open snapshots once they upgraded their VirtualBox from v5 to v6? Snapshots that were opening just fine are now failing for me with this error ...
HGCM#0: Bad auto mount point size: 0x5
[ver=3 pass=final] (VERR_SSM_DATA_UNIT_FORMAT_CHANGED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Some very old snapshots are able to open; but most new ones and ALL the ones I save now using VirtualBox 6 are failing to open. Same error above.
My host is Windows10 and the saved VMs are Ubuntu18 guests.
Disclaimer: It should not be an excepted solution as your saved state will be lost.
As I don't have any sensitive data in the saved state. I have discarded the saved state and it works fine for my case.
EDIT: in some cases it looks like if you take a snapshot using the saved state, and then discard the saved state you might be able to recover back to where your saved state was
Steps
Right Click on the OS
Select Discard Saved State... in the context menu.
Screenshot
Host OS: Windows 10, Guest OS: Ubuntu 18.04, on Virtual Box 6.0.0
I have resolved this problem by installing Oracle_VM_VirtualBox_Extension_Pack-6.0.4.vbox-extpack for my VirtualBox-6.0.4-128413-Win
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
I'm pretty sure this is a hardware issue. Just to prove my point, I loaded up the Blink script and the default startup file, both resulting in the same error. I'm worried I may of fried something or done something similar. I'm fine if the only solution is to buy a new Arduino, I'd just like to know what happened.
Here are is error message from both scripts:
Startup File
Blink Script
No errors occur when compiling, but when the code is sent to the Arduino, that happens. Any ideas on what the problem is?
It's hard to tell you what happened without knowing what you were doing with your board before it stopped working.
This error may have many causes, one possibility is that you downloaded the .org IDE, which has a higher version number. In this case it should be sufficient to uninstall the Arduino IDE, then download the latest .cc IDE from here and install it. Be sure to make a backup of your sketches first.
Your problem may also be a corrupt bootloader, in which case burning the bootloader may help.
If u have another functioning arduino with same processer(atmega328 in my case) than burn bootloader on ur malfunctioning arduino using ur function arduino
here-https://youtu.be/oce7D72Mdwo
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I am running into trouble calling libusb_open in C++ on Linux (running on Raspberry Pi but virtualized to x86 using Exagear).
I can find a device using libusb_get_device_list but it appears translating a device to a device handler using libusb_open is causing problems, even though it returns a 0 (success), however no further commands work. It is giving me the error:
libusb: error [op_open] getcap failed (22)
UPDATE
A little bit of digging has revealed that the following command is producing the error (within libusb):
r = ioctl(hpriv->fd, IOCTL_USBFS_GET_CAPABILITIES, &hpriv->caps);
where IOCTL_USBFS_GET_CAPABILITIES is _IOR('U', 26, __u32). Digging has revealed that error 22 from ioctl is an invalid argument. I'm still trying to unpick this, but any help here is greatly appreciated.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Trying to add an Event handler to a scheduled task in ColdFusion11.
I'm supposed to write a component that implements CFIDE.scheduler.ITaskEventHandler and "Specify a dot-delimited CFC path under webroot, for example a.b.server (without the CFC extension)"
I tried to put my component under
ColdFusion11/cfusion/wwwroot
ColdFusion11/cfusion/wwwroot/CFIDE
ColdFusion11/cfusion/wwwroot/CFIDE/scheduler
the Apache webroot
some virtual host webroot
I tried to add some dot notation (?) like CFIDE.scheduler.myEventHandler...
I don't understand if there is some more configuration at server level to understand.
I don't see any error in logs, the scheduler editor just refuse to save an EventHandler he cannot find, with the error
An error occured scheduling the task.
Invalid eventhandler.
Error: Eventhandler myEventHandler could not be found
Any help appreciated
The correct way seems to put the component in ColdFusion11/cfusion/wwwroot/myEventHandler.cfc, set the path as myEventHandler and implement in the component "CFIDE.scheduler.ITaskEventHandler"
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Im trying to run Ubuntu in a virtual machine on virtual box. So far I have reinstalled virtualbox once to see if it was the cause, then I redownloaded the .iso, but when I try to run the machine it says it still won't run.
Failed to open a session for the virtual machine ubuntu.
The virtual machine 'ubuntu' has terminated unexpectedly during startup with exit code 1.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
If you didn't power off the vm after last run, try right-click on VirtualBox Manager >> Discard Saved State. This will start the vm from (virtual) power off state. Current state of vm will be lost.
Are you using VirtualBox 4.3.14? There's a known bug which could be related: https://www.virtualbox.org/ticket/13187
I was having this problem, downgrading "solved" it.
Here's what I did and it worked properly:
(1) Move/copy your hard disk image (my_old_vm.vdi) to a
convenient folder, e.g. C:\my\VMS\my_new_vm\
(2) Create a new virtual machine (click the new button).
(2.b) At some point in time you are asked about the disk
to be used; choose 'existing disk image' and browse
to where you moved my_old_vm.vdi and select that.
(3) Start the VM and reconfigure the machine settings.
(4) Possibly delete the old machine. If you did not move the
.vdi file, then do not delete all files related to the
old machine.
This saved my day.
For me "Detachable Start" works, can you try it out?
I just went through exactly the same problem on a Windows VM. Uninstalling the Norton Internet Security and restarting my computer solved the problem. Credit to this article that I found here: https://forums.virtualbox.org/viewtopic.php?f=6&t=62615