LS Dyna

LS Dyna

Re: Linux 21.04 error

    • Sa-aadat Parker
      Subscriber

      Hello All,

       

      I get the following error when I try and run workbench on Linux. 

      /opt/ansys_inc/v222/Framework/bin/Linux64$ ./runwb2  

      Unhandled exception caught :

      System.DllNotFoundException: Ans.QT.dll assembly: type: member:(null)
       at (wrapper managed-to-native) Ansys.UI.Toolkit.QTC.Application.ans_qt_Application_setPluginDirectory(intptr,strin
      g)
       at Ansys.UI.Toolkit.QT.Application.SetPluginDirectory () [0x000d1] in :0  
       at Ansys.UI.Toolkit.QT.Application..ctor () [0x00006] in :0  
       at Ansys.UI.Toolkit.QT.UIFactory.newApplication () [0x00000] in :0  
       at Ansys.UI.Toolkit.UIFactory.newApplication () [0x0000c] in <3d00ca1c00134e6f8cbdeabb60d40546>:0  
       at Ansys.UI.Toolkit.Application.InstantiateIApplication () [0x00000] in <3d00ca1c00134e6f8cbdeabb60d40546>:0  
       at Ansys.UI.Toolkit.Application..cctor () [0x0000a] in <3d00ca1c00134e6f8cbdeabb60d40546>:0  
      --- System.TypeInitializationException: The type initializer for 'Ansys.UI.Toolkit.Application' threw an exception.
       at Ansys.UI.UIManager..ctor () [0x00055] in :0  
       at Ansys.UI.UIManager.get_Instance () [0x00023] in :0  
       at Ans.Program.Runtime.InitializeSplashScreen () [0x00057] in <533ef4cf2ec54545830ecf48d3de026d>:0  
       at Ans.Program.Runtime.Initialize (Ans.Program.RuntimeSettings settings) [0x0021a] in <533ef4cf2ec54545830ecf48d3d
      e026d>:0  
       at Ans.Program.ExecutableBase.Run (Ans.Program.CommandLineParse parser) [0x0000d] in 7a39>:0  
       at Ans.Program.ExecutableBase.DoMain (System.String[] args) [0x000be] in :0

    • Rachel Gomez
      Subscriber

      In many ways computers are this wobbling tower of intertwined standards, protocols, interfaces and files. Considering just how complex a modern Linux system is, it's astonishing that a Linux PC manages to successfully complete the delicate dance of powering up, launching the bootloader, handing over to the kernel, loading files of its file system, hopping through init and establishing an X graphical interface with interactive graphical desktop manager, wireless internet connection and all the other services that modern systems provide.

      At any stage this wobbling tower can crash down – and when it does, we're here to help you pick up the pieces! Our guide starts at the beginning with troubleshooting the boot process, moving through basic hardware and system issues, then on to more generic hardware, networking and finally classic desktop problems.

      Hopefully you'll come out of the darkness with at least a few invaluable nuggets of Linux knowledge to help make your Linux experience that little bit smoother and even more enjoyable. So lets turn the page and get fixing!

      The first thing to do is be patient – the boot process may be trying to initialise a piece of hardware, or access the network before it's available. These can time out after a few minutes, either allowing boot to proceed or at least giving you an error message to work with.

      In the good old days, distros used to stream reams of text up the screen as they were booting, until it became fashionable to hide this with a splash screen. Unfortunately, the splash screen also hides any error messages. You can disable the splash screen at the boot menu: if your computer starts booting without showing a menu, hold down Esc when it boots to call up the menu.

      If there's a recovery or safe option, pick that, as it disables the splash screen and often sets safer (if potentially less efficient) boot options. Otherwise, put the highlight on your normal boot option and press E for edit. Find the line that starts with linux and look for options like quiet, splash or theme.

      Delete these options and press F10 to continue booting. This won't fix your problem (unless the problem is the splash screen itself), but it will let you see what is going on and either get an error message or an idea of which stage of the boot is failing at. Then you can investigate further. If it appears to be a hardware detection issue, try disconnecting all unnecessary hardware, such as printers, scanners or USB rocket launchers. Once you can get past the problem, you can start to fix it.

      Regards,

      Rachel Gomez

Viewing 1 reply thread
  • You must be logged in to reply to this topic.