Hi Muhammad, is this error persistent or does it happen only sometimes? Fluent does not start at all anymore? Did you try to kill all fluent and cortex processes? Did you load the mesh in the same case or did you start a new case? On what operating system are you working? 

Thanks Julian,

Most of times, I face this error/Message. Once in a ten fifteen tries, don't.

I also delete clean-up files also.

I loaded the new mesh in a new case.

I am using ANSYS Fluent 14.5 on Windows 8.1 Pro.

The detailed Message is as bellow

Ansys.Fluent.Cortex.CortexNotAvailableException: Exception of type 'Ansys.Fluent.Cortex.CortexNotAvailableException' was thrown.

at Ansys.Fluent.Data.SetupData.GetCommunicator(IReadLockContainer context)

at Ansys.Fluent.Data.SetupData.LaunchFluentAndRead(IFullContext context, Boolean batchMode, Boolean loadSolution, DataContainerReference fromContainer, Boolean internallyStarted, Boolean reuseSession, Boolean pendingMode, Boolean isRsmUpdate)

at Ansys.Fluent.Data.SolutionData.LaunchFluentAndRead(IFullContext context, Boolean batchMode, Boolean internallyStarted)

at Ansys.Fluent.Commands.EditCommand.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: Exception of type 'Ansys.Fluent.Cortex.CortexNotAvailableException' was thrown.

CommandName: Fluent.Edit(Container="Solution 1")

at Ansys.Core.Commands.CommandAsyncResult.Wait(Int32 milliSecondsTimeout, Boolean exitContext)

at Ansys.Core.Commands.CommandAsyncResult.Wait()

at Ansys.Fluent.Commands.EditCommand.InvokeAndWait(IProtectedContext context, DataContainerReference Container, Boolean Interactive)

at Ansys.Fluent.Gui.GuiUtilities.GetLauncherSettingsAndEdit(GuiOperationContext operationContext, DataContainerReference cref, LauncherEditMode editMode)

at Ansys.Fluent.Gui.OpenInFluentGui.Invoke(GuiOperationContext context)

at Ansys.UI.UIManager.c__DisplayClassb.b__a()

at Ansys.UI.UIManager.InvokeOperationCore(String pseudoname, OperationDelegate callback, Boolean allowOSMessages, Boolean coreTransaction)

Okay, thanks for the additional info. It seems it does not depend on your case or mesh, but on your system configuration, system ressources or Fluent installation.

It might be that the dense mesh needs more ressources than available or pushes your system to its limits. Did you check, how much system memory is still available with the coarser mesh? How many mesh elements do the coarse and fine mesh have, respectively?

If there are enough system ressources, I could only suggest to reinstall Fluent and/or Windows, if possible, or directly contact the ANSYS support.

The problem is caused by mesh interfaces

Brahim Mohammedi i agree with you ...i also faced this problem ...and got rid og this by managing mesh interfaces.

Ahmad Saeed, could you share some tips on how to manage the interfaces?