Use the current CivilFEM online help and official CivilFEM resources as primary references. For licensing, verify the CivilFEM Apps entitlement, Workbench compatibility and the current CivilFEM Apps licensing guidance before using lower-level LM-X diagnostics.
ACT extension installs but fails to load because licensing source and license system are mismatched
CivilFEM Apps for Ansys WorkbenchSupport guidance
When an ACT extension is installed but does not load, first verify that the Workbench extension and the license source point to the same valid licensing system. Check local versus server license configuration, remove stale entries, and confirm that the customer has a CivilFEM Apps entitlement.
Symptoms
A temporary network license had to be reissued after the host information was found to be wrong, and the customer then requested a permanent license once the EULA and payment were completed.
After adding the license, the CivilFEM bar/menu did not appear in the main menu, and activating the tool did not show modules.
CivilFEM APDL runs, but the ACT extension in ANSYS Workbench reports that no CivilFEM license is available.
CivilFEM appeared to interfere with ANSYS Workbench or multiPlas usage, and even disabling the license server did not fully stop the conflict.
Each code check calculation uses a CivilFEM license, licenses are not returned after CivilFEM and ANSYS close, and the class cannot continue once the pool is exhausted.
Likely causes
ACT-based developments are not supported in Ansys Student, so the student path is blocked by platform limitations rather than a simple activation issue.
CivilFEM loading behavior or installation state was conflicting with the original ANSYS installation needed by Workbench/multiPlas; later messages suggest installation corruption or ANSYS package changes may have broken the connection.
Either the launcher was not run with sufficient permissions, the installation was incomplete, or the GRN menu files were not being loaded correctly.
Likely one or more of the following: case-sensitive password mismatch, the license service not running, or firewall interference with the LM-X service. This is based on vendor troubleshooting instructions in the thread.
Not established in the block; support was still asking whether the customer was using evaluation, Store, or web distribution.
Recommended resolution
Confirm that the license also covers ACT and provide the portal or direct download instructions for the relevant add-on package.
Confirm the exact distribution channel and evaluation status, then continue installation and license troubleshooting based on that variant.
Confirm the source of the app, verify supported ANSYS versions, and if needed generate a trial/license from host information and screenshots.
Confirm where the app was downloaded from, verify the correct ACT package, and either use the trial package or install the LM-X license server and point the client to it.
Confirm whether the customer already has a CivilFEM ACT license; if not, generate the needed license and keep the install documentation available.
Do not run `~cfactiv` before launching the calculation if it is not needed. Use the CivilFEM Administration Utility `Release Own` or the APDL `sys` call with `releaseown` if license release is required after each run.
ACT shell reinforcement depends on element orientation
CivilFEM Apps for Ansys WorkbenchSupport guidance
For shell reinforcement results in Workbench, treat element orientation and local axes as part of the model definition. Ask for the element orientation, shell normal and reinforcement direction, then reorient the mesh or redefine the reinforcement direction before comparing results.
Symptoms
A user asks how to combine seismic loads in three directions with SRSS when only linear combination is exposed.
A user asks whether inconsistent shell element orientation from automatic meshing affects reinforcement calculation results.
A user asks whether they can check structures with other codes or standards beyond the available options, and whether users can add new codes themselves.
In the Workbench workflow, the Mechanical package/red icon or the expected Edit option is missing, preventing modeling through the expected interface.
The app could not read the generated result files for design.
Likely causes
CivilFEM Apps do not allow user-defined code additions; only the implemented code set is available.
Reinforcement definition and related checks are orientation-dependent in the ACT/Workbench workflow.
Some structural elements were not fully or correctly defined for the check being performed, or the reinforcement/material setup was incomplete.
The block does not confirm a root cause; the issue may be a compatibility or integration mismatch between CivilFEM and the Workbench setup.
The MAPDL model was using non-MKS units, so the generated `.rst` files were not compatible with what the app expected.
Recommended resolution
Compare the installation against the referenced tutorial and verify that the Workbench/CivilFEM integration is complete and correctly exposed in the UI.
Perform the SRSS combination in ANSYS, then use the combined file as the CivilFEM dataset; APDL load case commands were suggested.
Review the model definition and reinforcement settings, then request a minimal reproducible model or the original project file for deeper investigation.
Standardize the MAPDL model to MKS units before generating the results, then rerun the workflow.
Use Element Orientation and verify mesh orientation consistency before running reinforcement checks.
Use the MAPDL environment where more codes are implemented, or request development for the desired code if it is not already available.
CivilFEM ACT apps are not available in the restricted area
CivilFEM Apps for Ansys WorkbenchSupport guidance
If apps are missing from the restricted area, check the portal account type, product entitlement, maintenance status and whether the user is looking under the right product. Do not treat it as a solver problem until access rights are confirmed.
Symptoms
After installation, the user sees only one menu entry and not the expected CivilFEM Workbench menu option.
In ANSYS Workbench, the user cannot share the model between Static Structural and CivilFEM Check & Design, and the Check & Design tool shows black crosses instead of a usable module.
The installer reports that ANSYS is not installed, even though the user says ANSYS is present.
The student-version installer fails during installation, then works after the installer is moved to another location.
The user cannot find the CivilFEM apps for ANSYS Workbench in the restricted area and asks where to download them.
Likely causes
Folder permission or administrator-rights issue on Windows.
Likely an access or distribution issue rather than a product defect. Support responds by providing direct download material instead of relying on the restricted area.
The block indicates ANSYS 2022 R1 was not supported by the CivilFEM ACT at that time.
The block suggests the CivilFEM extension may not be installed or activated correctly, or the wrong Ansys version/menu state is being used.
The wrong ANSYS component was installed or the ANSYS and CivilFEM versions did not match. The thread later states that CivilFEM for ANSYS needs ANSYS Mechanical APDL, not Workbench, and that the versions must align exactly.
Recommended resolution
Check whether the expected menu is present, disable the CivilFEM extension to compare behavior, and reinstall the extension if needed.
Move the installer to a different location and retry with appropriate permissions.
Share the ACT package and installation guide directly to the customer, outside the restricted download area.
Use a supported ANSYS version from the thread, or wait for the ACT compatibility update before relying on the workflow.
Verify the exact ANSYS release and install ANSYS Mechanical APDL, then reinstall the matching CivilFEM release.
CivilFEM Apps V6 compatibility question for ANSYS Workbench versions
CivilFEM Apps for Ansys WorkbenchSupport guidance
For CivilFEM Apps V6 compatibility, match the CivilFEM Apps release to the supported Ansys Workbench release. Avoid mixing old apps with unsupported Workbench versions; use the current product compatibility table when answering.
Symptoms
A customer asked which ANSYS Workbench versions CivilFEM Apps V6 supports.
After reducing mesh size, merging nodes, checking boundary conditions and material properties, and trying a quadratic mesh with the same time step as the reference model, the analysis still failed to converge.
Likely causes
Likely model setup or analysis-sequence issue rather than a pure licensing problem. The support replies point toward mesh, reinforcement, thermal setup, and material-property handling as the areas to review.
Version compatibility uncertainty between the CivilFEM Apps release and ANSYS Workbench releases.
Recommended resolution
Compare against the sample model, review the thermal-loading/material-property workflow, and continue the technical follow-up meeting while the temporary license is extended if needed.
Confirm the supported range from the thread: V6 adds support for ANSYS 2022 R1 and R2, while earlier supported versions remain supported from 2019 R1 onward.
Windows 11 23H2 compatibility needed for an ANSYS/CivilFEM software inventory
Cross-product / general CivilFEMSupport guidance
Current CivilFEM products support Windows 11 on 64-bit systems. New versions are 64-bit only. Mention product-specific compatibility and avoid implying support for new 32-bit installations.
Symptoms
A customer requested confirmation that several installed ANSYS/CivilFEM versions were compatible with Windows 11 23H2 before an OS rollout.
Likely causes
This is a compatibility-review request rather than a defect. The reply indicates that older versions are not officially certified, while current 2024 versions are supported/tested.
Recommended resolution
Provide a version-by-version compatibility statement and recommend the newer supported releases for Windows 11.
