Hi everybody,

i tried to run ANSYS Workbench on Debian or one of its kick-offs ([X][K]Ubuntu) and always end up with the situation that Workbench starts nicely, but when starting "Geometry" the applications hangs up showing a white rectangle in the upper left corner within the ANSYS window, starting "Meshing" ends up in a segfault.

The workstation has a NVIDIA graphic card (Quadro4 XGL 900) This situation seems to be caused by some issues resulting from Debians integration of the GLX-extension into the X-server (same results with XFree86 and X.org). When using the "nv"-driver or not loading the "glx"-Module Workbench's Geometry-Module starts (almost) perfectly. Since the GLX extension is missing, the 3D-Object-Window is empty (and Xlib is complaining about the missing GLX extension on stderr).

Right now I'm working on CentOS 4.5 with no problems, but I'm still trying to get the Workbench up and running on a Debian Linux. I checked Debian with the same nvidia-drivers (96.43.01) as on CentOS. As I remember some weeks before the official Debian 4.0 release (early 2007), Workbench worked with an etch installation (until I applied an dist-upgrade). Since then I haven't succeeded in bringing life back to Workbench on Debian&Co. Maybe it's worth to try installing backport libraries of the X-server.

In the official ANSYS forum I found some advices, but none of it worked:

- before starting Workbench ulimit -s unlimited

- using an environment variable setenv USEWBANSYS_GL true

Has someone spotted the problem with Workbench vs. X+GLX on Debian?

P.S.: Workbench runs on (uncertified by Ansys) Slackware 11.0 and distros basing on that one like VectorLinux 5.8 also tried others like PCLinuxOS, Knoppix etc. but they were also disappointing

[mechanicaldesign]

Hello hs,

In this moment I used Ubuntu9.04, and I try to installed ANSYS 11. First time when I installed on my computer, everithing works done, with exception of workbench. After I launching WB, apear a black window with specification "Segmentation Fault".

