Python failure - exit code -2135228411 (0x80bb0005): (unknown error)

Author	Message
Richard James Send message Joined: 30 Mar 20 Posts: 14 Credit: 2,109,641 RAC: 1,125	Message 106725 - Posted: 7 Aug 2022, 3:54:50 UTC Last modified: 7 Aug 2022, 4:05:09 UTC All python tacks are failing within a few seconds. A web search shows nothing useful. Current version of Bionic/VB installed (7.20.2) OS is Win 10 21H2 What is the problem? Thanks. Richard ============================= Here is the log listing for one: 8/6/2022 8:34:31 PM \| Rosetta@home \| [task_debug] task is running in processor group 0 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] task_state=EXECUTING for aaae-AGLY_pp-mNMPHE-ALA-ACHA14C_2859551_14_0 from start 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] Process for aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 exited, exit code 2159738885, task state 1 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] task_state=EXITED for aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 from handle_exited_app 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] result state=COMPUTE_ERROR for aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 from CS::report_result_error 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] Process for aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 exited 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] exit code -2135228411 (0x80bb0005): (unknown error) 8/6/2022 8:34:31 PM \| Rosetta@home \| Computation for task aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 finished 8/6/2022 8:34:31 PM \| Rosetta@home \| Output file aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0_r987744273_0 for task aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 absent 8/6/2022 8:34:31 PM \| Rosetta@home \| [task] result state=COMPUTE_ERROR for aaae-AIB-ACPhenC_pp-NMPHE-mACHA14C_2860235_14_0 from CS::app_finished ID: 106725 · Rating: 0 · rate: / Reply Quote

Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1681 Credit: 17,854,150 RAC: 22,647	Message 106728 - Posted: 7 Aug 2022, 9:06:28 UTC VBoxManage.exe: error: Could not launch the VM process for the machine 'boinc_6b728bc99538d245' (VERR_INVALID_UTF16_ENCODING) VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MachineWrap, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: "LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())" at line 727 of file VBoxManageMisc.cpp 2022-08-06 20:21:58 (12136): VM failed to start. 2022-08-06 20:21:58 (12136): Could not start 2022-08-06 20:21:58 (12136): ERROR: VM failed to start It couldn't start the Virtual Machine. Hyper V must be disabled. Virtualisation must be enabled in the BIOS. Grant Darwin NT ID: 106728 · Rating: 0 · rate: / Reply Quote

Richard James Send message Joined: 30 Mar 20 Posts: 14 Credit: 2,109,641 RAC: 1,125	Message 106741 - Posted: 9 Aug 2022, 3:39:13 UTC - in response to Message 106728. 2022-08-06 20:21:58 (12136): VM failed to start. 2022-08-06 20:21:58 (12136): Could not start 2022-08-06 20:21:58 (12136): ERROR: VM failed to start It couldn't start the Virtual Machine.[/quote] Hyper V must be disabled. Virtualisation must be enabled in the BIOS. Grant. As discussed earlier I had already done that. However, on checking I discovered that "Hyper V" is not used in the BIOS description. Instead a search on "Hyper" revealed it is Hyper-Threading. I have now disabled that and all seems good. Several files apparently processed with no error. Thanks again for your assistance. Richard ID: 106741 · Rating: 0 · rate: / Reply Quote

Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1681 Credit: 17,854,150 RAC: 22,647	Message 106742 - Posted: 9 Aug 2022, 6:16:41 UTC - in response to Message 106741. However, on checking I discovered that "Hyper V" is not used in the BIOS description. Instead a search on "Hyper" revealed it is Hyper-Threading. They are two completely different things, and only one is in the BIOS. HyperV is Microsoft's own Virtualisation software, it's an optional programme. Some systems may have it installed, others don't- accessable through Add/Remove programmes, Windows features. Hyper-Threading is virtual processors, allowing a physical processor to act as 2. Disabling that will halve the number of cores/threads your system has (or in the case of current Intel CPU halve the number of cores/threads the P cores can provide). Virtualisation in the BIOS is what allows virtualisation to make use of hardware supported Virtualisation features of the CPU. Grant Darwin NT ID: 106742 · Rating: 0 · rate: / Reply Quote

Richard James Send message Joined: 30 Mar 20 Posts: 14 Credit: 2,109,641 RAC: 1,125	Message 106749 - Posted: 10 Aug 2022, 4:45:25 UTC - in response to Message 106742. > However, on checking I discovered that "Hyper V" is not used in the BIOS description. Instead a search on "Hyper" revealed it is Hyper-Threading. >They are two completely different things, and only one is in the BIOS.[/quote OK > HyperV is Microsoft's own Virtualisation software, it's an optional programme. OK, already disabled. > Hyper-Threading is virtual processors, allowing a physical processor to act as 2. OK, restored. > Virtualisation in the BIOS is what allows virtualisation to make use of hardware supported Virtualisation features of the CPU. Yes. Seems to be working OK now. Thanks. Richard ID: 106749 · Rating: 0 · rate: / Reply Quote