When I start or open a virtual controller, it gets stuck on “Starting” until a window appears indicating there is no response. I have tried reinstalling, running with administrator privileges, verifying file paths, and checking versions (such as .NET and RobotWare); the firewall rules are correct and the processes seem to be running fine. However, after the error message, no controller appears in the browser—or if one does, the only option is to restart it—and the virtual controller process remains active in the task list.
Hello there,
If the VC processes exist, try this: In RobotStudio, go to Options → Virtual Controller → check the “To a console window” check box.
Then try to start a controller, and check the console window for an output.
When the controller crashes, the bottom 10-15 lines will show the cause.
If you see something like
01:00:00:130128 Status 0 from if_feature_present abb.robotics.robotcontrol.options.csgatewaynotconnected
osal_task_panic due to "osal_crypt: Must be able to open export key"
Will cause deliberate exceptionosal_exception_win32.cc,90 : Exception: task: "robRootts" @00007FFACD19C3C0, code:0xc0000005
25-09-29 14:17:43 MC0(robRootts): osal_exception_win32.cc 90 Exception: task: "robRootts" @00007FFACD19C3C0, code:0xc0000005
then the solution is to clear the contents of C:\Users\<username>\AppData\Roaming\Microsoft\Crypto\Keys\
Otherwise, my recommendation would be to reach out to your local ABB and ask for assistance, showing the console log output.
Thanks, but that doesn’t seem to be the problem; based on the virtual controller and AI output windows, we’ve determined the error is here, but we can’t move forward.
Status 13 from calling rlvisualize_start
(safety): SYS STOP