After that I trying to install other version of Linux (like OpenSusse, PClinuxOs), but the menus of this versions of linux are to difficult for me (I'm beginner in Linux).

You can send me some indication from where I can download an corect image of CentOs version 4.x, because all version which I downloaded present some problem (I think is because the image downloaded, the steps which apear on my insatation are different comparison with steps indicated on CentOs4.X).

All version which I trying to install and everithing working good, is version 5.3 from Centos. But in this moment I dont know if ANSYS11 can be installed on him.

I waiting your answer and if I discover something, I will send you an message.

Thank you in advance for support and best regards.

[Yankee]

I got some improvements using ANSYS12.1, the first release officially supporting the workbench2 environement (command runwb2) on Linux.

To intall it on a debian based distribution, you need to create a script called rpm somewhere in your path (eg /usr/local/bin), simply containing "echo glibc-2.5-34" : this is a workaround to tell which glibc version you have to the installer, that tries to get it from the rpm command ! You'll get some error messages about libraries (.so) which cannot be registered (using a "regsvr32" command specified on a workbench line), or that cannot be loaded in three .exe files. Nevertheless, the resulting distribution seems the same (diff -r gives only a few binary files differing) as the one I installed on a CentOS (redhat-based), that works almost fine.

To run it, you need to switch to an english locale, if you're not already. For example (on bash) you can issue "export LANG=en_US.UTF-8" before running runwb2 . The workbench environement works fine, enables you to call Fluent and CFX, that you can also call as standalone applications (typing "fluent" or "cfx5").

The only problem left is to start DesignModeller : clicking on a "Geometry" case in the workbench space opens an (empty) DM window, which is then closed with a message "A fatal error has occurred within AnsysWBU.exe and it must be closed..." displayed in the shell where runwb2 was issued (ie the standard error, I think). Switching back to the nv driver rather than nvidia (ie disabling the proprietary driver) does not improve the behavior, I just get a warning about the lack of GLX support, as Guest said, but no working DesignModeler.

Does someone has an idea to solve that, or to check the problem more deeply?

[mhsr]

I can't believe it's that simple. Ever since I've got a grip on the first Service Pack of v12, I tried to make the workbench run on debian. Thanks, Yankee, for the hint about the English locale. During the last weeks I was getting quite annoyed about SIGSEVs reported by the starting (and eventually crashing) application. My locale was set to de_DE@euro (use the -L parameter for non-English GUI text strings, e.g. runwb2 -L de) and on my second test system C - what a surprise, the must-have-locale for CFX 5.x...

To make the design modeler work you need the register the libraries that are logged in /ansys_inc/install.err. The errors are debian specific:

* debian/lenny: you need a working 'arch' command, there's none shipped in lenny, go get yourself a coreutils.deb from squeeze or something similar

* the registering application uses the recent Workbench(1) which complains about missing libComponentSystem.so because the workbench script (found in /ansys_inc/v121/aisol/workbench) uses 'uname -i' to determine on what kind of platform it is run. debian's uname returns 'unknown' when using the '-i' parameter. As a workaround change the workbench script in
line 86
< if [ 'uname -i' = "i386" ]; then
> if [ 'uname -m' = "i686" ]; then
and
line 98
< elif [ 'uname -i' = "x86_64" ]; then
> elif [ 'uname -m' = "x86_64" ]; then
After that you'll have to register the mentioned libraries manually. You will find the needed command lines in /ansys_inc/install.err

* debian also provides a rpm-package, if you don't want the installer/configuration to complain about the missing 'rpm' command

Tested the DesignModeler in Workbench2 on debian/squeeze/i686 some minutes ago, it works really fine. Going to check x86_64-platform and some other non-RHEL/SUSE-distros later

So, thanks again, Yankee.

[mhsr]

It's kind of strange: both, DesignModeler and Mesh Editor are run - according to ps - with the executable /ansys_inc/v121/aisol/CommonFiles/<platform>/ansyswbu.exe. While DM is doing great on debian-squeeze/i686, the start-up of the ME leads to the same error messages as the start of old Workbench StartPage (/ansys_inc/v121/aisol/workbench -> which calls the ansyswbu.exe without an additional argument). There are two message boxes popping up:

1. Error: Unable to create object WBScript.WBWshShell.121. Please contact technical support.

2.
Line: 3732
Char: 5
Error: Automation server can't create object
Code: 800a01ad
Source: Microsoft JScript runtime error
Script: return AnsObjectFactory.CreateDispatchObject(progID)

Turning debug on the following output is written to ~/.ansys/WorkbenchLogs/CoreEvents<id>.log:

[Ans.Core.Commands.CommandFailedException:Message] Unable to start the Meshing editor.
Ans.Core.Commands.UserReadableFailure: Unable to start the Meshing editor.
at Ans.Addins.Api.CommandHelper.Execute (Ans.Core.Commands.CommandContext context) [0x00000]
at Ans.Core.Commands.Concurrency.CommandWorkUnit.exec uteInContext (Ans.Core.Commands.CommandContext subContext, IExecutionEngineCallback tracer) [0x00000]
--- Ans.Core.Commands.CommandFailedException: Unable to start the Meshing editor.
Command: Meshing.StartMeshingProcess(AddinCollectionManager ="/Mesh/SimulationConnection:SimulationConnection", licenseCapabilityList=["10070"])
at Ans.Core.Commands.CommandAsyncResult.RethrowFailur eException (System.Exception e) [0x00000]
at Ans.Core.Commands.CommandAsyncResult.Wait (Int32 milliSecondsTimeout, Boolean exitContext) [0x00000]
at Ans.Core.Commands.CommandAsyncResult.Wait () [0x00000]
at Ans.Meshing.Core.Commands.StartMeshingProcess.Invo keAndWait (ICommandContext context, Ans.Core.DataModel.DataReference AddinCollectionManager, Ans.Core.Commands.Output`1 WorkbenchConnection, Ans.Core.Commands.Output`1 SimulationEventHandlers, Boolean IsBatchMode, System.Collections.Generic.List`1 licenseCapabilityList) [0x00000]
at Ans.Meshing.Core.ExternalProcessHandlers.StartSimu lation (Ans.Core.Commands.CommandContext context, Boolean bInBatch, Ans.Core.DataModel.DataReference modelRef, Ans.Core.DataModel.DataReference connectionRef) [0x00000]
at Ans.Meshing.Core.ExternalProcessHandlers.StartSimu lation (Ans.Core.Commands.CommandContext context, Ans.Core.DataModel.ProjectSystem.DataContainerRefe rence container, Boolean bIsBatchMode, Boolean bRequireLicense) [0x00000]
at Ans.Meshing.Core.Commands.StartMeshingEditor.Execu teCommand (Ans.Core.Commands.CommandContext context) [0x00000]
at Ans.Addins.Api.CommandHelper.Execute (Ans.Core.Commands.CommandContext context) [0x00000]
--- Ans.Core.Commands.CommandFailedException: Unable to start the Meshing editor.
Command: Meshing.StartMeshingEditor(ModelContainer="Mesh")
at Ans.Core.Commands.CommandAsyncResult.RethrowFailur eException (System.Exception e) [0x00000]
at Ans.Core.Commands.CommandAsyncResult.Wait (Int32 milliSecondsTimeout, Boolean exitContext) [0x00000]
at Ans.Core.Commands.CommandAsyncResult.Wait () [0x00000]
at Ans.Meshing.Core.Commands.StartMeshingEditor.Invok eAndWait (ICommandContext context, Ans.Core.DataModel.ProjectSystem.DataContainerRefe rence ModelContainer, Boolean IsBatchMode, Boolean RequireLicense) [0x00000]
at Ans.Meshing.GUI.EditModel.Invoke (Ans.UI.GuiOperationContext context) [0x00000]
at Ans.UI.GuiOperationContext.Invoke (Ans.UI.GuiOperationMetaData operationData) [0x00000]
at Ans.UI.UIManager+<InvokeOperation>c__AnonStorey1A. <>m__16 () [0x00000]
at Ans.UI.UIManager.InvokeOperationCore (System.String pseudoname, Ans.UI.Views.OperationDelegate callback, Boolean allowOSMessages) [0x00000]

Guess, that doesn't really help finding a solution to get all AddIns working in debian.

By the way, just checked v12.1 on a debian-squeeze/x86_64. Start-up of both, DM and ME, results in a plain white window with a pin-needle icon in the upper left corner and nothing else.

[Yankee]

Thanks, mhsr, and confiramtion : on ubuntu 9.10 (karmic), with a brand new install of ansys 12.1, and three modifications (1) add LANG=en_US.UTF-8 in runwb2 ; (2) modify the "workbench" script as you said ; (3) register manually the libraries :

- my problem with DesignModeler was solved by changing "uname -i" to "uname -m" in the script "workbench" (don't forget to change i386 to i686) and registering the libes

- I've now the same problem as you concerning meshing : exactely the same two popup messages, the second one being in a window called "script error". Then the first popup again, and the the meshing window disappears.

Your debug information doesn't sound clear for me (by the way how do you turn on debuging?)
I tried to locate this WBScript.WBWshShell in ansys_inc, I got one windows executable and some java scripts :

/ansys_inc/v121/aisol$ grep WBScript.WBWshShell */*/* */*/*/* */*/*/*/* */*/*/*/*/*
Fichier binaire CommonFiles/linia32/wbscriptu.rsb concordant
AGP/AGPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
AGP/AGPages/scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
CFXMeshApplet/CMPages/Scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
CFXMeshApplet/CMPages/Scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
CommonFiles/CommonPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
CommonFiles/CommonPages/scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
DesignSpace/DSPages/scripts/DSNonTranslatedStrings.js: str_ShellProgId = GenWBProgId("WBScript.WBWshShell");
DesignSpace/DSPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
DesignSpace/DSPages/scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
EDServices/EDPages/scripts/ImportCFXDialog.js: oWshShellHelper = eds.CreateActiveXObject(eds.GenWBProgId("WBScript. WBWshShell"));
EDServices/EDPages/scripts/ImportCFXDialog.js: oWshShellHelper = eds.CreateActiveXObject(eds.GenWBProgId("WBScript. WBWshShell"));
EDServices/EDPages/scripts/main.js: oWshShellHelper = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
EDServices/EDPages/scripts/NewBeamSectionDialog.js: oWshShellHelper = eds.CreateActiveXObject(eds.GenWBProgId("WBScript. WBWshShell"));
EDServices/EDPages/scripts/NewBeamSectionDialog.js: oWshShellHelper = eds.CreateActiveXObject(eds.GenWBProgId("WBScript. WBWshShell"));
EDServices/EDPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
EDServices/EDPages/scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
FEModeler/FEPages/scripts/FEHelperFunctions.js: var oShell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
FEModeler/FEPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");
FEModeler/FEPages/scripts/wbCommon.js: if(SystemInfo.OSType=="UNIX") var shell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
StartPage/StartPages/scripts/AIEActions.js: WshShell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
StartPage/StartPages/scripts/AIEActions.js: WshShell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
StartPage/StartPages/scripts/ProjectPageActions.js: var wbShell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll") );
StartPage/StartPages/scripts/StartPageMain.js: var WshShell = CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
StartPage/StartPages/scripts/StartPageMain.js: if(platform == "UNIX") return CreateActiveXObject(GenWBProgId("WBScript.WBWshShe ll"));
StartPage/StartPages/scripts/wbCommon.js: str_WScriptShellProgId = GenWBProgId("WBScript.WBWshShell");

Do you guess the usefullness of that command from that? and a workaround?

[strider]

Thanks mhsr, I can also confirm that design modeler on Ubuntu 9.10 x86_64 is working (with your modification of course). I had to add the entries into registry with sudo, otherwise I got the message that operation succeeded, but in reality nothing happened.
Now I am stuck at the same problem as you and Yankee with Mesh Editor.

Regards, Strider

[gokmenvt]

Hello, i need urgent help

i have a problem on ansys 12 workbench since this morning,i dont know what cause this problem, the program starts normally, when i tried to select analysis type, following error happened, (ihave vista x64)

System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent( )
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Ans.EngineeringData.Core.Preference.Load()
at Ans.EngineeringData.Core.Preference.get_Instance()
at Ans.EngineeringData.Commands.LibraryManager.LoadLi braries(IQueryContext contextToQuery, Boolean userLibrary)
at Ans.EngineeringData.Commands.LibraryManager.Initia lize(CommandContext cmdContext)
at Ans.EngineeringData.Commands.InitializeEngineering DataLibrary.ExecuteInitialize(CommandContext context)
at Ans.EngineeringData.Commands.InitializeEngineering DataLibrary.Execute(CommandContext context)
at Ans.Core.Commands.Concurrency.CommandWorkUnit.exec uteInContext(CommandContext subContext, IExecutionEngineCallback tracer)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.doExecu te(IExecutionEngineCallback executionEngine, CommandContext subContext)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.Execute (IExecutionEngineCallback executionEngine, Boolean dontCatchExceptions)
--- Ans.Core.Commands.CommandFailedException: Root element is missing.
Command: EngData.InitializeEngineeringDataLibrary(Name="Eng ineering Data")
at Ans.Core.Commands.CommandAsyncResult.RethrowFailur eException()
at Ans.Core.Commands.CommandAsyncResult.Wait(Int32 milliSecondsTimeout, Boolean exitContext)
at Ans.Core.Commands.Core.OutputArgBase.Wait()
at Ans.Core.Commands.Output`1.Get()
at Ans.ProjectSchematic.Data.CellTemplateEntity.Creat e(CommandContext context, String withName, DataReference inSystem, List`1 UpstreamContainers, Dictionary`2 systemProperties)
at Ans.ProjectSchematic.Commands.CreateCellFromTempla teCommand.Execute(CommandContext context)
at Ans.Core.Commands.Concurrency.CommandWorkUnit.exec uteInContext(CommandContext subContext, IExecutionEngineCallback tracer)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.doExecu te(IExecutionEngineCallback executionEngine, CommandContext subContext)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.Execute (IExecutionEngineCallback executionEngine, Boolean dontCatchExceptions)
--- Ans.Core.Commands.CommandFailedException: Root element is missing.
Command: CreateCellFromTemplate(Template="/Schematic/CellTemplate:EngDataCellTemplate", Name="Engineering Data", System="/Schematic/System:SYS", UpstreamCells=[], AllSystemProperties={"SystemType": ["Static Structural (ANSYS)"], "SystemTypeAbbreviation": ["SYS"], "Solver": ["", "ANSYS"], "PhysicsType": ["Structural"], "AnalysisType": ["Static"], "SolverType": ["ANSYS"], "SystemTypeName": ["Static Structural (ANSYS)"], "UniqueSystemDir": ["SYS"]})
at Ans.Core.Commands.CommandAsyncResult.RethrowFailur eException()
at Ans.Core.Commands.CommandAsyncResult.Wait(Int32 milliSecondsTimeout, Boolean exitContext)
at Ans.Core.Commands.Core.OutputArgBase.Wait()
at Ans.ProjectSchematic.DataHandling.ProjectWrapper.C reateCellFromTemplate(ICellTemplate template, String name, ISystem inSystem, Dictionary`2 sources, Dictionary`2 systemProperties)
at Ans.ProjectSchematic.DataHandling.SystemBuilder.In sertNewFromTemplate(ICellTemplate newCellTemplate, String name, ICell beforeCell, Dictionary`2 cellSources)
at Ans.ProjectSchematic.DataHandling.DataSourceCalcul us.CreateSystem(String name, ISystemTemplate sysTemplate, IList`1 cellsToShare, IList`1 cellsToUse, ISystem systemToPositionBy, PositionType posType, Boolean createPreceding)
at Ans.ProjectSchematic.Commands.CreateSystemCommand. Execute(CommandContext context)
at Ans.Core.Commands.Concurrency.CommandWorkUnit.exec uteInContext(CommandContext subContext, IExecutionEngineCallback tracer)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.doExecu te(IExecutionEngineCallback executionEngine, CommandContext subContext)
at Ans.Core.Commands.Concurrency.BaseWorkUnit.Execute (IExecutionEngineCallback executionEngine, Boolean dontCatchExceptions)
--- Ans.Core.Commands.CommandFailedException: Root element is missing.
Command: CreateSystem(Template="/Schematic/Template:Static Structural (ANSYS)", Position="Default")
at Ans.Core.Commands.CommandAsyncResult.RethrowFailur eException()
at Ans.Core.Commands.CommandAsyncResult.Wait(Int32 milliSecondsTimeout, Boolean exitContext)
at Ans.Core.Commands.CommandAsyncResult.Wait()
at Ans.ProjectSchematic.Commands.CreateSystemCommand. InvokeAndWait(ICommandContext context, DataReference Template, String Name, DataReference System, List`1 CellsToShare, List`1 DataTransferFrom, List`1 DataTransferTo, Nullable`1 Position, DataReference RelativeTo, Nullable`1 ConnectionMode)
at Ans.ProjectSchematic.DataHandling.Preview.Creation Info.DoCreate(ICommandContext context, IEnumerable`1 cellsToShare, IEnumerable`1 transferFrom, IEnumerable`1 transferTo)
at Ans.ProjectSchematic.Presentation.Schematic.AddSys temFromTemplate(ICommandContext commandContext, PreviewSystemBlock sysBlock, List`1 cellsToShare, List`1 cellsToUse)
at Ans.ProjectSchematic.View.ProjectSchematicViewStat e.<>c__DisplayClass1.<CreateSystemFromPreviewBlock >b__0()
at Ans.UI.UIManager.InvokeOperationCore(String pseudoname, OperationDelegate callback, Boolean allowOSMessages)

[ghorrocks]

If you have an urgent problem contact CFX support. That's what you pay them for.

Try deleting the CFX temporary folder in docs and settings/<user name>/.cfx. Sometimes that clears it.

[gokmenvt]

thanks, it works.

[Yankee]

There's a wiki on the subject on the site of the french ubuntu community :

http://doc.ubuntu-fr.org/ansys_workbench

With those directives no need to register manually the libes after a first installation, the workbench works directly and Design modeler also. Concerning the "meshing" product, it opens a window, but stops when it tries to collect information about the geometry, with the message (in the shell) :
"A fatal error has occurred within AnsysWBU.exe and it must be closed..."

It's a little more promising than the preceding step, nevertheless doesn't work...

Maybe it's related to remaining errors during installation (stored in ansys_inc/install.err):

[: 326: /data/export/ansys_inc/v121/aisol/dll/linia32/libans.common.clrhostmonou.so: unexpected operator
[: 326: /data/export/ansys_inc/v121/aisol/dll/linia32/libans.common.controlsu.so: unexpected operator
[: 326: /data/export/ansys_inc/v121/aisol/dll/linia32/libans.graphics.controlsu.so: unexpected operator
[: 326: /data/export/ansys_inc/v121/aisol/dll/linia32/libans.graphics.graphutilityu.so: unexpected operator
(last line repeated 9 times)...

[jsm]

Hi,

Could anyone able to run ansys 12.1 design modeler & ansys meshing in ubuntu 9.1?

Please give me the guidelines. Still searching for way.

[rafasdo]

Hi mhsr!

Did you make the test in openSuse x86_64? I ask because here (openSuse 11.2 x86_64) the DesignModeler don't work. The funny thing is that it works in openSuse 10.2. What do you think?

Originally Posted by mhsr

I can't believe it's that simple. Ever since I've got a grip on the first Service Pack of v12, I tried to make the workbench run on debian. Thanks, Yankee, for the hint about the English locale. During the last weeks I was getting quite annoyed about SIGSEVs reported by the starting (and eventually crashing) application. My locale was set to de_DE@euro (use the -L parameter for non-English GUI text strings, e.g. runwb2 -L de) and on my second test system C - what a surprise, the must-have-locale for CFX 5.x...

To make the design modeler work you need the register the libraries that are logged in /ansys_inc/install.err. The errors are debian specific:

* debian/lenny: you need a working 'arch' command, there's none shipped in lenny, go get yourself a coreutils.deb from squeeze or something similar

* the registering application uses the recent Workbench(1) which complains about missing libComponentSystem.so because the workbench script (found in /ansys_inc/v121/aisol/workbench) uses 'uname -i' to determine on what kind of platform it is run. debian's uname returns 'unknown' when using the '-i' parameter. As a workaround change the workbench script in
line 86
< if [ 'uname -i' = "i386" ]; then
> if [ 'uname -m' = "i686" ]; then
and
line 98
< elif [ 'uname -i' = "x86_64" ]; then
> elif [ 'uname -m' = "x86_64" ]; then
After that you'll have to register the mentioned libraries manually. You will find the needed command lines in /ansys_inc/install.err

* debian also provides a rpm-package, if you don't want the installer/configuration to complain about the missing 'rpm' command

Tested the DesignModeler in Workbench2 on debian/squeeze/i686 some minutes ago, it works really fine. Going to check x86_64-platform and some other non-RHEL/SUSE-distros later

So, thanks again, Yankee.

[chatelain]

Originally Posted by rafasdo

Hi mhsr!

Did you make the test in openSuse x86_64? I ask because here (openSuse 11.2 x86_64) the DesignModeler don't work. The funny thing is that it works in openSuse 10.2. What do you think?

Hi rafasdo,

DesignModeler don't work in OpenSuse 10.3 x86_64

[irw]

I’ve made some progress getting Ansys 12.1.1 Design Modeller working under Debian Linux Etch. I've now got the Design Modeller component functioning well. [EDIT, 2009/03/16: and have now got the Meshing tool to work.] I have seen it working in Debian Squeeze but with occasional lock-ups. I cannot get this to work in Debian Lenny.



For reference, the procedure I have followed is:

• Start by checking that the following dependencies installed on all of the computers where ANSYS products are going to run:

aptitude install mesa-utils gamin

• Also, ensure that the rpm package is not installed.

aptitude remove rpm alien

• The install scripts use the "/bin/uname -i" command which does not work in Debian so following the discussion on the French Ubuntu page:

su
mv /bin/uname /bin/uname2
cat << EOF >/bin/uname
#!/bin/bash
if [ "$1" ="-i" ]; then
   echo `uname2 -m | sed -e 's/i686/i386'`
else
   uname2 $@
fi
EOF
chmod +x /bin/uname

• If your version of Debian doesn't ship with the "arch" command, then you either need to find and install a copy of coreutils with "arch" included or you need to create another script or alias to make "arch" return the same result as "uname -i".

su
cat << EOF >/bin/arch
#!/bin/bash
uname -i
EOFchmod +x /bin/arch

• Also,create a /usr/bin/rpm script as that returns your version of glibc (you can find the glibc version in Debian using ldd --version):

#!/bin/bash
echo glibc-2.10.2-6

Don't forget the chmod +x /usr/bin/rpm.

• Now, install the ANSYS License Server if you haven't done so already.
• The Linux_x64 packages for ANSYS WORKBENCH, CFX and FLUENT were downloaded from the customer portal.
• A temporary directory was created: fluent12.1
• cd fluent12.1
• All of the files were extracted to fluent12.1.
• The fluent12.1/INSTALL script was ran.

Some of the shared-object libraries are actually windows Dynamic Link Libraries and need to be registered. If the commands that register the various libraries in .../v121/aisol/dll/linx64/ fail during install (see install.err) then they can be ran manually once the LD_LIBRARY_PATH has been set correctly:

find/ansys_inc/v121/aisol/dll/linx64/ -iname "*.so*" | \
  sudo xargs /ansys_inc/v121/aisol/workbench \
  -cmd/ansys_inc/v121/aisol/mw/bin-amd64_linux_optimized/regsvr32 -c -nodisplay

Note,it is important to run the xargs command as super-user. Without the sudo command the regsvr32 command says it succeeds but actually does nothing.

Finally, Debian is stricter than RedHat about memory deallocation so to stop crashes due to "free(): invalid pointer" you need to set the MALLOC_CHECK_ environment variable to 0 (or 1 if you want the warning message still). I start workbench using the following script:

#!/bin/csh
if ($?LD_LIBRARY_PATH == 0 ) setenv LD_LIBRARY_PATH ""
setenv LD_LIBRARY_PATH /depot/localapplic/opt/fluent/v121/all_libs/
setenv MALLOC_CHECK_ 0
 
/ansys_inc/v121/Framework/bin/Linux64/runwb2 -oglmesa
setenv MALLOC_CHECK_ 2
 
 
setenv LD_LIBRARY_PATH ${OLD_LD_PATH}
unsetenv OLD_LD_PATH

I found it useful to create a directory of all the shared libraries used by workbench to help with diagnosis. Most of the libraries needed are supplied by ANSYS in various lib folders through the install path. This is not necessary as the workbench script sets the LD_LIBRARY_PATH variable and LD_PRELOAD variables for you, however you may find this useful.

mkdir/ansys_inc/v121/all_libsfind /ansys_inc/v121 -iname'*.so*' | sudo xargs -IFILE ln -s FILE /ansys_inc/v121/all_libs/
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/ansys/inc/v121/all_libs

[irw]

The above method seems to work on three of our machines running Debian Etch, but one of the machines has Debian Testing (Squeeze) and this hangs when "suppressing a body" or closing design modeller.

[rafasdo]

Hello, irw

I stopped of try use the openSuse for run DesignModeler. So, I tried to use the method above in the Debian Lenny 5.0.3 but too I have not had success with DesignModeler. Appear the following errors:

a)When I run with common user

Fatal Error: Could not copy registry file from /opt/ansys_inc/v121/aisol/mw/system/hklm.bin to /opt/ansys_inc/v121/aisol/WBMWRegistry/hklm_amd64_linux.bin.monteserrat.19553_1.

b)When I run with user root

Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

PS: Here I had install the libmotif3 because I didn't found the libmotif4. The version of the glibc is 2.7-18. What do you think?

[irw]

Hi hsr,

Yes, I have seen your first error too. However this only occurred the first time. So, for the first time run as super-user and after this you can continue as a normal user. By default, the Ansys directory has bad read-write permissions for all users when first installed, and for some reason it wants to write to the install directory.

I have just checked the distribution of the machines and they are actually running Etch (i.e. old-stable) and not Lenny (current stable). Apologies for the confusion.

We have libmotif4 from as part of another software. (EDIT: I have seen that this actually prevent DesignModeller from closing correctly so use libmotif3 instead)



EDIT: I have updated the method described above.

[irw]

I followed the same installation method as described above in Ubuntu Karmic (i.e. fixed the rpm and uname commands and made sure the DLLs were registered correctly). However, I also needed to follow the instructions given in the installation section of the Ansys Workbench manual, i.e. create the correct X11 and OpenGL links.


Workbench looks for various X11 and OpenGL shared objects without the version number on the end so make sure run the following commands, where #### is the version installed on your system:


sudo aptitude install libmotif3
ln -sf /usr/lib64/libGLU.so.##### /usr/lib64/libGLU.so
ln -sf /usr/lib64/libXm.so.#### /usr/X11R6/lib64/libXm.so
ln -sf /usr/lib64/libXp.so.#### /usr/X11R6/lib64/libXp.so
ln -sf /usr/lib64/libXt.so.#### /usr/X11R6/lib64/libXt.so
ln -sf /usr/lib64/libXext.so.#### /usr/X11R6/lib64/libXext.so
ln -sf /usr/lib64/libXi.so.#### /usr/X11R6/lib64/libXi.so
ln -sf /usr/lib64/libX11.so.#### /usr/X11R6/lib64/libX11.so
ln -sf /usr/lib64/libSM.so.#### /usr/X11R6/lib64/libSM.so
ln -sf /usr/lib64/libICE.so.#### /usr/X11R6/lib64/libICE.so
ln -sf /lib64/libgcc_s.so.#### /lib64/libgcc.so

After this, workbench runs smoothly.


Installing the hardware accelerated NVIDIA driver (nvidia-glx) broke DesignModeller and the Meshing tool but the open-source NV graphics drivers built into Ubuntu seem to work fine.


Also, I note that libmotif4 prevents DesignModeller from exiting correctly. This is not open-source or part of Ubuntu anyway, but you may have it installed as part of other software.

[mechanicaldesign]

Hi all,

Yours advice is very useful to understand how can be made to work Workbench on uncertified distro. However, I installed ANSYS 11 64biti on CentOS5.4 64biti. Everithings works ok, but when I want to launch workbench, I encountered the next message:

>su
>password
>./runwb
>./runwb: line 24: 5827 Segmentation fault $DS_INSTALL_DIR/workbench -StartPage $*

Because ANSYS is made to work well for Red Hat, means that on CentOS must work well to. But how I see is not so simple to made it work on recomanded distros ( CentOS, RedHat). I think missing some library from my installation, these is the reason because I cant use it.

What means this error ? How I can fixed? Have somebody any ideea ?

I waiting much early is possible your suggestion, ideea or opinion referring to my problem.

Thank you very much for support and understanding.

Best regards.