Learning Forum

[AlperenKucukozkan]

Hello

I downloaded the last student version of Ansys and I am using Ansys Fluent,but whenever I click on meshing it says "Starting meshing"  and does not open meshing application.

I have disabled my antivirus and firewall but nothing changed also downloaded several times and installed again yet result is still the same.My OS is Windows 10 home.

Lastly,I realized that the application related to meshing looks properly working in the Task manager called"AnsysWBU.exe yet I can not open meshing.

Edit

Other than the meshing everything works fine.

 

Thanks for the help.

[Keyur Kanade]

can you open geometry?

can you open spaceclaim?

is your geometry complex?

there is limitation on no. of faces of geometry for student version. 

please check 

https://www.ansys.com/en-in/academic/free-student-products?utm_source=studentcommunity&utm_campaign=studentcommunity&utm_content=Studentproduct&utm_source=studentcommunity&utm_campaign=studentcommunity&utm_content=Studentproduct

Regards,

Keyur

 

If this helps, please mark this post as 'Is Solution' to help others.

Guidelines on the Student Community

How to access ANSYS help links

 

 

[AlperenKucukozkan]

I can open any other functions other than the meshing.

I just used (tried) geometry with a just one simple plane,nothing complicated.

[Keyur Kanade]

what is geometry? is 2d or 3d?

can you please open spaceclaim and insert image of the geometry here. 

 

[AlperenKucukozkan]

It doesnt matter what geometry I use.

I tried with 2D ,meshing did not work.

I tried with 3D ,meshing did not work.

[Keyur Kanade]

can you please open spaceclaim and insert image of the geometry here. 

[Ioakeim Sioutis]

 

Hello, is the problem solved somehow? I face exactly the same problem. Meshing is not starting (in the workbench it keeps initializing forever) and the geometry can be opened from space claim. I am using 2022R2 version.

 

[r.takamura089]

Hi, I have encountered same problem with Ansys 2022R2 Workbench.

I can open Geometry softwares(Discovery, Spaceclaim, Design Modeler), but the Meshing software does not open.

I created a simple cylinder using spaceclaim and tried to open Meshing, and workbench freezez with message of "Starting Meshing..." as the screenshot below.

Any idea on how to solve this issue?

 

[George Karnos]

Could virus protection or firewall software be interferring with the Meshing program starting up?
(Check Virus and Firewall logs)
Also, if you look under:
%TEMP%\WorkbenchLogs\
There should exist log files for the session.
Are there any errors in the log file?

[r.takamura089]

Hi George, thanks for the reply.

I am using Trend Micro Apex One as Anti-virus software.

I have checked the logs in it, but there's no significant message, so I doubt it as the cause of this error.

I found Workbench log file, the message was as follows.

Event log opened 2023/07/13 10:08:45 東京 (標準時)

Product version: 2022 R2
Build version: 22.2.0.2022051318

{2023/07/13 10:08:58} [ProjectReplaced:Project] A new project has been created.

{2023/07/13 10:09:31} [ProjectReplaced:Project] The project has been opened from C:\Work\2023\ansystest\test.wbpj.

{2023/07/13 10:10:27} [ProjectSaved:Project] The current project has been saved: C:\Work\2023\ansystest\test.wbpj.

{2023/07/13 10:29:50} [Ansys.Core.Commands.CommandFailedException:Message] Error while waiting for Meshing initialization to complete. Either the application crashed or Workbench lost communication with it.
System.Net.Sockets.SocketException: 既存の接続はリモート ホストに強制的に切断されました。

Server stack trace: 
   場所 System.Runtime.Remoting.Channels.SocketStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   場所 System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
   場所 System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
   場所 System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
   場所 System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
   場所 System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
   場所 System.Runtime.Remoting.Channels.Tcp.TcpClientSocketHandler.ReadHeaders()
   場所 System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   場所 System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Ans.Meshing.RemoteItf.IMeshingHelper.WaitForRemotingInitialization()
   at Ansys.Addins.Infrastructure.Remoting.RemotingApiHelper.FatalApiMethodInvalidOperationException(String message, RemotingApiMethod callback)
--- Ansys.Core.Commands.UserReadableFailureException: Error while waiting for Meshing initialization to complete. Either the application crashed or Workbench lost communication with it.
   at Ansys.Addins.Infrastructure.CommandUtilities.CommandHelper.Execute(IFullContext context)
   at Ansys.Core.Commands.Concurrency.CommandWorkUnit.executeInContext(CommandContext subContext, IExecutionEngineCallback tracer)
   at Ansys.Core.Commands.Concurrency.BaseWorkUnit.doExecute(IExecutionEngineCallback executionEngine, CommandContext subContext)
   at Ansys.Core.Commands.Concurrency.BaseWorkUnit.Execute(IExecutionEngineCallback executionEngine, Boolean dontCatchExceptions)
--- Ansys.Core.Commands.CommandFailedException: Error while waiting for Meshing initialization to complete. Either the application crashed or Workbench lost communication with it.
CommandName: Meshing.StartMeshingEditor(ModelContainer="Mesh")
   at Ansys.Core.Commands.CommandAsyncResult.RethrowFailureException(Exception e)
   at Ansys.Core.Commands.CommandAsyncResult.Wait(Int32 milliSecondsTimeout, Boolean exitContext)
   at Ansys.Meshing.Core.Commands.StartMeshingEditor.InvokeAndWait(IProtectedContext context, DataContainerReference ModelContainer, Boolean IsBatchMode, Boolean RequireLicense)
   at Ansys.Meshing.GUI.EditModel.Invoke(GuiOperationContext context)
   at Ansys.UI.GuiOperationContext.Invoke(GuiOperationMetaData operationData)
   at Ansys.UI.UIManager.InvokeOperationCore(String pseudoname, OperationDelegate callback, Boolean allowOSMessages, Boolean coreTransaction, Boolean deferredRefreshOnly)

 

 

 

[r.takamura089]

Hi all (if there's anyone interested ;))

I found the solution for my case, hope this helps someone.

 

It seems that the proxy setting was causing this problem.

In Windows (mine is 10) environment variables, there is HTTPS_PROXY.

That variable's value would be something like http://proxyname:portnumber.

For me, deleting "http://" from that value solved the issue.