-
-
December 21, 2022 at 10:33 pm
roozbeh.mehrabadi
SubscriberHello, when openning the Mechanical Modeller, we run into the above error message and it fails to start.Âplatform: CentOS 7.9.2,  AnsysFLST version 22.2           command to start: runwb2ÂSteps to produce the error: Open Workbench ==> Make a stead-state thermal project ==> double click on geometry ==>Make a simple geometry in design modeler (e.g. a simple cube), then in Workbench double click on Model.Â(Any other workflow that result in opening the Mechanical modeler would result in the error)Â# After selecting Steady State Thermal and double clicking on Geometry, a little error window pops up:
WB Error while loading the DocingPane.Then the "Steady-State Thermal - DesignModeler window shows up.ÂThe following are the exception trace shown on the terminal. If you need more information, please let me know.Roozbeh====================================================AnsysWBU: END
  Error: SERVER TO CLIENT CONNECTION ERROR: Connection to WB failed: System.ArgumentException: Invalid port number 0 upon calling CreatePortBasedURI
 at Ans.IPC.Remoting.Common.Connection.CreatePortBasedURI (System.Int32 portNumber, System.Type requestedType) [0x0001a] in:0Â
 at Ans.IPC.Remoting.Server.ServerToClientConnection.InitialConnect (System.Type classToProxy) [0x00000] in:0Â
 at Ans.IPC.Remoting.Server.ServerToClientConnection.TryToConnect () [0x00000] in:0Â
Throwing failure exception from wait: Unable to start the Mechanical editor.
--------------------------------------------
UIManager.InvokeOperationCore (CommandFailedException)
--------------------------------------------
Ansys.Core.Commands.CommandFailedException: Unable to start the Mechanical editor. ---> Ansys.Core.Commands.UserReadableFailureException: Unable to start the Mechanical editor.
 at Ansys.Addins.Infrastructure.CommandUtilities.CommandHelper.Execute (Ansys.Core.Commands.IFullContext context) [0x0004b] in:0Â
 at Ansys.Core.Commands.Concurrency.CommandWorkUnit.executeInContext (Ansys.Core.Commands.CommandContext subContext, Ansys.Core.Commands.Concurrency.IExecutionEngineCallback tracer) [0x000a1] in <06df2a3f074f408f9f324f103911d6ca>:0Â
 at Ansys.Core.Commands.Concurrency.BaseWorkUnit.doExecute (Ansys.Core.Commands.Concurrency.IExecutionEngineCallback executionEngine, Ansys.Core.Commands.CommandContext subContext) [0x0002d] in <06df2a3f074f408f9f324f103911d6ca>:0Â
 at Ansys.Core.Commands.Concurrency.BaseWorkUnit.Execute (Ansys.Core.Commands.Concurrency.IExecutionEngineCallback executionEngine, System.Boolean dontCatchExceptions) [0x0010f] in <06df2a3f074f408f9f324f103911d6ca>:0Â
  --- End of inner exception stack trace ---
 at Ansys.Core.Commands.CommandAsyncResult.RethrowFailureException (System.Exception e) [0x0000c] in <06df2a3f074f408f9f324f103911d6ca>:0Â
 at Ansys.Core.Commands.CommandAsyncResult.Wait (System.Int32 milliSecondsTimeout, System.Boolean exitContext) [0x00095] in <06df2a3f074f408f9f324f103911d6ca>:0Â
 at Ansys.Core.Commands.CommandAsyncResult.Wait () [0x00000] in <06df2a3f074f408f9f324f103911d6ca>:0Â
 at Ansys.Simulation.Core.Commands.EditModel.InvokeAndWait (Ansys.Core.Commands.IProtectedContext context, Ansys.Core.DataModel.ProjectSystem.DataContainerReference Container, System.Boolean Interactive, System.Boolean Hidden, System.Boolean StartAsReadOnly) [0x0003c] in <9e984731e7ad40778cdd21db3e4a2906>:0Â
 at Ansys.Simulation.GUI.EditModel.InvokeCommand (Ansys.UI.GuiOperationContext context, Ansys.Core.DataModel.ProjectSystem.DataContainerReference dcr) [0x00006] in <0c8aab3e3e3c4de8b649add38feec2b8>:0Â
 at Ansys.Simulation.GUI.EditModelBase.InvokeEditModelOperation (Ansys.UI.GuiOperationContext context, Ansys.UI.Interfaces.IGuiOperation guiOperation, Ansys.Core.DataModel.ProjectSystem.DataContainerReference dcr) [0x00284] in <0c8aab3e3e3c4de8b649add38feec2b8>:0Â
 at Ansys.Simulation.GUI.EditModelBase.Invoke (Ansys.UI.GuiOperationContext context) [0x00012] in <0c8aab3e3e3c4de8b649add38feec2b8>:0Â
 at Ansys.UI.GuiOperationContext.Invoke (Ansys.UI.GuiOperationMetaData operationData) [0x00006] in:0Â
 at Ansys.UI.UIManager+<>c__DisplayClass206_0.b__0 () [0x00031] in :0Â
 at Ansys.UI.UIManager.InvokeOperationCore (System.String pseudoname, Ansys.UI.Views.View+OperationDelegate callback, System.Boolean allowOSMessages, System.Boolean coreTransaction, System.Boolean deferredRefreshOnly) [0x001a6] in:0Â
--------------------------------------------*** making exception trace ***
Â
-
December 28, 2022 at 2:22 pm
MangeshANSYS
Ansys EmployeeHello
Please check if a dedicated graphics card and recent driver from the manufacturer installed on this system. Or are you using remote display?
-
June 8, 2023 at 11:01 pm
barrett0
SubscriberHello, we're currently running into the same error message, with remote display. Any guidance on how to proceed would be helpful.Â
thanks
-
-
- The topic ‘Error message: Unable to start the Mechanical editor in ANSYS WorkBench’ is closed to new replies.
-
3647
-
1313
-
1142
-
1075
-
1013
© 2025 Copyright ANSYS, Inc. All rights reserved.