"crashes" while exporting from VM - crash

I am using CENTOS6 and REDHAWK2.0 (RH2.0). VM installed based on "VirtualBox 5.0.16 for Windows host" and "VirtualBox 5.0.17 r106140 Guest Additions installer image". The OS for the computer is Windows professional 7. However, whenever I export the machine profile (CENTOS6, RH2.0) from VM, all the projects listed in the REDHAWK "project explorer" window disappear (no projects show up in "project explorer" window if I reopen the REDHAWK IDE). I have tried this in different PCs, and it keeps happening. However, if I don't export the appliance, everything is OK, which means that project list in the "project explorer" window stay no matter how many times I close and open the REDHAWK IDE in the VM.
Another note:
When I close the VM, I get the following message:
Microsoft Visual C++ Runtime Library
Runtime Error!
program: C:Program Files\Oracle\VirtualBox\VBoxSVC.exe
R6025
-pure virtual function call
Then, after I close this dialogue box, I got another message:
VirtualBox Interface has stopped working
Details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: VBoxSVC.exe
Application Version: 5.0.16.5871
Application Timestamp: 56d9b7f1
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.40219.1
Fault Module Timestamp: 4d5f034a
Exception Code: 40000015
Exception Offset: 00000000000761c9
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 3b88
Additional Information 2: 3b88e6353d8105cc00c90d3a5da0074b
Additional Information 3: 5abc
Additional Information 4: 5abc42e81271271eab3d346a48f0ce0a
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Any clues on how to fix this problem?

I have not seen any bugs that are related between VirtualBox itself on the host and the Redhawk project explorer in the guest, but the following are steps you can take to debug further. Because your order of operations isn't clear:
Do not export a VM while the VM is still running. Shut it down first, then export.
If you were already doing that, or still have issues, ensure there are no compatibility issues between your version of host OS (Windows 7 Professional) and the version of VirtualBox (VirtualBox 5.0.16). A quick search on your error turned up VirtualBox COM service crash at exit. Try re-installing the VirtualBox client and updating your Windows host - if there is something wrong/corrupted with VirtualBox itself then there's no telling what problems you'll have with a guest OS.
If you re-install VirtualBox and then re-import or add your existing VM and you still have issues inside the VM with Redhawk IDE project explorer view, you may have a corrupted IDE. Delete the eclipse folder with the IDE and re-download it.

Related

VirtualBox won't run win10: Failed to open a session for the virtual machine w10. Result Code: NS_ERROR_FAILURE (0x80004005)

Ok so I want to get a virtual machine with Windows so I can download applications only on Windows (Not on OSX (I'm on Big Sur 11.2.3 by the way)), so I downloaded VirtualBox, then downloaded the Windows thing which apparently I have to (as seen in one of the pics) (you can tell I have hardly any experience with vms), then I created a new vm in the VirtualBox app, and left all the default settings except for the type of hard drive (which is also in one of the pictures), then I clicked Start and it asked me to add a 'virtual optical disk file', so I clicked on the folder button then clicked add in the top left, and it gave me this error code:
Failed to open a session for the virtual machine w10.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
as you can also see in one of the pictures below. Also, when I leave the screen for a couple of minutes right before I click on the previously mentioned add button, this appears:
but I tried just leaving it to load, and nothing happened. I have tried uninstalling using the uninstall tool twice, rebooting my Mac, etc etc, and yes I have allowed everything I need to in the Security settings. I'm not installing it on a moderator account, but the Windows 10 virtual optical disk file is in Documents which the account I'm on has read and write access to, and obviously the actual VM is in applications.
Thanks so much!
Here's the previously mentioned image of the one changed setting:
And here's the pic of the Win10 64-bit I had to install:
thanks everyone!
VirtualBox Version: 6.1.22 r144080 (Qt5.6.3)
Host Operating System: MacOS BigSur
I came across exactly same issue, where clicking on add to choose image was crashing the dialog. This issue persists in the latest version of Virtual Box for Mac.
I could figure out couple of ways to avoid clicking on Add button to choose image.
First Option:
Steps:
Click on Settings to open settings window for your VM.
Choose Storage
Select Empty disc and choose Disk image by clicking small disc icon in the Attributes section. Please follow the image to have visual instructions.
Second Option:
Steps:
Click on VM's Normal start
Once you get the option to choose image, simply cancel the dialog.
Now click on the small disc icon in the bottom of VM's dialog to choose the image.
Hope this helps. Feel free to comment if you find this post useful.
I had the same message because of permissions at directories where the hard disks were stored in. So, just execute VirtualBox 'As Administrator' and all run well.
I was getting the same error on Ubuntu 22.04 machine while trying to start an existing or a new VM-
Failed to open a session for the virtual machine NuacareRocky.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
I tried a few things as suggested on youtube, but nothing worked. finally, I just upgraded the extension and it worked.

Need to restart wsl everytime after Windows start before using vscode-remote

I'm running Windows 10 with WSL2. I'm using VSCode with the Remote - WSL extension to open the files from my wsl file system.
When I boot my Windows laptop, and open VSCode I get the following error:
When I perform a wsl.exe --shutdown in PowerShell, and restart Docker Desktop, Everything works fine. But I have to do this after every laptop restart.
Remote WSL extension version: v0.51.4
Visual Studio Code version: v1.51.1
Windows version: 10.0.19041 Build 19041
Someone any idea?
I have had this problem several times, and I have found that on Windows 10 20H2 one of the two options described below solves the problem.
Network reset
This option can make you lose your network configuration, so use it with discretion and read every warning. You can perform this task by going to Settings > Network & Internet > Status. There you need to click on the option "Network reset" after that, you can start the network reset by clicking on "Reset now" Picture of Windows 10 20H2 status section. Then you will need to wait some minutes until your PC is restarted automatically and try to execute Visual Studio Code under WSL2 again.
Reset Windows
This option is dangerous as it will remove either all your files and programs or all your installed programs. You select what you want to remove before starting the reset process. This option can be performed by going to Settings > Update & Security > Recovery. Then you have to click on the button "Get started" on the section "Reset this PC" and follow the instructions provided by the reset tool Picture of Windows 10 20H2 recovery section. After your Windows is reset, you will have to configure your WSL again because all your WSL files will be lost when executing this operation.

Uno Platform on WSL: Errors in unchanged template

I'm attempting to build the Uno project template with Linux support, using WSL (Ubuntu 20.04), following the official guide.
Unfortunately, I always get an error running the Skia GTK project template:
DllNotFoundException: Gtk: libgtk-3-0.dll, libgtk-3.so.0, libgtk-3.0.dylib, gtk-3.dll
I tried adding libgtk-3-0.dll's folder to the Windows PATH, but this didn't help. Then I tried installing libgtk-3 in WSL, but it just changed the error to Can't open display :0.
What am I doing wrong?
The Skia.Gtk backend expects a running X Window server to connect to.
The guide suggests installing vcXsrv, an X11 server for Windows
You'll need to start the server in "Multiple windows" mode, starting with "no client" mode.

Out of Memory "Set CS6 = New LabelManager2.Application" (VB6 - Codesoft)

I build VB6 Application to printing label using Codesoft 9 Application, but when I try to execute the code, the error appears "Out Of Memory" and then it debug to this code :
Set CS6 = New LabelManager2.Application
So, what's wrong with my code, any idea???
The error should be an exception with this message:
Creating an instance of the COM component with CLSID
{3624B9C0-9E5D-11D3-A896-00C04F324E22} from the IClassFactory failed due to the following
error: 8007000e Not enough storage is available to complete this operation.
(Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).
The issue probably involves licensing.
Only the Enterprise version of Teklynx Codesoft 9 and 10 support the full ActiveX LabelManager2.dll (Lppx2.Application) component. I can duplicate your problem using the Pro level or not starting the Codesoft application with the Enterprise Evaluation license first.
I think that the .Net wrapper version Lppnet.dll (Tkx.Lppa.Application), may work with the Pro level license, but it is very limited version.
Here is some additional information:
If you are running in Demo/Evaluation mode you can set the license level of the demo in the program's options
To open options with Codesoft 9, click Tools\ Options
To open configuration with Codesoft 10, click Tools\ Configuration
On the left side of the resulting dialog, there is a set of icons. Scroll to the bottom and click Product Mode
Select Codesoft Enterprise RFID
Click OK
Close and restart the program
When running in a demo mode you have to start the Codesoft application first before running your program. It may not load on its own unless you have an Enterprise license installed. I don’t currently have a non-demo Codesoft license to do testing on this aspect.
I also do not have Codesoft 2012 or 2014 installed so I don’t know if everything listed applies directly to those versions. They have made major changes to the way licensing works and installing them uninstalls the older version.

Can't launch JBoss7 from Eclipse Indigo

I can't figure out where I am going wrong. I have Eclipse Indigo, JBoss 7.1, JBoss Tools installed. I have this configuration working on my Windows7 64-bit system. I am attempting to set up a co-worker's Windows XP 32-bit machine with the same configuration but am not able to get the server to launch. I have configured the server but when I attempt to start the server, I get an error indicating that it was unable to start the server but there is no specific error listed.
I am able to start JBoss from the command prompt using the standalone.bat file.
I am able to configure the standalone.xml file from within Eclipse. I have confirmed this by checking the file in the standalone/configuration directory.
When I attempt to publish the project from within Eclipse, it does not publish.
Nothing gets written to server.log
The startup parameters match what I have on my computer.
I can't figure out what I am missing. Any suggestions would be appreciated!
Edit:
I have done some more checking. I am able to publish to the server and I am able to start the server (with the published application) fine from the command prompt. That part works. When I attempt to start the server from within Eclipse it gives me "Server JBoss 7.1 Runtime Server failed to start." It never writes anything to the console tab in Eclipse either so I can't tell why it is failing to start.
Also in the Servers tab, there is an entry called "Server Details". When I expand that entry, it says "Not Connected".
The answer to my problem is that Eclipse had be configured to use the java JDK, not the JRE. As soon as I switched over to use the JDK it started working fine. For some reason JBoss will start under 64-bit windows with the JRE but under 32-bit you need to use the JDK. I found the answer here: https://community.jboss.org/thread/169097