Force and moment values reported incorrectly in result files

Problem

Strange or unexpected force and moment values were extracted from result files without an obvious error message

Possible cause

Not established in the block; support could not reproduce it and asked for a log file

Solution

Collect log files, confirm the exact v11 patch level, and verify whether the issue is reproducible on the target environment

Validity context: Historical; first appears in 2013 and is still being discussed in February 2014

Portable Marc license file was generated with an incorrect expiration date

Problem

A portable installation could not use the expected license and was behaving as if the license file were invalid or misgenerated

Possible cause

The license file itself appears to have been generated with the wrong validity data, specifically an incorrect expiration date

Solution

Replace the old license file with a regenerated one from the vendor and restart the service or machine after installation

Validity context: Late 2014, with a fix still pending through early December 2014 and then delivered once the replacement file arrived

CivilFEM client starts in Student mode instead of using the server license

Problem

CivilFEM launches but only offers or uses the Student option, connects to `localhost`, and does not expose the expected University/server license behavior

Possible cause

The client is not pointed at the license server, and the server side may not be configured to allow remote clients

Solution

Enter the server name instead of `localhost` on the client, and configure the server’s Admin Control Center to allow remote client access and the desired user restrictions

Validity context: December 2014

CivilFEM/Marc fails to launch on some machines after installation

Problem

Installation completes, but the program later shows a Windows error on launch on some machines; the same machine can work after moving it to a different network path and reinstalling

Possible cause

The thread points first to network and port handling, then narrows toward SafeNet driver detection/configuration; missing updates were also considered, but not confirmed as the root cause

Solution

Reproduce on a clean machine, verify SafeNet driver configuration, check the network path/port handling, and if needed reinstall or repair the driver rather than the entire suite

Validity context: Late December 2014 to early January 2015

CivilFEM license server deployment constraints on Linux, VM, and USB dongles

Problem

A customer asks whether the CivilFEM license server can run on Linux, whether a VMware-hosted server can reuse the same USB dongle, and whether a dongle can be avoided entirely

Possible cause

The questions are about product/platform support limits rather than a defect in the software itself

Solution

Use a Windows host for the license server, test USB passthrough only if the VM layer supports it, and consider machine-locked licensing as an alternative if the dongle is a blocker

Validity context: February 2015

Student installer appears frozen but eventually completes

Problem

The CivilFEM student installation seemed to hang immediately after starting and the user reported no progress for a long time

Possible cause

The installer was still performing initialization or data collection rather than truly failing

Solution

Advise waiting longer before treating it as a failure; the user later confirmed it eventually finished after a long wait

Validity context: November 2015

License file does not match the machine host identifier

Problem

After installing a license file, the program showed a license error; later checks indicated the machine identifier in the license file did not match the actual machine identifiers

Possible cause

The license file was generated for the wrong machine identifier, likely due to a MAC address mismatch or a change in the active network adapter

Solution

Regenerate the license for the correct host identifier and verify the active network adapter and power-management settings before issuing the file

Validity context: December 2015

Student license rejected with feature include-list error

Problem

A student user reported an error stating the user or host was not included for the licensed feature

Possible cause

The license entitlement had not yet propagated, or the user needed to be added to the feature include list

Solution

Request inclusion in the program list and allow time for the license server registration to propagate

Validity context: November 2015

Marc solver returns error 67 after CivilFEM/Marc installation

Problem

The user reports an "error 67 on Marc solver" after installing Marc and CivilFEM and clicking solve

Possible cause

Not stated in the block. The only visible context is that Marc and CivilFEM were both installed, so the issue may involve installation or licensing, but that is not confirmed

Solution

No resolution is provided in the block. The next step would be to collect the exact solver log, installation state, and any license-related messages

Validity context: April 18, 2016

Silent CivilFEM installation is blocked by the LM-X license dialog

Problem

A silent deployment reaches the license configuration step and pops a license setup dialog, which breaks unattended installation flow

Possible cause

The installer requires explicit license-configuration input during setup instead of accepting a fully unattended path

Solution

The suggested workaround was to add a yes/no branch in the installer and use the environment-variable method when the answer is no; the thread later mentions a new installer and service-pack update that includes the fix

Validity context: May 23, 2016 to June 8, 2016; the guidance is tied to the installer version current at that time

Student CivilFEM on Windows XP cannot start LM-X licensing

Problem

The LM configuration tool does not open correctly, and launching the licensing executable reports that it is not a valid Win32 application

Possible cause

The operating system is unsupported for the LM-X component

Solution

Move the installation to a supported Windows version; one reply also suggests trying the `LMX_LICENSE_PATH` environment variable, but the core answer is that Windows XP is no longer supported

Validity context: May 30, 2016 to May 31, 2016

Marc license file was wrong or mismatched, causing installation/runtime errors

Problem

After reinstalling Marc and entering the license file, the user still sees an error message; later the issue resolves and meshing works again

Possible cause

The license file path or format was wrong, or the administration department had sent an incorrect file initially

Solution

Reinstall with the correct file type and keep the file at the path selected during setup; use the `MSC_LICENSE_FILE` environment variable for local-file configuration; the thread ultimately states the administration department sent a new file

Validity context: June 9, 2016

CivilFEM 2016 SP1 launches with an error after unattended installation

Problem

The unattended install completes, but opening the desktop shortcut returns an error; the start-menu shortcut also looks broken or generic even though it points to the right target

Possible cause

A local machine-specific environment or configuration problem after deployment; the block does not isolate a single failing component

Solution

Clear the CivilFEM user configuration cache, verify Windows updates and OS bitness, compare the behavior on other machines, and continue with remote support if it reproduces

Validity context: June to July 2016, tied to CivilFEM 2016 SP1 and internal version 0201

Mesh generation problem after CivilFEM/Marc setup

Problem

A user reports a mesh problem after installing the software and loading a `.dat` file into Marc

Possible cause

Unknown from the excerpt; the block only confirms a mesh-related failure during setup or use

Solution

Review the attached image, reproduce the install/import sequence, and request the exact error text if the screenshot is insufficient

Validity context: Late July 2016

Floating MARC/Mentat license cannot be checked out because the server is unreachable or misconfigured

Problem

Diagnostics show MARC/Mentat features failing to check out because the license server is down, refusing connections, or being addressed by the wrong host or port

Possible cause

The server name in the license file does not match the real server, the server is not running, or the port/host in the license path is wrong

Solution

Verify the real server hostname and port, correct the license file if needed, and collect the full Flex-LM status, diagnostics, and view logs if remote access is not possible

Validity context: August 4, 2016; historical only

License model mismatch between server-based floating use and local dongle use

Problem

The customer cannot use the provided license in their virtual environment and insists that the deployment needs to work with a client-side dongle instead of a server-hosted license

Possible cause

The parties are referring to different license models, and there is also a virtualization constraint around USB passthrough for the dongle

Solution

Confirm in writing whether the target is a floating server license or a dongle-locked local license, then issue the matching file and installation instructions for that model

Validity context: September 9 to September 27, 2016; historical and specific to that deployment

CivilFEM trial reports "product not selected" after installation

Problem

After installing the trial and starting the license service, the application throws a security error stating that no CivilFEM product is selected

Possible cause

The license server is not running or the client is not configured to look for the server license

Solution

Verify that the license service is running, confirm the client points to the correct server, and follow the installation guidance referenced in the reply

Validity context: September 29, 2016; historical only

Opening a saved study case crashes or fails in the CivilFEM Advanced workflow

Problem

A specific study case causes a fatal crash or cannot be opened, and the user reports it after launching the program and opening the dataset

Possible cause

The block does not prove a software defect; the failure could be file-specific or related to how the data was created

Solution

Reproduce the issue with the exact file and steps, then forward the case to development if it can be reproduced

Validity context: August 10 to August 18, 2016; historical only

Macro replay creates points in the wrong coordinate system

Problem

A macro recorded while a custom Cartesian coordinate system is active replays in Python but creates the points in the default global system instead of the active one

Possible cause

The replay path may not be preserving coordinate-system context, but the block does not prove whether this is a product defect or a usage issue

Solution

Request exact reproduction steps and compare the recorded macro against the Python replay to isolate where the coordinate context is lost

Validity context: September 16 to September 19, 2016; historical only

CivilFEM/Marc freezes or crashes in results, especially when loading files

Problem

The application often froze or crashed in the results area, leaving the mouse running continuously until forced shutdown

Possible cause

Unknown from the block. The thread only shows repeated crashes and a request for a reproducible model

Solution

Collect a reproducible project or model and inspect the crash state; the block does not show a confirmed fix

Validity context: A 2016 support thread; no durable root cause confirmed in the provided material

Student/license mix-up and post-install behavior confusion

Problem

A student license worked while the lecturer license did not, and the update behavior was inconsistent after reinstall/reboot

Possible cause

The block does not confirm whether the issue was license type, node-locked behavior, update state, or process conflicts

Solution

Need a clean comparison of the working and failing license setup, plus the exact install state after reboot

Validity context: Only seen in the November 2016 lecturer-license thread

Overlapping license files caused one seat to disappear

Problem

A license server view showed inconsistent recognition of the available licenses; one view indicated two files while another appeared to show only one, and a third license could not be started

Possible cause

The license files were generated in a way that caused one license to overlap another

Solution

Replace the prior set with a newly generated license file that contains the full license count

Validity context: Confirmed in the 2016-11-30 thread and acknowledged as fixed by 2016-12-12

CivilFEM crashed when opening the folders explorer

Problem

CivilFEM randomly crashed when opening its folders explorer, including during a live presentation

Possible cause

The support response points to an operating-system and privilege issue rather than a reproducible application defect

Solution

Run CivilFEM as administrator; if needed, reinstall Windows or test on another computer to reproduce; later guidance also mentions a read-only documentation folder as a workaround

Validity context: Reported on 2016-12-02, with follow-up replies the same day

CivilFEM Spectra launcher and GUI problems on Windows 7

Problem

The user could not submit a batch job through the new launcher, the input macro caused an error, and a Spectra-by-code GUI would not behave correctly

Possible cause

The launcher issue is linked to a known 17.1 problem fixed in a later service pack, while the GUI issue is described as a missing-library or privilege problem on Windows 7

Solution

Use the documented workaround, wait for the service pack, run with administrator privileges, and if needed install the missing Microsoft redistributables

Validity context: Confirmed across 2016-12-27 to 2016-12-29

LM-X License Server Client fails to open because Java/JAR handling is broken

Problem

LM-X License Server Client fails to open because Java/JAR handling is broken

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

Service Pack update download completes but nothing happens afterward

Problem

Service Pack update download completes but nothing happens afterward

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

CivilFEM license-server OS compatibility question for Windows Server 2008/2012

Problem

CivilFEM license-server OS compatibility question for Windows Server 2008/2012

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

Marc license install/repair fails after hardware change

Problem

After replacing a hard drive, the CivilFEM/Marc license installs via the configuration tool but the Marc license component cannot be repaired or modified through Programs and Features

Possible cause

The Marc component is installed as part of the initial setup and may need a reinstall rather than a repair/modify action

Solution

Reinstall the Marc-related component rather than relying on repair/modify, then verify the CivilFEM license remains intact

Validity context: March 3, 2017

Marc/MSC download blocked by gateway antivirus

Problem

A student user can download CivilFEM and the student license but cannot download the Marc executable because a gateway antivirus alert blocks it

Possible cause

The block indicates a false positive on the provider or gateway side rather than a confirmed product defect

Solution

Offer an alternate temporary download URL packaged as ZIP and confirm whether the user can retrieve it successfully

Validity context: April 27, 2017

Marc/Mentat not detected correctly by CivilFEM 2016

Problem

CivilFEM 2016 reports that the MSC product is not recognized even though Marc is installed in the same directory

Possible cause

The block suggests a detection bug or a configuration mismatch where CivilFEM is picking up the wrong Marc license file type

Solution

Check the CivilFEM-detected MSC version in the configuration options and confirm the correct license file type is used for Marc/Mentat

Validity context: April 28, 2017

CivilFEM installation fails with no visible reaction on a Chinese technician workstation

Problem

The technician reports that Marc2016 installs with an error after selecting the .dat file, while CivilFEM2016 launches with no reaction at all after antivirus and firewall are disabled

Possible cause

The block does not confirm the cause; likely installation or environment prerequisites are missing, but the exact blocker is not stated

Solution

Use remote support to inspect the machine state, confirm prerequisites, and compare the installer behavior step by step against the installation manual

Validity context: May 25-26, 2017

Student version does not recognize the Marc component after installation

Problem

A student installation completed, but the software did not recognize the Marc program or behaved as if the student version was not working

Possible cause

Support indicated this behavior was tied to a known bug fixed in Service Pack 5

Solution

Update to Service Pack 5 and retry; if the issue remains, reopen with the same thread and screenshots

Validity context: Mid-2017; explicitly linked to the SP5 release window

Student installation aborts early on Windows 10

Problem

The Marc and CivilFEM installers stopped or vanished at different stages without a clear error message on Windows 10

Possible cause

Not established in the block; support suggested checking installer integrity, Windows updates, antivirus/firewall interference, and using a remote troubleshooting session if needed

Solution

Re-download the installer, ensure Windows is fully updated, check security software interference, and gather screenshots if escalation is needed

Validity context: June 2017

License server and virtual-machine licensing migration question

Problem

A customer asked how to move CivilFEM licensing to a virtual machine, whether another host ID was needed, and how USB dongle licensing should be set up

Possible cause

No defect was identified in the block; this is a licensing deployment/configuration issue

Solution

Follow the support guidance in the thread: virtual server licensing is supported with a physical security dongle in the relevant setup, LM-X license server placement matters, and administration is needed for the license change

Validity context: July 2017

Rigid body modes caused by disconnected mesh and free nodes

Problem

Solving produced a rigid-body-type error, and the user could not obtain a congruent mesh even after reducing mesh size

Possible cause

The model had unconnected nodes between columns and beams, plus other free nodes and some distorted elements

Solution

Merge the relevant nodes, inspect free nodes with the check-nodes tool, and consider glue contacts or contact pairs instead of relying only on local mesh controls

Validity context: Late July to early August 2017

File cannot be opened or resaved in the older version after 2017 edits

Problem

The recipient could not load an attached file after it had been modified in a newer CivilFEM version, and expected it to be resaved for an older version

Possible cause

The block states that documents created with newer features cannot be saved back to an older version format

Solution

Keep the working file in the same version lineage, wait for the original editor to return, or move all parties to the newer release rather than trying to down-save

Validity context: 2017 release window

Student license stops being recognized after previously working

Problem

A student reported that CivilFEM had worked previously, then suddenly no longer recognized the license

Possible cause

Not established in the block; only a replacement student-universal license was mentioned internally

Solution

Verify whether the current student license file matches the installed version and whether the license needs replacement or reinstallation

Validity context: August 2017

CivilFEM 2017 student and commercial license setup is confusing

Problem

The user asks whether professional and student CivilFEM can be installed as independent programs, and how to manage both working modes

Possible cause

The installer is shared for CivilFEM while the active license changes by license file; the thread also references policy differences between student and commercial use

Solution

Install CivilFEM once, then add the relevant student or commercial license through the Administration Utility and verify which license is active when launching

Validity context: Aug 16-17, 2017; references CivilFEM 2017 installation and license-file handling

Student-license activation fails because the clock reset utility cannot complete

Problem

After installing the student license, the user gets an error and CivilFEM closes; the clock-reset utility does not complete successfully

Possible cause

The activation utility cannot reach a remote time service, likely because UDP port 123/NTP is blocked, the utility is not elevated, or the network path is being filtered

Solution

Run the reset utility as administrator, verify the system clock, check firewall rules for UDP 123, and if needed test with firewall temporarily disabled and capture the output

Validity context: Aug 24-31, 2017; explicitly references `lmxresetsystemclock.exe` and a CivilFEM 2017 install path

Mesh or solve requires elevated launch on first use after install or update

Problem

CivilFEM mesh/solve fails with an MSC-related launch issue unless the program is started with administrator rights

Possible cause

Windows UAC or permissions appear to interfere with the first mesh/solve execution after install or update, although support also says the license is local and no server setup should be needed

Solution

Check whether UAC is enabled, generate the Administration Utility report, and verify whether the issue happens only on the first run after install or updates

Validity context: Sep 6-7, 2017; references CivilFEM 2017 and a comparison to CivilFEM 2016

Thermal stress results from solid-derived shell vertices include free expansion

Problem

Thermal-load cases produce very large forces and moments when shell vertices are generated from solid elements, even though the physical strain and stress should be small

Possible cause

The described workflow seems to use total nodal displacements, including free thermal expansion, when deriving shell-vertex forces from solid elements

Solution

The block does not show a completed fix; the case was escalated for technical support review, so a supported workaround or product guidance is still needed

Validity context: Sep 18-20, 2017; presented as an unresolved technical support question

CivilFEM license server and dongle migration to a new VMWare host

Problem

Whessoe needs to confirm the current CivilFEM licensing situation and move a dongle-based floating license server to a new VMWare host

Possible cause

The prior license deployment was not fully documented after staff turnover, but the block says the license is tied to the USB dongle and can be moved if USB passthrough works

Solution

Plug the dongle into the new server, install the LM-X license server and floating license file there, and verify that VMWare detects the USB device

Validity context: Sep 19-22, 2017; references Windows 7, VMWare, and floating network licensing

CivilFEM 2017 opens incorrectly and crashes during meshing

Problem

The user reports that double-click opening shows a license/GUI-related error, and the application crashes when creating a mesh

Possible cause

The mails point first to a local installation/configuration problem, then to a backend dependency/configuration issue for meshing; support also tests the model successfully on their side, which suggests the issue may be installation- or environment-specific rather than a universal product defect

Solution

Reinstall the software, verify the CivilFEM/Marc configuration, generate and review the installation report, and compare the failing model/settings with a working setup

Validity context: Historical, tied to the 2017 CivilFEM release line

CFVerif requests administrator privileges during execution

Problem

Running CFVerif prompts for administrator credentials, which blocks use in restricted user environments and interferes with editing the installation area

Possible cause

The tool writes results into its installation directory and was designed to run with elevated privileges when installed under Program Files

Solution

Use the documented workaround: copy the installation to a non-Program Files location, apply the patched executable, and run the copied instance from there

Validity context: Historical, specific to CFVerif 17.1

CFVerif manual and installed examples do not match expected chapter list

Problem

The user notices missing chapters and example files in the installed verification package and asks whether this is normal

Possible cause

Support states that the mail originally referenced an extended verification set, while the manual only ships the full integration examples

Solution

Treat the discrepancy as an explanation/documentation issue rather than a product fault; only the subset in the manual is intended for clients

Validity context: Historical, tied to the 2017 verification package content

CivilFEM 2017 meshing problem caused by Marc version detection/configuration

Problem

Meshing failed only in CivilFEM 2017, while older CivilFEM versions worked on the same model

Possible cause

The block points to a Marc version detection problem, possibly due to a missing or improperly detected Marc 2016 installation, or a stale CivilFEM configuration file

Solution

Remove the CivilFEM configuration file, re-detect Marc, reinstall Marc if needed, and if the issue persists use a remote session and generate a report file

Validity context: Strongly time-bound to CivilFEM 2017 and the Marc integration described in 2017

CivilFEM 2017 SP1 license security error when running older cases

Problem

Running some previously downloaded or older cases in CivilFEM 2017 SP1 produced a license security error

Possible cause

The thread suggests a missing MSC license, a license interference issue, or another computer-specific conflict; the report file reportedly looked normal, so the exact cause remained unresolved in the text

Solution

Generate and review a report file, verify the MSC license installation, try running CivilFEM as administrator, and check for interfering MSC license-server software

Validity context: Time-bound to CivilFEM 2017 SP1 and the 2017-2018 support exchange

Online help geometry tab missing

Problem

The user reported that the geometry menu help link was missing and the “press F1” label seemed outdated

Possible cause

The reply says the online help had a missing geometry tab, implying a documentation/help-content packaging issue

Solution

Confirm the help content is deployed correctly and verify the missing geometry section is available again

Validity context: Time-bound to the December 2017 help-content correction

CivilFEM license security error on one machine despite renewal

Problem

A renewed CivilFEM license still triggers a security/error condition on one client machine while other machines appear unaffected

Possible cause

Interference from another MSC license component or a local configuration/permission issue on that specific computer

Solution

Test running CivilFEM as administrator; remove any conflicting MSC license server if present; retry the solver as a workaround if needed

Validity context: January 2018; the thread indicates the issue was not reproducible elsewhere at that time

Provisional license expired during transition to dongle-based licensing

Problem

The user could not continue working because a provisional license had expired while waiting to complete a dongle transition

Possible cause

Temporary license lifecycle during the move from provisional authorization to a dongle-based setup

Solution

Issue the updated license file for the dongle key; the thread also states the newer license can still be used with the earlier version during transition

Validity context: January 2018; the exchange explicitly references a time-bounded provisional license and a year-end license file

License usage logs needed for optimization and analysis

Problem

The user wants CivilFEM license usage logs and asks whether the data can be exported or filtered by date

Possible cause

The LM-X License Server Client exposes raw log data, but not necessarily a ready-made CSV/XLS export workflow

Solution

Use the LM-X License Server Client log file view; raw logs can be reviewed there and any deeper analysis would need external processing

Validity context: February 2018; the conversation is about current access to usage logs at that time

CivilFEM 2017 student version crashes on launch with a development error

Problem

After installation, launching CivilFEM 2017 shows a development error and closes immediately

Possible cause

Not established in the block; support suspected either an environment issue or something requiring more diagnostics

Solution

Generate a report file, try running as administrator, and if needed schedule a remote support session

Validity context: February 2018; the issue persists across multiple follow-ups over several days

Marc solver error 13 after Parasolid geometry import

Problem

The solver throws error 13 whenever geometry imported as Parasolid is used, and the user asks for a basic error list

Possible cause

The input passed to Marc is not correctly defined; the block does not establish a deeper root cause

Solution

Collect more diagnostics and verify the model/setup around the imported geometry

Validity context: February 2018; the issue is described as recurring every time the same geometry workflow is used

CivilFEM network license fails because the client sees the wrong host ID

Problem

The client cannot obtain a license from the server, and the host ID collected by LM-X does not match the host ID encoded in the license file

Possible cause

The machine appears to expose a different MAC address than expected, likely through a virtual adapter or multiplexor driver; firewall or LM-X service state may also contribute

Solution

Regenerate the license for the correct physical MAC address; verify firewall settings; restart the LM-X license service; collect a client report and server log for diagnostics

Validity context: February 2018; the issue is traced across multiple replies until the host-ID mismatch is identified

CivilFEM for Ansys installer and LM-X server download access not visible in portal

Problem

The user cannot find the CivilFEM for Ansys installation files in the portal and asks for the direct LM-X License Server download link

Possible cause

Product-profile separation in the customer portal hides the file from the current account, even though the same license server is used for both products

Solution

Provide the direct download link and confirm whether the installer is already included with the CivilFEM with Marc package

Validity context: February 2018; this is a portal-access issue tied to the then-current product distribution

CivilFEM with Marc installation fails when the install path contains spaces or special characters

Problem

Marc/Mentat would not install or would later fail until the software was moved to a simpler path

Possible cause

The installation path contained spaces or special characters, which the Marc installation and/or launch path did not handle reliably

Solution

Install to a default/simple path such as the standard CivilFEM/MSC location, or place the software on a path without spaces; the block also mentions a virtual-drive workaround, but the final confirmed fix was installing directly on `C:` without appending the path

Validity context: Observed across 2018-02-23 to 2018-02-26, with confirmation that the software worked after the path was simplified

CivilFEM with Marc requires separate Marc/Mentat licensing and server setup, not just the CivilFEM license

Problem

Users expected CivilFEM licensing alone to be enough, but Marc/Mentat could not be used for meshing/solving or the license check boxes did not reflect usable access

Possible cause

The Marc/Mentat license server and its corresponding license file were not installed or not recognized, or the user was expecting the CivilFEM license to unlock Marc as a standalone product

Solution

Install the MSC license server with the correct Marc license file, edit the license file host name as required, verify that the client can reach the server, and confirm that CivilFEM can mesh and solve. If still unclear, generate and review the CivilFEM Administration Utility report

Validity context: Observed from 2018-02-20 through 2018-03-07, with repeated clarifications that the license included with CivilFEM with Marc does not enable Marc as a standalone application

CivilFEM 2018 Beta cannot obtain license because communication to the license port is blocked

Problem

The beta version could not retrieve the CivilFEM license even after installing Marc/Mentat, and the support report indicated a blocked communication path

Possible cause

Firewall or antivirus blocking communication on port 6200

Solution

Allow CivilFEM through the firewall/antivirus and re-test the license connection; if needed, use the report file to verify port reachability

Validity context: Explicitly stated on 2018-03-06 for CivilFEM 2018 Beta

Solver failure caused by processor-count mismatch between license and CivilFEM configuration

Problem

Modal solving failed with a Marc solver error while the license/configuration showed different processor limits

Possible cause

The license allowed 4 processors for one part of the parallel solve while CivilFEM configuration was set to 48, creating a mismatch

Solution

Set the CivilFEM config options to match the licensed processor count, then retest the solve; if it still fails, send the report file

Validity context: Observed on 2018-03-04 to 2018-03-05

Solver failure caused by file name or working-directory path containing spaces or special characters

Problem

Marc returned an unknown error during solve even after the model had been meshed

Possible cause

The working directory path or file name contained spaces or special characters

Solution

Rename the model file and/or move it to a path without spaces or special characters; the thread shows the solve succeeding after changing the filename

Validity context: Confirmed on 2018-03-05

CivilFEM 2018 local license was misconfigured as a server license

Problem

The 2018 license file did not behave as expected until support clarified that it had been changed from server mode to local mode

Possible cause

The license type was changed internally without the recipient being aware, so the configuration did not match the intended use

Solution

Reconfigure the license as a local license through CivilFEM Administration Utility and confirm the intended license mode before deployment

Validity context: Observed on 2018-03-02

CivilFEM beta opens with a graphics/OpenGL compatibility error

Problem

A newly installed beta build fails when opening a new file, with the support thread focusing on graphics detection and 3D rendering problems

Possible cause

The support replies point to an old or basic graphics card, missing driver updates, or remote desktop access preventing hardware acceleration. The thread specifically mentions an OpenGL requirement

Solution

Check the graphics adapter and driver version, avoid running only through remote desktop if possible, and move the install to a machine with a compatible GPU or updated drivers

Validity context: March 21 to March 22, 2018, tied to CivilFEM 2018 beta

Student version crashes on launch around beta/update handling

Problem

The student installation crashes when launching, sometimes described as crashing after idle time or quick interaction, and the user cannot reach any CivilFEM commands

Possible cause

The thread alternates between a missing beta update, missing Windows updates, and a known bug fixed in CivilFEM 2018 beta but still present in CivilFEM 2017. The support notes also separate the student crash from the commercial-beta licensing delay

Solution

Install the latest CivilFEM 2018 beta update, verify Windows updates are current, keep the relevant installers available for re-install if needed, and continue with online support if the issue persists

Validity context: March 26 to April 12, 2018, with repeated follow-ups and a planned online support session

Temporary license outage during server migration and urgent license renewal

Problem

The user reports losing access to CivilFEM as if the server were down, then later asks for new licenses urgently for a meeting

Possible cause

The support reply explicitly ties the outage to a server move. The later renewal thread shows temporary license handling, remote support, and license file distribution

Solution

Restore licenses after the server move, send or re-send the needed license files, and coordinate a remote session if the user still cannot run the software

Validity context: March 27 to April 2, 2018

CivilFEM Student version fails to launch on one Windows machine

Problem

A student installation would not launch CivilFEM successfully even after remote support and repeated attempts

Possible cause

A machine-specific internal bug was ultimately found; the thread also observed dependency-version conflicts and suspected Windows/environment issues, but the final support note points to a bug tied to local language configuration and string comparison

Solution

The installation was patched on the affected machine, and a service pack was planned. If the issue reappears, the fallback mentioned in the block is to set the environment variable `CF_USERLOCALE` to `no`

Validity context: April 12-19, 2018; later resolved and scheduled for broader fix in a service pack

Marc solver license security error blocks meshing

Problem

Meshing failed with a Marc solver license security error, and the user asked whether the server was down

Possible cause

A temporary licensing server outage

Solution

Retry after the server is back online; the follow-up says the server problem was resolved

Validity context: April 16, 2018

Python script runs out of memory on a 4 GB machine

Problem

A CivilFEM Python script from the case pool failed with an out-of-memory message on a machine with 4 GB RAM, while it worked on an 8 GB machine

Possible cause

Available memory may be insufficient for the script or the machine may be running too many other programs; the block also indicates support was steering toward a configuration change, but the exact option is not visible here

Solution

Identify the missing configuration option from the screenshot, reduce background load, or test on a higher-memory machine if possible

Validity context: April 27, 2018; unresolved in the visible excerpt

Direct LM-X vendor installer is missing a required DLL

Problem

Installing the LM-X License Server directly from X-Formation requested a missing `liblmxvendor.dll`, and vendor downloads asked for an activation key the user did not have

Possible cause

The wrong installer source was used. CivilFEM ships its own installer bundle that includes the needed LM-X components and library

Solution

Use the CivilFEM-supplied installer, not the direct X-Formation download, and install the license server from there

Validity context: May 14-16, 2018

Beta tester update and 15-day license refresh needed after CivilFEM 2018 release

Problem

After license-file changes, CivilFEM still reported LM-X internal error 455 and software expired, while the installation still appeared to be the beta tester build

Possible cause

The beta installation had not yet been automatically updated to the released CivilFEM 2018 build when the user retried

Solution

Wait for or trigger the automatic update to CivilFEM 2018, then retry. If the license error persists, generate a report file from the Administration Utility and send it back

Validity context: May 17, 2018; later resolved after the automatic update downloaded and installed

HOSTS file formatting breaks name resolution during installation

Problem

The installer or setup could not proceed cleanly, and a ping/name-resolution problem pointed to a server hostname not translating correctly

Possible cause

A malformed HOSTS file, including formatting mistakes and a missing line break, was identified as the likely root cause

Solution

Fix the HOSTS file formatting, ensure the file extension is correct, and retry the installation or connectivity check

Validity context: April 19-23, 2018

Concrete slab bridge training material shows a display misalignment

Problem

In the training material, combination types were shown with the wrong label instead of the expected value

Possible cause

Windows font-size or UI scaling caused a misplacement in the interface

Solution

Use a smaller Windows font as a workaround; support said the issue would be fixed in version 19.0

Validity context: April 14-24, 2018

CivilFEM uninstall opens installer instead of removing the program

Problem

Uninstalling CivilFEM from Windows control panel launches the installer wizard; start menu uninstall entries are missing

Possible cause

The CivilFEM installation appears broken or partially removed, so the Windows uninstall entry no longer behaves correctly

Solution

Perform a manual cleanup of the installed CivilFEM and Marc directories, remove the CivilFEM configuration folder, then retry uninstalling from Control Panel so Windows can clear the stale entry

Validity context: Version-specific to the 2017/2016 install set shown in the thread; historical but concrete for that environment

Student license disappears after removing an older CivilFEM version

Problem

A student installation that previously worked starts asking for a license file or closes at startup after an older CivilFEM version is uninstalled

Possible cause

The older CivilFEM 2016 uninstall removed the shared student license state used by CivilFEM 2018

Solution

Reopen the Administration Utility and reselect the student license file for CivilFEM 2018; if the portal access is wrong, verify the student portal entitlement before reinstalling

Validity context: Explicitly tied to the 2016/2018 transition and the licensing model described in the thread

Marc installation not detected, causing meshing/solver failures

Problem

CivilFEM cannot find the Marc executable path, meshing fails, and the application reports issues with Marc/Mentat availability

Possible cause

The Marc installation or CivilFEM configuration is inconsistent, including a malformed MSC license entry that uses a server port prefix with a local file path

Solution

Correct the license entry in Administration Utility so it contains only the local license path, remove the unnecessary student-license line when using a commercial license, and if needed reinstall Marc or remove the CivilFEM config file so auto-detection runs again

Validity context: Supported directly by the report-based troubleshooting in early June 2018

Marc solver fails on large model due to memory pressure

Problem

Running a downloaded case produces an error about dynamic memory allocation for the Marc solver

Possible cause

The model requires a large amount of RAM, and the machine does not have enough free memory

Solution

Close other applications and free additional RAM before rerunning the case; if the machine still lacks sufficient memory, use a higher-memory system

Validity context: Limited to the specific model and machine described in the thread

CivilFEM becomes unresponsive during model creation and crashes

Problem

The program becomes unresponsive while creating a model and crashes before the user can progress far

Possible cause

The exact crash cause is unresolved in the thread; the discussion points to mixed-version evidence and a separate Marc detection/configuration issue rather than a single confirmed defect

Solution

Collect a matching version screenshot and installation report, verify which CivilFEM version is actually crashing, and use remote support if needed

Validity context: Historical and unresolved in the provided block

Unicode folder names break CivilFEM/Mentat workflows

Problem

Problems disappear after renaming a working folder with Latvian diacritics to an ASCII-only name

Possible cause

CivilFEM fully supports Unicode except when calling third-party software such as Marc/Mentat, which appears unable to handle the non-ASCII path reliably

Solution

Use ASCII-only directory names for the working path and rerun the example cases

Validity context: Specific to the path-handling behavior described in the June 8 thread

CivilFEM opens, but the model view panel stays blank

Problem

CivilFEM starts, but the grid/model do not appear in the model view panel even after removing the configuration file

Possible cause

Support suspected the wrong graphics driver selection, specifically a “Mirage Driver” being used for model view, or a configuration/Marc-detection issue

Solution

Update or reinstall the graphics driver, make the NVIDIA card the default, reopen CivilFEM, and if needed remove the CivilFEM configuration file and generate a new report

Validity context: June 27-28, 2018; the thread references CivilFEM 2017 SP1 and CivilFEM 2018

CivilFEM installation detects the wrong Marc setup or missing solver configuration

Problem

CivilFEM appears installed, but support says it is not detecting the Marc installation or the solver is not available/configured correctly

Possible cause

The configuration file or registry likely points to the wrong Marc version, or Marc is installed in a location/configuration CivilFEM does not detect

Solution

Reinstall CivilFEM or Marc as needed, avoid manually forcing the solver path, and use the detected solver entry rather than browsing to the folder path

Validity context: July 4-9, 2018

Student license expires earlier than the user expected

Problem

A student installation reported that the license expired on July 15, although the user expected it to last until the end of the year

Possible cause

Support indicated the user was likely on an older student stack and that the expiration depended on the specific CivilFEM/Marc version

Solution

Install the newer student release pair that support recommended

Validity context: July 25, 2018; the reply distinguishes 2016, 2017, and 2018 student versions with different expiration dates

Meshing always fails with an unspecified filename error on a student installation

Problem

The user reports that the error happens every time they try to mesh the model, and one screenshot shows an unspecified filename error

Possible cause

Support suspected the program was trying to run the commercial MSC Marc version instead of the student version, which points to a configuration-file problem

Solution

Remove the CivilFEM configuration file from the appdata CivilFEM folder, reopen CivilFEM, and verify the student version is detected

Validity context: July 25-26, 2018

License configured as local file instead of LM-X server license

Problem

CivilFEM 19.0 would not use the supplied license correctly; the report suggested the license was being treated as a local file

Possible cause

The license was meant for the CivilFEM LM-X License Server, but the client was configured as if it were a standalone local license

Solution

Install/configure the CivilFEM LM-X License Server, then point the LM-X Configuration Tool to the server on the local machine or the correct host; if still failing, send a fresh report

Validity context: July 25-27, 2018

Student CivilFEM/Marc installation is using the wrong Marc runtime or stale configuration

Problem

The software would not start cleanly or would fail during meshing, with errors such as file-not-specified or security-check failures after installation

Possible cause

The block points to a mismatch between student and commercial Marc configurations, and in one case to an expired Marc 2016 student edition versus a still-valid Marc 2017 SE

Solution

Remove the CivilFEM configuration file so the student version is detected correctly, or reinstall the correct Marc student edition; if the issue persists, generate a new report file

Validity context: July 25-August 20, 2018

CivilFEM 2018 rejected an older CivilFEM 2017 license file

Problem

CivilFEM 2018 would not recognize the existing license set even though the user believed the prior license should still work

Possible cause

The license file supplied earlier was for CivilFEM 2017, not CivilFEM 2018

Solution

Issue a new CivilFEM 2018 license file; the corresponding `.dat` file can remain valid

Validity context: August 7-8, 2018

Virtualized license server setup needed a virtual-server license workflow

Problem

The customer wanted to move the licensing server into a virtual machine and asked whether a security dongle was required

Possible cause

The licensing workflow for a virtual server was not yet fully established in the thread; the block shows back-and-forth about dongles, HostID, and LM-X reporting

Solution

Provide the LM-X report from the server that will host the virtual license, then generate a new license for the virtual server. The thread also states that a virtual machine can be used without a dongle

Validity context: August 14-20, 2018

Student installation hangs while meshing because CivilFEM loads the wrong Marc configuration

Problem

CivilFEM 2018 creates geometry and elements, but meshing stalls with almost no progress and eventually has to be force-closed

Possible cause

The student install is picking up a commercial MSC Marc configuration instead of the student one, likely due to a saved CivilFEM configuration file

Solution

Remove the saved CivilFEM configuration from the user appdata area, reopen CivilFEM 2018, and re-save the Options settings so it detects the student Marc again

Validity context: Known student-installation issue in late August 2018

CivilFEM 2017 cannot solve because the Marc 2016 student license is expired

Problem

The older CivilFEM 2017 installation can open and mesh, but solving fails with a license-related security error

Possible cause

Marc 2016 student support has expired, while CivilFEM 2017 still requires that Marc version

Solution

Use the newer CivilFEM 2018 / Marc 2017 combination, or otherwise restore a valid Marc 2016 license if the older version must be kept

Validity context: Explicitly tied to a July 2018 expiration and August 2018 follow-up

Commercial CivilFEM on a network server was misconfigured on the client side

Problem

A commercial CivilFEM install over VPN initially prompts for Marc and Mentat paths, and the license window is not behaving as expected

Possible cause

The client is not connected correctly to the floating network setup, or the wrong installer/licensing path was used while trying to mix student and commercial components

Solution

Use the floating-network installation flow, ensure VPN access to the license server is active, and install the matching commercial Marc package rather than only the student package

Validity context: Late August 2018

CivilFEM 2018 does not run on older graphics hardware

Problem

The 2018 version fails to start because of a GL graphics error on older machines without a dedicated graphics card

Possible cause

The machine does not meet the minimum graphics requirements for CivilFEM 2018

Solution

Upgrade the graphics hardware or the machine. A temporary unsupported dependency-copy workaround was mentioned, but it was explicitly described as unsupported

Validity context: Late August 2018

CivilFEM NPP addon does not become available after license update

Problem

After updating license files, the user says the NPP addon is still not available in CivilFEM and asks how to switch it on

Possible cause

Inferred from the support reply, the addon likely was not being activated correctly because the license files needed to be added together in the Administration Utility rather than replacing one file with another

Solution

Keep both license files installed together in the Administration Utility, verify the report file, and if still unresolved use remote support to inspect the configuration

Validity context: September 2018, tied to CivilFEM NPP powered by Marc 2018

CivilFEM / Marc Mentat meshing never completes

Problem

The user can open CivilFEM and draw a model, but clicking Mesh leaves it stuck at "Started meshing" and it never finishes

Possible cause

Inferred from the replies, likely Mentat path/locale handling issues or an incomplete Marc Mentat installation; later messages also mention missing Marc Mentat Documentation

Solution

Generate and inspect the Administration Utility report, try meshing from a plain-English path, verify Marc Mentat Documentation is installed, and use remote support if needed

Validity context: September 2018, with references to CivilFEM 2018 and Marc Mentat 2017

CivilFEM 2018 student version appears to need license configuration

Problem

The user says no products are found after installation and asks how to configure the CivilFEM 2018 student version license or MSC dat file

Possible cause

The block’s support reply says no explicit configuration is needed because the student version uses a generic embedded student license; if activation still fails, it may be an admin-rights issue

Solution

Treat the student edition as self-licensed, test by running CivilFEM as administrator, and use remote support if the issue persists

Validity context: September 2018, specifically CivilFEM 2018 student version

Dynamic memory allocation failure during a demo mesh case

Problem

The user reports an "unable to perform dynamic memory allocation" error in a demo case and asks whether it is caused by RAM capacity

Possible cause

Inferred from the reply, the mesh may be too fine and consuming too much memory; the support note also suggests the error may originate from MSC rather than CivilFEM

Solution

Try a coarser mesh with fewer elements, then re-test; if the error persists, treat it as an MSC-side issue based on the support reply

Validity context: September 2018, tied to the specific demo case mentioned in the thread

Factor of safety workflow on CivilFEM

Problem

The user asks how to specify a factor of safety on CivilFEM, including an example applying 1.6 to yield stress

Possible cause

The block does not give a cause; it only shows that the question was redirected to a support channel that handles installation and licensing

Solution

The missing piece is the specific CivilFEM module or menu workflow where the factor of safety is being set; that is needed before a defensible extraction can be made

Validity context: September 2018

CivilFEM launch depends on graphics driver and OpenGL support

Problem

CivilFEM opens but cannot create a new model, the model view stays blank, or Marc/Mentat reports a security check failure

Possible cause

An older GPU or outdated driver does not meet the required OpenGL support, and the Marc/Mentat standalone launch is not permitted by the bundled license

Solution

Update the graphics driver or test on another computer, and use CivilFEM only in the supported way for Marc/Mentat

Validity context: November 2018; tied to machine capabilities and driver state

Windows 10 support differs by CivilFEM version

Problem

A customer asks whether existing CivilFEM versions will run after an OS migration to Windows 10 64-bit

Possible cause

Version-specific support boundaries; newer releases are supported, while older releases are only informally tested

Solution

Treat 17.1 and later as the supported range for Windows 10 in this block, and avoid claiming official support for 14.5

Validity context: October 2018; purely version-dependent

Dropdown selection crash when a section is not defined first

Problem

A structural element drop-down shows no values and can crash when the field is edited

Possible cause

A workflow bug triggered by pressing TAB before defining the section first

Solution

Avoid TAB, use Enter or the mouse, define the section before editing the field, and apply the future service pack once available

Validity context: October 2018; explicitly reproducible in the thread

CivilFEM installation needs a local path without spaces or non-English characters

Problem

CivilFEM with Marc Student fails to install or run correctly in certain paths

Possible cause

The Marc installation path contains spaces or non-English characters, which the thread says can cause problems

Solution

Reinstall using a path without blank spaces or non-English characters and follow the installation video if needed

Validity context: October 2018; installation-path specific

Node-locked license needs local installation mode

Problem

The license is described as local rather than floating, and installation must follow a local workflow

Possible cause

The license is bound to a machine component rather than a floating server setup

Solution

Use local installation mode instead of a floating-license workflow

Validity context: December 2018; specific to that license arrangement

CivilFEM installation failing due to clock/license reset utility confusion

Problem

The user reports an installation-related problem and asks about a clock error and whether a specific executable exists to fix it

Possible cause

A local licensing/security-time issue, possibly involving a bundled reset utility for the licensing clock

Solution

Verify whether the relevant reset utility exists in the installation tree, confirm it was run with admin rights, and check whether the issue is actually licensing-related rather than a generic installer failure

Validity context: Dec 2018

Mesh generation fails in CivilFEM powered by Marc with version/path mismatch

Problem

A user cannot generate a mesh for structural elements and later reports a rigid bodies error

Possible cause

The report file appears to come from version 2017 while Marc system paths are missing, even though the CivilFEM 2018 license is installed. The issue may also be influenced by an unusual working directory path with special characters or whitespaces

Solution

Generate and inspect the report file, verify Marc system paths, test in a normal working directory, and if needed use remote assistance to reproduce the fault directly on the machine

Validity context: Jan 2019

CivilFEM crash or unexpected error on open or while selecting a reference point

Problem

CivilFEM crashes on launch after installation, or crashes when the user clicks to reference a point in a beam example

Possible cause

No concrete code defect is identified in the emails. The support flow points to generating a report file, checking graphics drivers, and reproducing the issue if it persists

Solution

Request the Administration Utility report file, confirm graphics drivers are updated, and if the issue continues reproduce it in-house or via remote session

Validity context: Feb 2019

License/EULA administration for CivilFEM with Marc and Ansys

Problem

The emails ask what documents need to be signed and how to proceed with licenses for CivilFEM with Marc and CivilFEM with Ansys

Possible cause

Administrative licensing paperwork rather than a technical software fault

Solution

Do not treat as a technical support issue unless a concrete activation or installation failure is present

Validity context: Feb 2019

Mesh fails with "Mentat log file not found"

Problem

Meshing stops with an error that the mesh failed for a solid group and Mentat log file is not found, including when testing simple examples

Possible cause

Working-folder or installation-path configuration problem; the support thread also checks CivilFEM path settings and asks for an installation report, so a local environment/config issue is more likely than a model-only problem

Solution

Verify CivilFEM configuration paths, use a clean working folder, and compare the installation report against a known-good setup before retrying the mesh

Validity context: March 2019 support case; appears tied to the then-current installation

Saved .cf file becomes truncated after clearing mesh or Boolean operation

Problem

A model can be saved normally at first, but after removing mesh or after a Boolean click, saving produces a much smaller .cf file and the model appears nearly empty on reopen

Possible cause

Not established in the block. The thread suggests the failure is triggered by model operations such as clearing mesh or Boolean, but the exact root cause is not confirmed

Solution

Reproduce the problem starting from the same model state, isolate the operation that triggers truncation, and compare the saved file immediately before and after mesh removal or Boolean processing

Validity context: April 2019 support case; the behavior is explicitly tied to operations performed on that model state

CivilFEM saves produce truncated `.cf` files and lose model content

Problem

A saved model collapses to a tiny file size compared with the original, and reopening it shows an almost empty model; the sender also says the issue happened before when exporting results

Possible cause

Unknown from the block; the emails only show that the file save or write process is failing after some model operations

Solution

Reproduce using the source file, compare save behavior immediately after opening versus after edits, and use remote assistance if reproduction is not possible

Validity context: April 2019, with the main report on 2019-04-15 and follow-ups on 2019-04-23

CivilFEM crashes when clicking Boolean operations

Problem

The user reports a crash exactly when clicking the Boolean tool, with no other action before the failure

Possible cause

Unknown from the block; the support reply says more detail would be needed to reproduce the Boolean operation

Solution

Capture the exact Boolean step and model state, then reproduce it on the support side

Validity context: April 2019

Marc/Mentat fails to start or behaves incorrectly on Windows, likely tied to license or environment

Problem

One thread says CivilFEM cannot start and shows a license-related error; another reports Marc/Mentat failing to open or crashing while working with the installation

Possible cause

The block points to Windows 7/update state, installation state, and licensing/environment issues, but does not establish a single root cause

Solution

The emails recommend using the Marc Student 2017.0 installer, checking Windows Update, trying another machine, and running as administrator if needed

Validity context: April 30, 2019 and May 7-10, 2019

CivilFEM license security error because the MSC license file is missing from its original location

Problem

CivilFEM refuses to run with a license security error, and the report indicates the configured MSC license file is no longer present where CivilFEM expects it

Possible cause

The license file was selected during installation and later moved or removed, leaving CivilFEM pointing at a missing path

Solution

Re-open the CivilFEM Administration Utility and select the MSC license file again; the support reply also says the installer should copy the file into the program folder to avoid this

Validity context: May 21, 2019

License security error caused by missing license file path

Problem

A license security error appears because the referenced license file is no longer found in the original location; the issue persists until the file/path is corrected

Possible cause

The selected license file was moved or removed after installation, leaving the configured path stale

Solution

Re-add the license file in the administration utility or restore the correct path, then reopen the application to refresh the license state

Validity context: 2019 thread; likely version-specific to the documented workflow

Beta tester exercise fails due to MSC license configuration conflict

Problem

A CivilFEM 2019 Beta exercise fails to run, installation warns about not reaching the license server, and report files are exchanged repeatedly while the problem persists

Possible cause

The local MSC license configuration is overriding the beta server settings, or stale expired license references remain on the machine

Solution

Remove the user-level license variable if present, set the beta server in the administration utility, and remove references to expired local license files. If needed, test on another machine or use a remote support session

Validity context: 2019 beta context

Temporary CivilFEM and Marc licenses needed for a multi-user training setup

Problem

A training group cannot start exercises because temporary licenses are missing, and the requester asks whether the licenses should be floating or node-locked and how many seats are needed

Possible cause

Temporary licensing had not yet been provisioned, and the licensing model was still being clarified for the group size and work-from-home need

Solution

Collect host IDs, confirm whether the commercial plan should be floating or node-locked, and issue matching temporary licenses for both CivilFEM and Marc as required

Validity context: 2019 and tied to a training extension scenario

Beta version expected as an update instead of a new installer

Problem

A user selects the beta option inside the product but does not get any new download or update

Possible cause

The beta release is a separate installer rather than an in-place update path

Solution

Download the beta installer from the account portal and install it separately; minor updates continue to use service packs

Validity context: 2019 beta onboarding context

Duplicate library version causes a CivilFEM-related startup or runtime error

Problem

A procedure entry point/library error appears, and the user reports that the issue is resolved only after identifying a program incompatibility

Possible cause

The same DLL/library is installed more than once in different versions, likely from another application

Solution

Identify the conflicting DLL and remove or rename the duplicate version; confirm which third-party program installed it

Validity context: June 2019; likely a one-off environment conflict, not a product defect

CivilFEM 2019 beta mis-detects Marc/Mentat license features

Problem

CivilFEM 2019 fails to find or use Marc/Mentat licensing even though the underlying MSC license appears to be running

Possible cause

The beta auto-detection is a false positive, detecting Marc_the organization and Mentat_the organization features that are not actually present on the machine

Solution

Use the temporary license provided by support; the thread says the issue is solved for now and a fix/workaround will be implemented in the final version

Validity context: June 2019 beta-era issue; explicitly described as temporary and later fixable in the final CivilFEM 2019 release

Crash when a trainee uses a macro and specific tendon-loss workflow

Problem

The application crashes, initially described as random while recoding a macro, later narrowed to a repeatable crash when the user forgets to mesh the model and calculates losses in tendons

Possible cause

A workflow-dependent defect or missing precondition in the model setup; the dump file did not reveal a root cause

Solution

Reproduce the crash with exact steps, especially the meshing state and tendon-loss calculation sequence, so support can isolate the bug

Validity context: June 2019; support later says the bug will be corrected in the next revision of CivilFEM 2019

CivilFEM 2019 Student uninstall leaves remnants after upgrade

Problem

After uninstalling Marc 2017 and CivilFEM 2018, the new CivilFEM 2019 Student installation appears to work, but the old CivilFEM 2018 entry still shows up in Windows

Possible cause

The standard uninstaller does not fully remove prior installation artifacts

Solution

Use a manual uninstall or delete the leftover program directory by hand; update the installation guide to include migration/removal steps

Validity context: July 2019; framed as an installation/migration issue during the CivilFEM 2019 Student rollout

CivilFEM 2019 release license file tied to the wrong computer

Problem

After installing CivilFEM 2019, the software does not detect the licenses, and later it becomes clear that the license files sent earlier were for a different computer

Possible cause

License files were generated for the second computer, while the user needed a license for the first computer where CivilFEM 2019 was installed

Solution

Generate and install a new license file bound to the correct machine, using the CivilFEM Administration Utility to select the correct license file

Validity context: July 2019 release window; explicitly tied to CivilFEM 2019 and machine-specific licensing

Dealer license CivilFEM error 19 on node-locked deployment

Problem

After installing CivilFEM, the user gets error message 19 even with a node-locked license on a single computer

Possible cause

The license is being used in a way that does not match the intended deployment; the thread also shows a server/network transition, MSC/FlexLM conflict with another installed software, missing privileges to write in AppData, and blocked communication to port 27500

Solution

Provide a report file, verify whether the license should be node-locked or floating network, generate the correct server or workstation license, and ensure the network path to port 27500 is open

Validity context: July 2019; the support summary says the installation was eventually made working on the server after these fixes

CivilFEM cannot start because the license server is not reachable

Problem

CivilFEM freezes at startup and later only works when the client stops pointing to the network license server

Possible cause

The client could not reliably reach the floating-license server on the required port, and the server-side license process may also have been blocked. To identify the exact product variant, we would need the launcher/module name or the report file

Solution

Open the required port, ensure the license server process is allowed to use it, and verify the license from a report file

Validity context: Historical, tied to July 2019 license setup

Installation fails because the installer cannot write configuration files

Problem

CivilFEM installation does not complete and no report file is produced

Possible cause

The installer likely lacked permission to write configuration and temporary files under the user profile area. To identify the exact product, we would need the product name from the launcher or the generated report

Solution

Verify user privileges and write access to the profile/temp location, then retry and generate a report file

Validity context: Historical, tied to the same July 2019 installation case

CivilFEM by Marc reports a license-file and computer-ID mismatch

Problem

Opening CivilFEM shows an error message and the software does not start normally

Possible cause

The license file is tied to a different computer ID than the one being used, or there is a local configuration issue if only one computer is involved

Solution

Use the matching host or request a floating-network license; otherwise generate a report file for diagnosis

Validity context: Historical, tied to July-August 2019

CivilFEM by Marc keeps failing after a heavy DXF import and crash

Problem

The software stops while processing a heavy DXF file and then shows an error message on startup

Possible cause

The crash may have left Windows in an unstable state, or the DXF import itself may be the reproducible trigger

Solution

Restart the machine, try remote support, and reproduce the issue with the DXF file if it can be shared

Validity context: Historical, tied to July-August 2019

CivilFEM 2019 ribbon layout breaks on a smaller laptop screen after moving between monitors

Problem

The upper ribbon shows a large blank area on the laptop screen, but looks normal on the external monitor

Possible cause

The issue seems tied to a display configuration, monitor resolution, desktop extension/cloning behavior, or possibly localization/font sizing. To identify the product, we would need the exact CivilFEM module name from the screenshot/report

Solution

Try the ribbon layout workarounds, test on another computer or OS language, and compare the behavior with the monitor connected before or after launching the app

Validity context: Historical, tied to August 2019

CivilFEM crashes when loading result files after switching analysis type

Problem

The user reports repeated crashes when loading result files after changing from one analysis type to another

Possible cause

The cause is not established in the block; the user suspects memory, but the thread only confirms a reproducible crash path after switching analysis type. To identify the product, we would need the exact module name from the report or screenshot

Solution

Reproduce the crash with the attached sample project and inspect the report file and screenshots

Validity context: Historical, tied to January 2019

CivilFEM beta/service-pack crash on Windows 7

Problem

CivilFEM would not start after installing a beta service pack; the issue was reported as occurring only on Windows 7

Possible cause

A bundled library was missing on Windows 7 but present on Windows 10, forcing a repackaging fix

Solution

Repackaged build was provided through a direct download link because automatic update could not run while the application was down

Validity context: Specific to the 2019 beta/service-pack build and Windows 7; historically time-bound

CivilFEM 2018/2019 fails after installing a new license file

Problem

After installing a new license file, none of the software versions would run

Possible cause

Likely a license type or deployment mismatch, with at least one follow-up indicating the wrong installation path for the license type

Solution

Request and inspect an Administration Utility report plus the installed license file(s); determine whether the user has a floating network license or a local/evaluation license

Validity context: Tied to 2018-2019 licensing behavior and the 2019 maintenance period

CivilFEM student license expired or mismatched with Marc/Mentat version

Problem

A student user could not mesh or launch Mentat and saw an expired educational license message

Possible cause

CivilFEM 2018 paired with Marc 2017 Student Edition had expired; the solution path points to a newer CivilFEM 2019 package that includes Marc 2018.1

Solution

Uninstall CivilFEM 2018 and Marc 2017, then install CivilFEM 2019 with the matching student release; if the error persists, send an Administration Utility report

Validity context: Strongly tied to the 2018/2019 student distribution and educational license expiry timing

Concrete Cracking / MSC license selection conflict

Problem

CivilFEM launched Marc/Mentat through the wrong license mode or failed when the standalone MSC license path was selected

Possible cause

The automatic MSC-license detection could misidentify available features, and the standalone MSC path did not pass the expected Marc input parameter

Solution

Apply the planned bug fix in the next update and verify whether the user has MSC-related features provided by the vendor or a standalone MSC license

Validity context: Specific to the CivilFEM 2019 license-selection logic

CivilFEM 2019 display/layout issue on multi-monitor setups

Problem

The ribbon area showed a large blank space when CivilFEM was moved from an external monitor to a laptop screen

Possible cause

Likely a display-scaling, resolution, language-localization, or multi-monitor configuration issue

Solution

Reproduce on another machine or configuration, then try ribbon layout toggles such as minimizing the ribbon or changing the ribbon position

Validity context: Time-bound to CivilFEM 2019 UI behavior on specific display setups

the organization lab license deployment needs floating-license server setup and the correct machine mapping

Problem

A lab needs help installing the software, but the licensing setup is unclear, the license file is not straightforward to deploy, and the team needs to know which machine the license belongs to

Possible cause

The deployment is for a floating-license setup and the correct license-server host or target machine was not initially identified. The support thread asks for license files and a generated report to diagnose the setup

Solution

Confirm the target machine/server, install the license server on the correct host, provide the requested report file, and use the license file set provided by support

Validity context: Historical, based on a September 2019 lab deployment thread

CivilFEM license is not recognized after renewal and a temporary replacement is issued

Problem

The software no longer recognizes the license after a renewal date starts

Possible cause

The renewed license was not yet active in the software workflow, so support issued a temporary replacement license until payment or activation completed

Solution

Install the temporary license through Administration Utility, then replace it with the permanent license once activation/payment is complete

Validity context: Historical, tied to a renewal event dated 2019-10-01

Marc behavior breaks when usernames or file paths contain accents

Problem

Marc has problems when the user name contains accented characters, and a later reply says the same can affect the path where the file is stored. A follow-up suggests disabling the safe-path option in the solver and mesher

Possible cause

Character-encoding or path-handling limitations in Marc for accented usernames and accented directory paths

Solution

Use a non-accented user account and store the files in a path without accents. If the run still fails, test with the safe-path checkbox disabled for the solver and mesher

Validity context: Historical, tied to the October 2019 Marc support thread

CivilFEM with Marc licensing needs server-side requirements clarified

Problem

The customer asks what server requirements are needed to install licensing for CivilFEM Expert / Marc

Possible cause

The licensing stack depends on specific server-side components and supported operating systems. The reply says CivilFEM and Marc use separate license servers and that only certain 64-bit Windows versions are supported

Solution

Provide the server’s configuration file or generated text file to support, then install the required license-server components on a supported 64-bit Windows host

Validity context: Historical, based on the 2019-10-11 licensing setup thread

CivilFEM license file version mismatch between 19.1, 19.2, and 2019 R1

Problem

A license file issued for one CivilFEM version is not accepted when the user moves between versions

Possible cause

The license was initially issued for the wrong version, then corrected after the mismatch was recognized

Solution

Generate and issue the correct license file for the target version; confirm which version the customer is actually running

Validity context: Historical, tied to October 2019 version migration discussions

CivilFEM Marc issue with accented user names or accented file paths

Problem

Marc misbehaves when the Windows user name contains accents, and the issue is linked to paths or safe-path handling

Possible cause

The software or its path handling is not robust with accented characters in user names or file paths

Solution

Use a non-accented user account or disable the safe-path option for solver and mesher as indicated in the thread

Validity context: Historical, tied to October 2019 and Marc-specific support

Student download package appears corrupted or truncated

Problem

The downloaded student installer is much smaller than expected and is described as corrupted

Possible cause

The download was interrupted or otherwise incomplete

Solution

Re-download the package and verify the file size before retrying installation

Validity context: Historical, October 2019 webinar follow-up

Network license treated as a local installation license

Problem

CivilFEM would not run with a valid `.lic` file because the user tried to use a server license as if it were a node-locked local license

Possible cause

The license file was for a license server, and the client machine needed to point to that server instead of installing the file locally

Solution

Follow the server-install and client-pointing steps from the installation guide, verify the license server is running, and confirm the client is configured to reach it

Validity context: 2019-11-18 to 2019-11-20

License bound to the wrong hardware identifier or to a changing MAC address

Problem

CivilFEM reported that the license did not match the PC, and the user later still saw the same error after generating a report

Possible cause

The license was generated against a hardware identifier that no longer matched the machine, including a MAC address that could change by software

Solution

Reissue the license against a stable identifier, with support indicating a BIOS-only binding to avoid the mismatch

Validity context: 2019-11-21 to 2019-11-23

University licensing setup questions for local server and machine migration

Problem

The institution needed to understand how the 25 student licenses and professor license should be deployed, what server requirements apply, and whether licenses can be moved when the server or professor machine changes

Possible cause

The deployment model and Excel/EULA inputs were not yet fully clarified between the university and support

Solution

Confirm the server and professor machines, complete the Excel/EULA, use the local server model described by support, and request a machine change through Secretariat if the server changes

Validity context: 2019-11-22 to 2019-11-23

CivilFEM license server migration from legacy Windows to a new host

Problem

CivilFEM license server migration from legacy Windows to a new host

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

University license deployment model for 25 seats and remote access

Problem

University license deployment model for 25 seats and remote access

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

CivilFEM speed-test comparison and performance bottleneck analysis

Problem

CivilFEM speed-test comparison and performance bottleneck analysis

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

Marc Solver error 67 during model execution

Problem

Marc Solver error 67 during model execution

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

CivilFEM product not found or service error during installation with student/commercial version mismatch

Problem

CivilFEM product not found or service error during installation with student/commercial version mismatch

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

ATOMPROEKT license files were not combining into a single usable pool

Problem

Multiple license files were being treated separately, so the customer could not use all purchased tasks simultaneously

Possible cause

Separate files from different purchases were being handled as independent license entries instead of additive ones

Solution

Issue a cumulative additive license file or merge the entries into one file so the task counts add up correctly

Validity context: January 2020

CivilFEM Expert 2019 powered by Marc needed deployment guidance and license-server setup

Problem

The customer needed server requirements, license generation, and first-time installation help. There was also confusion about whether two license services had to be on separate PCs

Possible cause

Incomplete deployment guidance and ambiguity about the licensing topology

Solution

Use the supported 64-bit Windows licensing setup, allow both license services to live on one machine if desired, generate the required licenses, and follow the installation guides and videos

Validity context: October 2019 to February 2020

CivilFEM licensing and deployment for a university server was delayed by infrastructure requirements

Problem

The customer could not finish installation because the server, public IP, and Windows Server procurement were still pending

Possible cause

The required server-side infrastructure was not ready

Solution

Wait for the server and public IP to be provisioned, then resend the server and machine details so the licenses can be issued

Validity context: January 2020

CivilFEM Expert 2019 powered by Marc had a meshing/opening problem on a structural gallery model

Problem

The user reported that the software could not be opened and later that there was a problem while trying to mesh the structure

Possible cause

Not stated in the block. The available text only shows the problem report and a request for help

Solution

Review the attached screenshots/model to determine whether the blocker is geometric, meshing-related, or license-related; no fix is shown in the block

Validity context: January to February 2020

MSC license file expired or not updated

Problem

The software could not proceed normally because the MSC license file was reported as expired or missing an updated file

Possible cause

The MSC-side license had expired and needed replacement or update

Solution

Update the MSC license file through the Administration Utility, or obtain the renewed file from the secretariat if it was not received

Validity context: Strongly supported by February 2020 messages and the stated expiration date window

CivilFEM cannot open after license change

Problem

The user reported being unable to open the software after a license-related exchange

Possible cause

The annual license was needed or the updated license had not yet been applied correctly

Solution

Wait for the new license file, then apply it using the documented installation/update process

Validity context: Supported by the January 2020 thread, but the exact failure mode is not fully described in the excerpt

Student installation leaves Marc unavailable or already installed

Problem

The installer either did not install Marc, or later reported that Marc Mentat was already installed

Possible cause

The CivilFEM/Marc installation was incomplete, conflicted with an existing Marc installation, or needed a retry through the correct installer option

Solution

Re-run the installer, choose the Marc installation option, try uninstalling the existing Marc entry if possible, and if needed generate a report file for support

Validity context: Supported by March 2020 messages

Remote use requires a special license

Problem

A customer wanted to install CivilFEM on one machine and connect to it remotely from outside the local network

Possible cause

A special license or activation mode for remote control was likely required, but the exact product/workflow is unclear from the excerpt

Solution

Confirm which CivilFEM variant and license model apply, then verify whether administration can create a license that permits remote use and provide the required instructions

Validity context: Supported by internal correspondence dated February 18-19, 2020

Structural gallery modeling and load application assistance

Problem

The customer asked for help applying loads and understanding the provided model materials/sections, with earlier references to geometry and meshing already completed

Possible cause

The model handoff/documentation was not clear enough to continue independently

Solution

Review the installed model files and clarify load application and related modeling assumptions

Validity context: Present in the November 2019 conversation, but the excerpt is truncated and mostly collaborative rather than a clear support defect

MSC Marc component missing after CivilFEM student install

Problem

the installer reports Marc as already installed, but the desktop shortcut, control panel entry, or program files are not present

Possible cause

the Marc component was not installed correctly, or the main installer wizard hid the component while the underlying Marc installer was only partially unpacked

Solution

run the installer again, open the installer folder from the help/info area, launch the original Marc installer directly, and if needed uninstall and reinstall from the default path

Validity context: March 2020, tied to the student-license install thread

Student-version model error from missing boundary condition or disconnected nodes

Problem

a small shell-and-beam model in the student version produces an error during structural analysis

Possible cause

a disconnected node, a missing merge of nodes, or a missing boundary condition in the load case

Solution

check for unmerged nodes, verify the load-case boundary conditions, and send the model if further inspection is needed

Validity context: March 2020

Patran installer hangs and later solver path is broken

Problem

the Patran installer freezes near the end; after forcing it closed, the program appears installed but exercises fail when sent to the solver, and uninstalling seems to reinstall instead

Possible cause

incomplete installation state, incorrect solver path configuration, or leftover files causing the uninstall/reinstall loop

Solution

uninstall, restart, remove leftover installation directories manually if they remain, check `P3_TRANS.INI` or `site_setup` for the solver executable path, and verify the required environment variables

Validity context: March 2020

Patran installation completes inconsistently, but solver calculation fails afterward

Problem

Patran installation completes inconsistently, but solver calculation fails afterward

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

CivilFEM 2020 setup fails on the final step before licensing is applied

Problem

CivilFEM 2020 setup fails on the final step before licensing is applied

Possible cause

The root cause must be confirmed from the exact version, licensing setup and environment

Solution

Confirm the product, version, host application, license mode and exact error before applying changes

Patran installer hangs or fails to resolve after repeated reinstalls

Problem

The user repeatedly reports that Patran installation stops at the same point, later hits a different startup/resolver error, and sometimes appears to install 32-bit components while still failing to work

Possible cause

The thread suggests a broken or non-clean installation state, possibly leftover configuration, an incorrect install directory, or an INI/path configuration problem. The block also mentions a Windows update during troubleshooting, but does not prove causation

Solution

Try a clean reinstall into the intended directory, verify that old files and registry/config remnants are removed, and check whether the INI/path configuration points to the solver correctly. Remote assistance was offered, and MSC student support was also suggested

Validity context: April 2020 only; the exact workaround and link references are date-specific

CivilFEM 2020 free-course launch closes immediately after license login

Problem

After entering the login/license prompt, the program closes within seconds with no usable session. The user reports repeated reinstall attempts with the same result

Possible cause

The block does not confirm a cause. The support thread points to a missing or misplaced Marc license file, possible antivirus/firewall interference, or a startup/debug issue, but none is proven

Solution

Restore or verify the Marc license file location, temporarily disable security software for testing, try Debug Mode from the administration utility, and collect the generated report and starting log if the crash persists

Validity context: April 2020 only; references CivilFEM 2020 powered by Marc and course-specific behavior

CivilFEM 2020 commercial-license update and course-license confusion

Problem

The user is unsure whether a new course license is needed, how it differs from the existing commercial license, and how to move from the 2019 installation to 2020 without breaking the current server-based setup

Possible cause

The block points to process confusion rather than a technical fault. The support replies indicate that the commercial license should remain valid and that the 2020 update needs to be installed carefully, but no failure mode is confirmed

Solution

Wait for the new commercial license file from Secretariat, then update the CivilFEM 2020 license/server configuration as instructed. The thread explicitly separates the course license from the existing commercial/license-server setup

Validity context: April 2020 only; tied to the 2019 to 2020 transition and the free-course rollout

CivilFEM 2020 powered by Marc closes shortly after license login

Problem

The program reaches the License Login step, then closes after a few seconds. The same behavior was reported after reinstalling, disabling the firewall, and starting in debug mode. Marc would not open independently either

Possible cause

A configuration or environment conflict on the machine was suspected. Support later suggested a system environment variable change and also mentioned trying another PC or remote debugging

Solution

Set the system environment variable `CF_USERLOCALE=no`, retry CivilFEM, and if it still fails test on another machine or use remote support

Validity context: April 22-24, 2020

Student or trial installer cannot be executed on the user’s PC

Problem

The Student Version installer for 2019 or 2020 reportedly cannot run on the machine, with a message that the application cannot be executed on this computer. In the same support chain, the user also reported download or registration difficulties

Possible cause

Support speculated about 32-bit Windows, an outdated operating system, or a corrupted or incomplete download

Solution

Confirm the machine is 64-bit with an updated Windows 10 install, redownload the installer, and if it still fails collect a screenshot of the exact error

Validity context: May 2-4, 2020

License transfer or machine-change request for node-locked and network licenses

Problem

The customer needs licenses moved to a different machine or server, including requests to change MAC address, update Host-ID, and support remote access for students. Multiple node-locked and network license IDs are discussed

Possible cause

The licenses are bound to machine or server identifiers, so moving to a new server or changing hardware requires regeneration of the license files

Solution

Collect the machine-information text file from the configuration tool, confirm whether the target is a virtual server, complete the license change form, and generate new license files

Validity context: April 28-May 18, 2020

License renewal/update confusion for existing CivilFEM installations

Problem

A user asks whether an existing CivilFEM installation must be uninstalled to apply a renewed license, or how to add new license files after receiving a time-limited renewal

Possible cause

License renewal is being confused with software reinstall. The support response indicates the license should be updated through the Administration Utility rather than uninstalling the program

Solution

Add the new license files via the Administration Utility and do not uninstall unless another issue is present

Validity context: May 4, 2020

CivilFEM 2020 license does not open on a new machine after migration

Problem

CivilFEM 2020 fails to open or starts without the expected MSC feature set after a computer change; the support thread shows the license was tied to the old machine instead of the replacement device

Possible cause

The license file was generated for the old computer or bound to the wrong hardware identifier, and the selected network adapter could be unstable

Solution

Reissue the license for the new machine using the correct machine data, then update it through the Administration Utility. Avoid reusing the old machine-bound file

Validity context: May 18-22, 2020; resolved in-thread by reissuing licenses

CivilFEM 2020 replace-based license generation fails after upgrade

Problem

A CivilFEM 2020 license that should replace a previous CivilFEM 2019 license still does not work, even though the older license was not expired

Possible cause

The thread suggests a version-specific replace issue, possibly related to an LM-X platform change; this is not confirmed in the block

Solution

Generate new CivilFEM 2020 licenses without replace, and keep the replace issue under investigation with the licensing vendor

Validity context: May 20-21, 2020

CivilFEM blocks at startup after Windows date/time was changed

Problem

The student reports that CivilFEM does not open after installation and shows an error at the license login stage; the same issue happened with the Student Version

Possible cause

The system clock had been changed, triggering the software security check

Solution

Restore the correct date/time and run the clock-reset utility from the installation directory with administrator privileges

Validity context: May 14-19, 2020; the thread indicates the issue was identified and a utility-based fix was provided

Marc Error 13 when solving due to oversized material element lists

Problem

Marc returns “Error 13” on solve; the user suspects mesh quality, but the support reply points to the material assignment structure instead

Possible cause

A single material is being read with too many mesh elements in the list, exceeding Marc’s default input limit of 1,000,000 items

Solution

Split the material into copies and assign each copy to a subset of structural elements so each list stays below the limit

Validity context: May 18-19, 2020

License transfer to another machine blocked until a new file is issued

Problem

The customer says they are blocked from project progress and needs the license moved or regenerated for another computer

Possible cause

The existing license was bound to a different machine or required formal reissue before use on the target computer

Solution

Complete the license change process, sign the change form, and generate/send the new license file for the new machine

Validity context: Late May 2020; appears to be a one-off workflow issue tied to that customer request

CivilFEM 2020 powered by Marc failed because license files were generated with a replace/naming mismatch

Problem

CivilFEM 2020 on the same machine as 2019 did not find the expected license; support later concluded the failure was related to the generated license files and the replace behavior

Possible cause

The license files were generated before the replace behavior was understood, and the naming/replacement logic caused the new files to be unusable as-is

Solution

Regenerate the CivilFEM license without replace, remove the old file, and keep only the newly issued license file on the client machine

Validity context: Strongly tied to late May 2020 release/support activity for CivilFEM 2020

CivilFEM 2020 powered by Marc could not find a working license server until MSC Licensing was upgraded and the port was configured

Problem

CivilFEM 2020 launched but did not find a usable license; later the Marc side worked only after updating the license server and correcting the server port configuration

Possible cause

The installed MSC Licensing server version was too old for the needed setup, and the license server port was either unset or misconfigured in the CivilFEM Administration Utility

Solution

Upgrade MSC Licensing to the required version, then enter the correct server port in the Administration Utility and verify the license path/configuration

Validity context: Early June 2020; this is a specific installation/configuration state for that environment

CivilFEM 2020 installer fails on Chinese-localized Windows 10

Problem

The 2020 installer fails on Chinese Windows 10, while the same workflow works on English Windows 10; the failure is reported as a setup crash or a path syntax error, and CivilFEM 2019 can install on the same Chinese system

Possible cause

Likely an installer or locale compatibility issue tied to the Chinese Windows environment; the block does not isolate whether the trigger is OS language, build level, packaging, or path handling

Solution

Retry with the updated installer, test on exact Windows build numbers, use a simple custom install path, run with admin rights, and check whether the signed helper utility fails on the affected system

Validity context: June 23-30, 2020; confirmed across multiple follow-ups and multiple machines

CivilFEM Expert powered by Marc license was installed as node-locked/local instead of server-based

Problem

CivilFEM does not launch correctly after license-file updates; the report shows the licenses configured as local files, and the customer also reports that a separate Marc license stops working after the change

Possible cause

The license files intended for a license server were applied as node-locked/local licenses, and the Administration Utility still pointed to local values instead of the required server/port configuration

Solution

Install the CivilFEM and MSC license files on the proper license servers, set the Administration Utility to the server:port values, and regenerate a license file if the core count or license scope must change

Validity context: June 16-18, 2020, with a later follow-up on June 24

Marc Mentat is not meant to launch as a standalone app under CivilFEM licensing

Problem

A customer expects Marc Mentat to open directly after adding the license files, but support says Marc should run under CivilFEM 2020 and that successful CivilFEM licensing is the real test

Possible cause

Usage expectation mismatch rather than a software defect; the support reply frames stand-alone Marc launch as unsupported in this configuration

Solution

Launch CivilFEM first, verify the license screen, check the solver and mesher paths, and follow the basic example flow used by support

Validity context: June 17, 2020

Student CivilFEM license expired and user was moved to the student version

Problem

The user reports that the CivilFEM student license has expired and asks what to do to continue the course

Possible cause

Normal student-license expiry and course-version lifecycle

Solution

Use the separate student installer, uninstall the course version if needed for disk space, and continue with the student license

Validity context: June 12-18, 2020

CivilFEM 2020 installer crashes on Chinese Windows during setup

Problem

Setup fails during installation, then `Setup.exe` stops working and the software is not installed

Possible cause

A CivilFEM 2020 installer change introduced a locale-sensitive issue; the thread later identifies the start-menu text containing a special character in the "powered by Marc" wording as the root trigger

Solution

Use the temporary fixed installer, then replace the official installer once validated

Validity context: Confirmed in July 2020; later acknowledged as fixed for future releases

License file not found because copied/renamed license paths were registered

Problem

The program asks for a license and does not open; the report says the referenced license file does not exist

Possible cause

The license files were added from a path that later changed, and the stored filenames included copy suffixes, so the administration utility pointed to missing files

Solution

Re-save the license files in a stable folder, remove prior entries, re-add them from the new path, and generate a fresh report if it still fails

Validity context: June-July 2020

License fails after machine identifier changes or is tied to an unstable adapter

Problem

The license no longer matches the computer after an OS update or when the machine identifier changes; the software cannot start or loses license validity

Possible cause

The license was bound to a changing hardware identifier, initially discussed as a Bluetooth/Wi-Fi adapter MAC-like value, so operating system changes or adapter selection caused the ID to differ from the license

Solution

Regenerate the license against a stable identifier, with the thread suggesting BIOS binding as a workaround for the CivilFEM side

Validity context: May-July 2020

License behavior differs by Windows user profile

Problem

The failure appears only with the current Windows user, while another user may behave differently

Possible cause

A user-specific configuration or per-user generated host-id context appears to differ from the other account

Solution

Compare the failing and working user profiles, regenerate the host-id/license context for the active user, and retest under both accounts

Validity context: July 2020

License breaks when the machine identifier changes

Problem

A previously working license stops working after an OS update or hardware change, and the user is left without access until a new file is issued

Possible cause

The license appears to be tied to a changing machine identifier, so a MAC change invalidates the existing binding

Solution

Reissue the license against a stable hardware identifier or a fixed adapter/dongle path; if the problem recurs, collect a fresh host report from the updated machine before generating the replacement

Validity context: July 2020; historical and hardware-dependent

Temporary beta license expires before testing is complete

Problem

The beta version can be installed, but the temporary license is about to expire before testing and benchmarking are finished

Possible cause

The temporary test window is too short for the ongoing validation work

Solution

Extend the temporary license period or replace it with a longer-lived license that covers the needed feature set

Validity context: June-September 2020; tied to a time-limited beta process

CivilFEM 2020 does not start because the license is missing or misconfigured

Problem

The new release does not start; the problem is later narrowed to license availability or license-manager configuration rather than the application itself

Possible cause

The license may not have been assigned yet, or the license manager/configuration is wrong after the installation

Solution

Verify that the correct 2020 license was issued, reload the license file if needed, and check the license-manager configuration before escalating

Validity context: August 2020; tied to the 2020 release and its initial deployment

Windows update causes license communication to fail

Problem

After a Windows 10 update, CivilFEM reports that it cannot find the license, but the problem clears after reloading the license file

Possible cause

The update likely changed the local environment, firewall state, or service communication path, breaking access to the license source

Solution

Recheck the license service and reload the license file; if the issue recurs, inspect firewall and communication settings introduced by the update

Validity context: August 2020; dependent on Windows update behavior

Startup crash while loading Core/Common DLLs

Problem

The application crashes during startup, specifically while loading core components and the update engine, and the same error still appears when trying an older version

Possible cause

A machine-specific runtime or DLL-loading issue is suspected, but the block does not provide enough evidence to isolate the cause

Solution

Try another machine to separate environment from software, and if available collect a crash report or fuller startup log for DLL-level diagnosis

Validity context: September 2020; historical and environment-specific

Beta feature regression in concrete-checking commands

Problem

The beta version’s concrete-checking commands do not work, forcing fallback to an older version for those checks

Possible cause

The beta build appears incomplete or regressed for this command path

Solution

Verify the concrete-checking path against the beta build and compare it with the older version that still works

Validity context: July 2020; tied to beta validation

Temporary license extension for ongoing testing/development

Problem

A temporary license is repeatedly requested to keep a development or benchmarking effort running while testing is still incomplete

Possible cause

The agreed testing window appears to have been too short for the work being done, so the temporary license ran out before validation finished

Solution

Issue a short extension or replacement temporary license for the agreed testing period; the thread also suggests the team may later replace repeated temporary licenses with a permanent commercial arrangement

Validity context: September 2020, especially the `2020-161` thread

License bound to the wrong host or machine identity

Problem

A license works on one machine but fails on another, or after host changes; the user also asks whether renaming the PC will affect activation

Possible cause

The license is tied to machine identity data such as MAC and BIOS, and the wrong host information or a changed host identity breaks it

Solution

Generate a fresh host-ID file from the intended machine, ensure the EULA references the correct MAC/host data, and if needed move to a USB dongle with a fixed network adapter ID

Validity context: Late September to early October 2020

CivilFEM installation planning for a virtual machine with remote access

Problem

The customer wants to deploy CivilFEM on a new VM, asks for optimal hardware requirements, and asks whether remote desktop is allowed

Possible cause

The customer needs the platform requirements and the license type that explicitly permits virtualized and remote use

Solution

Provide the machine information needed for the license request, confirm the license can be local/virtual/remote-enabled, and use the evaluation license path if they want to benchmark performance first

Validity context: September to October 2020, especially the `2020-194` thread

Remote desktop or VM graphics compatibility issue

Problem

CivilFEM appears to run into graphics or rendering problems when used over remote desktop or in a VMware virtual machine

Possible cause

The remote session or virtual graphics driver is not exposing the OpenGL capability CivilFEM expects

Solution

Check the detected OpenGL version in the Administration Utility report, apply the Nvidia patch if applicable, or adjust the Mesa/OpenGL override path if that is the graphics stack in use

Validity context: October 2020

CivilFEM fails or misbehaves in a virtualized/RDP environment due to OpenGL compatibility limitations

Problem

The application behaves differently depending on access method and user account; it works for an administrator but fails for other users, and the issue persists across multiple remote access methods and a virtual machine setup

Possible cause

The virtual GPU/OpenGL emulation in the vSphere/RDP stack is not exposing the required compatibility profile or OpenGL extensions consistently to all users

Solution

Verify vSphere graphics configuration, test the virtual GPU/OpenGL settings, and continue the remote session review. The block also points to a future product-side change to allow core-mode execution, with a temporary fallback to a physical machine or a different remote desktop path

Validity context: Observed across 2020-10-08 to 2020-10-15; still open until the planned remote session and later product change discussion

Security check fail after license/host-ID change

Problem

CivilFEM reports a security validation failure after a Windows update or host information refresh

Possible cause

The license binding no longer matches the machine identifier expected by the license, especially after a host-ID change

Solution

Send the updated Host ID and current license file for regeneration, and provide a report file from the Administration Utility if needed

Validity context: Observed on 2020-10-22 to 2020-10-26

Security check fail caused by special characters in the license file name

Problem

The license starts working after the file name is changed to remove non-English characters

Possible cause

Marc/CivilFEM is sensitive to special characters or spaces in the license file name

Solution

Rename the license file to a simple ASCII name and re-add it with the Administration Utility

Validity context: Confirmed on 2020-10-26 in the same support thread

Marc solver error 0 tied to working path or filename restrictions

Problem

The solver returns error 0 and the message indicates a path or file-name problem

Possible cause

The working directory or file name contains unsupported spaces or special characters

Solution

Move the model files to a simple path without blanks or special characters and rerun the solve

Validity context: Observed on 2020-10-16

Marc solver error 4031 due to insufficient memory on the workstation

Problem

The solver cannot obtain the requested memory during a dynamic request

Possible cause

The machine has too little RAM for the model size

Solution

Increase physical RAM, reduce background memory use, or try batch mode; the block also suggests a temporary virtual-memory workaround, but the recommended direction is more physical memory

Validity context: Observed from 2020-10-19 to 2020-10-26

Download portal and account access failure for CivilFEM installers

Problem

Users cannot reach the CivilFEM download page or cannot log in / pass the portal flow to obtain the software

Possible cause

A website/account-side issue, not a product runtime defect, since the block shows repeated complaints about the download page and account access

Solution

Provide direct installer links while the portal issue is fixed and route the web problem to the technical team

Validity context: Observed on 2020-11-05 to 2020-11-12

CivilFEM crash or rendering failure in vSphere

Problem

CivilFEM did not behave correctly in a virtualized environment, with discussion of a beta build, a service pack, and later a DLL update that changed rendering behavior

Possible cause

Graphics-driver or anti-aliasing incompatibility in the VM environment, with a software-side workaround via an updated View3dEngine DLL

Solution

Test the updated DLL or service pack, disable unsupported anti-aliasing behavior, and validate the fix in the target VM using remote access

Validity context: October 15-December 17, 2020

CivilFEM crashes or fails to start in remote sessions on a virtual machine

Problem

CivilFEM works for one user or on one access path, but crashes or fails to operate when the same virtual machine is accessed through RDP or similar remote tools

Possible cause

The emails point to OpenGL/WDDM remote-session handling as the likely cause, especially under VMware and Windows Remote Desktop

Solution

Test the suggested remote-graphics workaround in the thread: change the remote-session WDDM setting, reboot, and retest. If needed, use a non-RDP remote method and verify with the Administration Utility report

Validity context: Dec 17-23, 2020

User-specific OpenGL environment mismatch blocks CivilFEM/Mentat for one account

Problem

CivilFEM opens for the administrator account but not for a domain user, and Marc Mentat then shows an error for the affected user

Possible cause

The block indicates a missing per-user Windows environment variable, with different OpenGL versions detected between the administrator account and the affected user

Solution

Add the environment variable to the affected user, reboot, and retest. Keep the remote-session graphics workaround in place if the issue persists

Validity context: Dec 21, 2020

Virtual/RDP licensing needs migration from node-locked to floating licenses

Problem

CivilFEM and Marc eventually work after the licensing model is changed, but the earlier node-locked virtual setup does not behave correctly in the remote environment

Possible cause

The block explicitly says the initial virtual machine license was node-locked and that Marc did not allow RDP in that licensing mode

Solution

Replace the node-locked licenses with floating licenses, install the license servers, and point CivilFEM and Marc to the configured license endpoints

Validity context: Dec 22-23, 2020

CivilFEM installation remains unresolved on a new Windows machine

Problem

The same install problem appears on a replacement machine, and the user is unsure whether Linux on another partition is related

Possible cause

Not established in the block. The support thread asks for the exact error, screenshots, and a report from the Administration Utility

Solution

Collect the exact error context, a screenshot, and the Administration Utility report; confirm the Windows partition and install path being used

Validity context: Sep-Dec 2020

Offset formulas mis-evaluate when using bracketed vectors

Problem

The offset parameter behaves strangely when formulas are used, especially when vectors are entered in bracket form

Possible cause

The thread explicitly describes a bug in result representation and formula evaluation being converted to the active coordinate system when it should not be

Solution

Work around it by switching to the global coordinate system before editing offsets; a fix was promised for a later update or release

Validity context: Dec 18-23, 2020

CivilFEM loses license after update or server reset

Problem

After an automatic software update, CivilFEM no longer obtains a license, even though the user believes the network and antivirus state are unchanged

Possible cause

Not proven in the block. The support replies suggest investigating license-server delivery, connectivity, firewall/antivirus interference, and possible ISP or public-IP changes

Solution

Verify the license server status, client-server connectivity, firewall/antivirus settings, and the configured public IP. If necessary, reconnect with support and compare server reports

Validity context: Dec 31, 2020-Jan 4, 2021

CivilFEM crash in a virtualized/RDP environment

Problem

CivilFEM visualization or startup failed in a VMware/RDP setup, with follow-up confirmation that the issue was tied to the environment rather than a simple install failure

Possible cause

OpenGL compatibility mode was not supported by the virtualization drivers, and the setup also needed a Windows environment variable plus a different license mode for RDP use

Solution

Switch OpenGL from compatible to core, set the OpenGL override environment variable, use the corrected DLL or Service Pack, and move from node-locked to floating licensing for the virtual machine

Validity context: Late December 2020 through early January 2021

CivilFEM installation/startup failure on a Windows desktop after reinstall or update

Problem

The software kept failing after reinstalling, updating, or moving to a new desktop; the same error persisted and a crash report was attached

Possible cause

The block does not confirm a single cause. The thread suggests environment-specific issues such as Windows-versus-Mac setup, Windows updates, or a user-profile problem, but this is not proven

Solution

Test on a standard Windows installation, try a fresh English-named user profile, verify Windows updates, and inspect the attached crash report for a narrower failure signature

Validity context: December 2020 to January 14, 2021

CivilFEM and Marc floating-license server setup shows empty feature list

Problem

After following the server-license setup steps, the LM-X License Server showed an empty feature list, so the client could not connect

Possible cause

The license-server configuration or uploaded license files were not being registered correctly. The block does not prove whether the issue is in the server install, the .lic/.dat content, or the version mismatch

Solution

Re-check the license-server configuration against the reference video, verify the license files are loaded into the server correctly, and confirm the features appear before testing the client connection

Validity context: January 11 to January 20, 2021

CivilFEM crashes or fails during installation on Windows

Problem

The application keeps crashing or showing the same error after installation attempts and follow-up fixes

Possible cause

A bad environment variable, missing runtime dependencies, or a machine-specific Windows setup issue; the thread also raises a Windows-on-Mac/partition question

Solution

Verify and remove the suspect environment variable, reinstall missing runtime dependencies, and collect crash diagnostics if the error persists

Validity context: Supported by a January 2021 install thread and a later dependency-based workaround in early February 2021

License renewal file is not taking effect until older files are removed and the service is restarted

Problem

The new license date does not appear to change, or the software still behaves as if the old license is active

Possible cause

Older license files remain installed, or the LM-X license service was not restarted after the new file was applied

Solution

Remove older license files, restart the LM-X licensing service, and verify the updated license file is the only one loaded

Validity context: Clear in the January 27-February 1, 2021 renewal thread

License server access fails despite an apparently open port

Problem

The LM-X server reports the license, but CivilFEM still cannot run from the client side

Possible cause

Firewall exception is only port-level instead of process-level, or router/client-server forwarding is incomplete

Solution

Validate the server-client path end-to-end, add a process exception for the LM-X service binary, confirm router forwarding if applicable, and check client logs

Validity context: Explicitly discussed on January 26 and January 27, 2021

CivilFEM powered by Marc license generation and server setup are unclear

Problem

The user asks how to activate the expert version, whether a license server is needed, and how to proceed after providing host data

Possible cause

The deployment path is ambiguous between student and expert installs, and between local and network licensing

Solution

Confirm whether the target is a local or server license, provide the correct installer path, and supply the license-server setup instructions for the Marc-based workflow

Validity context: Supported by the February 2-3, 2021 host-ID and license-server exchange

CivilFEM expert activation for Marc is confused with the student package

Problem

The user installs the student version but asks how to enable the expert version

Possible cause

The student bundle includes a student Marc component, and the commercial expert package is a different installer/license path

Solution

Use the commercial installer for the expert edition and follow the correct install/configure path for the selected license type

Validity context: Explicit in the February 3-4, 2021 exchange

Student-to-commercial access transition for CivilFEM powered by Marc

Problem

A user could not log in to the distribution portal and could not activate or obtain the commercial edition after initially downloading the student build

Possible cause

The account role/access state was still aligned with the student workflow, so the user could not reach the commercial installer area until access was changed

Solution

Update the user role/access, provide the correct commercial installer entry point, and confirm the user can download the commercial package from the distributor portal

Validity context: Observed in early February 2021; references only apply to the CivilFEM 2020 commercial/student split used in that thread

CivilFEM installation crash linked to dependency/library conflict

Problem

CivilFEM failed to start correctly on a university machine, and the user reported that installing the suggested runtime dependency did not fix the issue. Crash reporting pointed to a Windows library

Possible cause

A conflicting software installation, driver, or system-library issue was suspected, but the block does not prove a root cause

Solution

Reproduce the crash with diagnostic tooling, collect a dependency report and crash report, and check whether another installed application or system component is interfering

Validity context: Early February to early March 2021; the thread explicitly treats the problem as unresolved at the time of the exchanged messages

License-server setup confusion between nodelocked and network licenses

Problem

A server-side license setup did not work because the wrong license file was associated with the server, and the user initially tried to download or run server software for a license that was not server-based

Possible cause

Wrong license type was applied to the wrong machine, including confusion between a network license and a nodelocked license, plus a host mismatch in one of the license files

Solution

Install the 30-user server license on the license server, install the two nodelocked licenses on their respective computers, and configure clients to point to the server with the administration utility

Validity context: March 2021; the thread explicitly distinguishes server-side and nodelocked behavior for that installation

Solver engine not found during CivilFEM solve

Problem

When solving any model, the user got a solver-engine-not-found error and could not complete analysis

Possible cause

The thread points to a CivilFEM Student installation that may not have the matching MSC Marc Student component, or to a mismatch between the installed CivilFEM package and the required solver package

Solution

Confirm the correct MSC Marc installer is present, use the proper CivilFEM installation for the license type, and generate an Administration Utility report for diagnosis

Validity context: March 2021; the support guidance is explicitly tied to CivilFEM 2020 and the student/commercial installer split

Student installer download portal access

Problem

A registered user could not find the student installer download location on the portal

Possible cause

Portal navigation or access-path confusion; the block does not show a technical failure in the installer itself

Solution

Provide the student-portal entry point and the direct student installer / installation guide links, then confirm the account can reach the download area

Validity context: Late February to early March 2021

CivilFEM Student install cannot find the solver engine

Problem

Solving any model triggers a solver-engine not found error

Possible cause

The CivilFEM Student installation is missing the matching MSC Marc Student component, or student and commercial components were mixed

Solution

Install the correct MSC Marc Student package, generate the CivilFEM Administration Utility report, and verify the setup in a remote session if needed. The thread later indicates the local machine reset made it work, which points to an environment-side issue rather than a product defect

Validity context: March 16-18, 2021; CivilFEM 2020 student/commercial installer behavior

Mesh command fails because Mentat log file is missing

Problem

Running Mesh fails immediately with a Mentat log file not found error, including on example models

Possible cause

Mentat integration or local configuration is broken, or a local security/tooling issue is blocking the expected runtime path

Solution

Verify Mentat installation and configuration via the report file, then reproduce in a live remote session. The thread also suggests checking antivirus/security software

Validity context: April 14-16, 2021; CivilFEM 2020 / Mentat configuration

CivilFEM license server setup and HostID-based activation

Problem

The customer wants the license on a server for multiple workstations and needs the LM-X server package plus activation steps

Possible cause

The license must be generated from the intended server HostID and then paired with the correct LM-X server setup; the exact CivilFEM product family is not explicit enough from the block alone

Solution

Run the LM-X configuration tool on the intended server, send the generated text file, and follow the license-server installation guidance before issuing the server license

Validity context: March 18-April 13, 2021; version-bound licensing guidance

Latest CivilFEM download access is blocked by portal role/account confusion

Problem

The user cannot find a download link in the profile, is initially steered toward student access, and later needs commercial download access for the latest version

Possible cause

Portal role or credentials are not set correctly for the intended customer download path

Solution

Confirm the correct portal role and credentials, then use the client portal or the shared commercial installer for the requested release

Validity context: May 21-28, 2021; refers to the 2020 release and the upcoming 2021 beta

CivilFEM customer portal access and account role misassignment

Problem

The customer could not access the CivilFEM download area with the correct permissions and was being treated as a student instead of a client

Possible cause

Account role / portal entitlement mismatch

Solution

Change the portal role from student to client and reuse the already issued 2020 delivery; no new server software upgrade was required in the thread

Validity context: Resolved in-thread on 2021-05-31

Misunderstanding about updating the LM-X license server versus updating only the license file

Problem

The user believed the license server software had to be updated to 2020 in order to use the new CivilFEM license

Possible cause

Confusion between license-server software version and the license file replacement process

Solution

Keep the existing license-server software, install the new license file on the current CivilFEM LM-X License Server, and follow the installation video referenced in the thread

Validity context: Resolved in-thread on 2021-05-31

ITB license-server detection failure during CivilFEM installation

Problem

CivilFEM and/or the license tools reported that the license server was not running, the host was not found, and a report file could not be accessed

Possible cause

Not established from the text. The support replies suggest firewall blocking, license-server configuration issues, or problems with the shared license server/hostname resolution

Solution

Review the license-server configuration directly with the customer, verify host resolution and communication to the license server, and use remote support if needed

Validity context: Resolved by 2021-06-08 after the customer reported it was working, but the exact fix is not stated

CivilFEM 2021 license file was generated incorrectly for the target machine

Problem

CivilFEM 2021 would not launch correctly after installation; the support report pointed to mismatched or missing license components

Possible cause

A license file was generated for the wrong computer or the package was malformed during generation, so the installed license set did not match the intended machine

Solution

Regenerate the license for the correct computer, ensure the replacement license is paired with the previous required component, and reinstall through the Administration Utility or with support assistance

Validity context: July 21, 2021 to August 4, 2021

CivilFEM license update was misunderstood as an expiration change

Problem

the new license did not change the expiration date and asked why it had been sent

Possible cause

The communication appears to have been about a new software version rather than an extension of the existing expiration period

Solution

Clarify that the license accompanied a new version, confirm whether the customer should update to that version, and preserve the existing .dat file if applicable

Validity context: August 5 to August 6, 2021

Server-based CivilFEM license was updated in the wrong place

Problem

The customer followed the usual update procedure but the license still did not reflect the expected change

Possible cause

The license was a server license, so updating it through the local Administration Utility was not the right process

Solution

Update the license on the LM-X license server instead of the local utility; use the guided remote session or the referenced procedure if needed

Validity context: August 5 to August 6, 2021

CivilFEM Academic installer fails to run because the downloaded EXE is incomplete or corrupted

Problem

Running the downloaded CivilFEM Academic EXE returns a Windows error that the app cannot run on the PC

Possible cause

The download was likely incomplete/corrupted, or Windows/software interference prevented the self-extracting installer from running

Solution

Re-download the full installer, verify the file size/icon, try the installer on another PC, or extract the self-extractor and use the internal installers

Validity context: Valid for the August 2021 Academic installer thread

License error on CivilFEM due to machine identifier mismatch and removable USB dongle behavior

Problem

CivilFEM reports a license error even after the license is updated in Administration Utility

Possible cause

The license was linked to a different machine identifier than the active machine, and the later thread indicates a USB dongle-like device may have been involved; the problem was not caused by the 2020 vs 2022 version number

Solution

Verify that the active machine identifier matches the licensed machine, ensure the old and new license files are both being referenced as instructed, and check hardware/dongle seating if applicable. A remote session was offered as a fallback

Validity context: Valid for September 2021, with explicit follow-up confirmation that the issue was resolved by moving the USB device to a different port

License server access fails because the active license set was expired

Problem

Access to the CivilFEM server/licensing path fails and the user says it is not an installation or program error

Possible cause

The block later states the licenses had expired on 1 August, which explains the failure

Solution

Issue updated licenses and confirm the client updates them successfully. A remote session was offered if the problem persisted

Validity context: Valid for late August 2021

CivilFEM 2021 will not install on older Windows systems

Problem

A user could not install CivilFEM 2021 on a Windows 7-era machine and asked whether the license could be moved between computers

Possible cause

The thread points to OS compatibility limits and dependent tooling constraints rather than a product defect; the support reply attributes the install difficulty mainly to older Windows support and MSC requirements

Solution

Use a supported Windows version, verify whether the workflow depends on MSC, and confirm that any USB dongle license is attached when moving between machines

Validity context: September 15-16, 2021

CivilFEM setup crashes with an unexpected error report

Problem

An installer-generated crash report appears during CivilFEM installation

Possible cause

Not established in the block. Support asked for a screenshot, the generated report, repro steps, and whether the issue recurs

Solution

Collect the crash report, screenshots, and exact steps to reproduce before trying to classify the failure

Validity context: September 16, 2021

Cracked section analysis fails because the command cannot find valid load steps

Problem

The CONRELAX-based cracked section workflow reports that the feature is unavailable or that a load step number is not found

Possible cause

The final support diagnosis says the script/model is missing the required mechanical and thermal load steps, though the thread also explored license-server behavior and a license-feature mismatch earlier

Solution

Verify that both required load steps exist and are readable in the RCV file, then test with the provided simple example model

Validity context: September 17-21, 2021

CivilFEM 2021 downloads are incomplete or corrupt

Problem

The installer downloads stop short of the expected size and cannot be installed on any machine

Possible cause

The thread points to incomplete downloads from the server or the user’s connection, with the installer possibly being truncated or corrupt

Solution

Retry with a browser or download manager that can resume partial downloads, and verify the installer size before запускing it

Validity context: October 5-6, 2021

Installer download fails or produces an incomplete CivilFEM package

Problem

The user could not reliably download the full installer from the provided link, and support asked them to confirm the file was larger than 1 GB and to retry if needed

Possible cause

Likely incomplete download, transfer issue, or browser/server handling problem. The emails suggest the download source was fine from one side, but the user experienced failures

Solution

Ask the user to retry with the direct link or browser copy/paste approach, and verify the installer size before installation

Validity context: Confirmed in October 2021; no root cause was established in the block

CivilFEM installation problem with missing or incomplete setup details

Problem

A student reported that CivilFEM would not install cleanly or the issue remained unresolved after multiple exchanges, but the exact error was never provided in the text

Possible cause

Unconfirmed. The block only shows that support requested an error message or screenshot and asked the user to confirm they had downloaded the full installer

Solution

Collect the exact error text or a screenshot and confirm the installer package integrity before further troubleshooting

Validity context: Historical thread from October 2021; the underlying failure mode is not identified

Direct download / registration portal access issue for CivilFEM setup and license manager

Problem

The user could read a PDF but said internet installation was restricted and asked where to download the application and license manager; support then supplied direct links and registration guidance

Possible cause

Likely organizational internet restrictions or webpage access friction rather than a software defect

Solution

Use direct download links, try another browser if the web page fails, and if commercial use is needed, submit Host-ID information to the Secretariat for license handling

Validity context: Confirmed in early October 2021; the thread was eventually closed after the user said the download worked

Solver error when resolving in CivilFEM Student/commercial setup

Problem

The user could mesh successfully but got a repeated error only when resolving, across 2D and 3D cases; support suspected the student installation, wrong version detection, or missing Marc/Mentat features

Possible cause

Likely misdetected or incomplete Marc/Mentat installation, or a mismatch between CivilFEM 2020 and 2021 state in the machine configuration. The block also mentions path detection not working correctly and the absence of Marc/Mentat features in the report

Solution

Re-select Marc 2020 and Mentat 2020 in CivilFEM settings, ensure the configuration is saved with OK, and if the problem persists, do a remote support session or reinstall while checking DLL/environment conflicts

Validity context: October 2021; several follow-ups show the issue was still under investigation and not conclusively solved in the block

CivilFEM version speed-test workflow breaks due to macro/run naming or working-directory setup

Problem

The speed-test run required changing the working directory in a macro, and later messages mention that some windows kept opening and the macro name or job setup caused trouble

Possible cause

Likely a scripting or job-setup issue in the benchmark workflow, not the solver itself. The block shows manual path replacement and later troubleshooting around macro names and dialogs

Solution

Normalize the macro names, verify the working-directory substitution, and rerun the benchmark with the intended folder structure

Validity context: October 2021, but the benchmark itself refers back to a 2019 test case

Simplified Chinese labels and tooltips are incomplete or incorrect in CivilFEM 2021

Problem

Several UI labels and tooltips in the Simplified Chinese translation needed correction, including wording in geometry items and hover text

Possible cause

Translation/content issue in the UI language files, not a runtime defect

Solution

Update the language file, verify the renamed labels and tooltips in the application, and include the corrected file in the next CivilFEM update

Validity context: Confirmed in October 2021 and appears to have been resolved in the thread

CivilFEM license move / floating-license conversion from an old Windows 7 machine

Problem

A license file was attached to a Windows 7 machine and needed to be moved to Windows 10, with an additional request to convert to floating licenses

Possible cause

License binding to the original machine or server. The thread indicates a new Host-ID would be needed for reissue or for a license-server-based setup

Solution

Generate Host-ID for the destination machine or license server, then send it to the Secretariat to request a moved or floating license

Validity context: October 2021; the compatibility concern is historical and environment-specific

CivilFEM 2021 crashes or shows an error on Windows 7

Problem

The program errors when opening or when reaching the solve stage on Windows 7; the user reports repeated failure even after following prior steps

Possible cause

Windows 7 incompatibility in CivilFEM 2021, with support explicitly saying the issue exists on Windows 7 and that a service pack was being prepared to fix it

Solution

Install the referenced service pack/beta build, or move the case to a remote session if it still fails

Validity context: October-November 2021

CivilFEM 2021 cannot be installed or run on an older Marc/CivilFEM setup without the service pack

Problem

The user downloads the CivilFEM 2021 package but reports that CivilFEM is not installed on the machine or that the setup is too complex to complete

Possible cause

The package requires CivilFEM 2021 plus Marc 2020 components and, on Windows 7, the compatibility fix/service pack

Solution

Install the full CivilFEM 2021 package first, then apply the Windows 7 service pack; if needed, use remote assistance

Validity context: November 2021

Marc model convergence issue for a tracker structure

Problem

The model must converge in Marc before the CivilFEM workflow can proceed

Possible cause

The structure does not converge in Marc; no deeper cause is established in the block

Solution

Work the model in Marc first and use the Marc convergence result as the prerequisite for the CivilFEM step

Validity context: November 2021

Local license must be moved to a new Windows 10 computer

Problem

A local license tied to a Windows 7 machine needs to work on a new Windows 10 machine, or be converted to floating licensing

Possible cause

The license is node-locked/local and tied to a specific Host-ID

Solution

Generate a new license file from the new machine’s Host-ID, or set up the required license server components for floating licenses

Validity context: October-November 2021

CivilFEM 2021 crashes or fails on Windows 7, with a beta fix and Marc DLL workaround

Problem

CivilFEM 2021 produces crash reports or fails during startup or geometry selection on Windows 7; related Marc 2020 issues are also discussed in the same thread cluster

Possible cause

Likely a Windows 7 compatibility defect acknowledged by support. The thread also ties Marc 2020 failures to the same unsupported OS context

Solution

Install the referenced beta service pack, and if Marc 2020 still fails, apply the manual DLL-copy workaround described in the thread

Validity context: Nov 16 to Nov 19, 2021, historical support context

CivilFEM by Marc student installation does not launch Marc correctly on Windows 11

Problem

CFLauncher asks to launch the Marc installer, then nothing happens and CivilFEM continues installing; the Marc solver is also reported as incompatible with Windows 11

Possible cause

Likely an old CivilFEM 2020 installer and/or leftover Marc installation state, combined with Windows 11 incompatibility for the Marc Student component at that point in time

Solution

Use the latest CivilFEM 2021 installer, uninstall previous Marc installations, remove leftover Marc files if present, reboot, and retry. The thread also suggests checking Marc’s student edition separately

Validity context: Nov 15 to Nov 25, 2021, historical support context

CivilFEM installer download appears incomplete or truncated

Problem

The user reports repeated failed downloads of the CivilFEM installer, with the file size changing between attempts and ending smaller than expected, followed by an installation error when starting the setup

Possible cause

The installer package may be incomplete, corrupted during download, or not being delivered reliably through the current download path

Solution

No final fix is shown for the download-size mismatch; the thread moves on to alternative delivery and later license/crash troubleshooting

Validity context: Observed from 2022-01-04 through 2022-01-05; unresolved in the excerpt

CivilFEM crashes after license application on Windows 11, with Administration Utility becoming unresponsive

Problem

After applying the received license file, the Administration Utility stops responding, the install completes only after force-closing it, and CivilFEM then fails to start with an error window

Possible cause

The block suggests a compatibility issue with Windows 11, plus a separate non-blocking Administration Utility hang caused by environment-variable broadcast behavior

Solution

Support asked for crash reports and an Administration Utility report, suggested redistributables and Nvidia driver updates, and arranged a remote assistance session; one internal note says the no-response behavior is expected and will be fixed in a later version

Validity context: Observed from 2022-01-05 to 2022-01-06; still open at the end of the excerpt, with remote support scheduled

LM-X license server stops frequently or fails to create the service after installation/migration

Problem

The license service reportedly stops repeatedly, later does not get created after LM-X License Server installation, and the customer asks for help migrating the license to a new server

Possible cause

The thread points to a license-server installation or migration issue, possibly tied to the installer version, service setup, license file, or server-specific configuration, but the exact product family is not explicit

Solution

Support recommended reinstalling the license server, generating a new Host ID, obtaining a new license file, and escalating to the vendor if the issue persists; remote assistance was scheduled

Validity context: Observed from 2021-12-28 to 2022-01-07; unresolved in the excerpt

LM-X license server installed but the CivilFEM service is not created

Problem

After installing the LM-X License server, the service is reported as not being created and online support is requested

Possible cause

The block does not confirm the root cause; the issue appears tied to license-server setup or service registration during installation

Solution

Remote assistance was proposed, and the thread moved to license-file handling and connectivity checks

Validity context: January 5-7, 2022, during support case 2021-117

CivilFEM 2021 startup crash and Script Help no-response behavior on Windows 11

Problem

The application crashes at startup, Script Help shows no reaction, and the Administration Utility behaves unexpectedly during setup

Possible cause

CivilFEM 2021 is repeatedly discussed as not officially supporting Windows 11 at that time, with the possibility of third-party software interfering with dependencies

Solution

Support suggested redistributables, updated graphics drivers, a special testing build, and remote verification

Validity context: January 5-25, 2022, with explicit Windows 11 references in the thread

Downloaded CivilFEM installer is incomplete or corrupted

Problem

The user repeatedly downloads the installer but gets the same execution error, and the browser indicates the file did not download correctly

Possible cause

The installer download is incomplete or corrupted rather than a product runtime bug

Solution

Support advised re-downloading the file, checking the browser download status, trying another browser or download manager, and using alternate download links

Validity context: January 11-12, 2022

License file version mismatch prevents CivilFEM 2021 from showing products

Problem

CivilFEM launches but no products are available, or the new version does not recognize the existing license set

Possible cause

The available license is for CivilFEM 2020, while the user is trying to run CivilFEM 2021; the license file may also be near expiry

Solution

Support indicated that a newer CivilFEM 2021 license file would be needed, and if staying on CivilFEM 2020 the firewall and older-version licensing should be checked

Validity context: January 12-17, 2022

CivilFEM 2020 meshing fails because the Marc server version is incompatible

Problem

CivilFEM 2020 opens, but meshing fails with a log/file-related error, while the same workflow works in CivilFEM 2019

Possible cause

The license-server version used with CivilFEM 2020 is not compatible with the Marc version used by that CivilFEM release

Solution

Support said the Marc license server version used by CivilFEM 2020/2021 should be installed from the corresponding installer, and remote assistance was offered

Validity context: January 24-25, 2022

CivilFEM LM-X license server stops frequently and causes repeated license downtime

Problem

The CivilFEM service/license server stops repeatedly, including reported downtime every 1 to 2 days, and the server event log shows `lmx-serv.exe` faults

Possible cause

Likely an LM-X security library or driver issue, with support also considering network or machine-configuration interference

Solution

Test the updated LM-X/CivilFEM license-server build, collect LM-X logs and config files, and use temporary local licenses while troubleshooting continues

Validity context: Active in late January through mid-February 2022

CivilFEM 2020/2021 license compatibility and version-bound activation failure

Problem

Existing licenses work on CivilFEM 2019, but CivilFEM 2020/2021 does not recognize them or requires new license files; users ask for replacement licenses and server updates

Possible cause

License entitlements appear tied to specific CivilFEM versions, and support also points to a Marc-server version mismatch for newer releases

Solution

Generate version-appropriate license files and align the license-server/MARC version with the CivilFEM release in use

Validity context: Active from 2022-01-24 through 2022-02-15

CivilFEM 2021 / Windows 11 installation and beta-test startup issue

Problem

CivilFEM 2021 is reported as not supporting Windows 11, causing installation delays; the standalone test build also appears to do nothing when launched on the workstation

Possible cause

OS compatibility problem with CivilFEM 2021 and Marc, plus a separate failure to launch the test build on the workstation

Solution

Use the special Windows 11 build or fall back to CivilFEM 2020/2019 for testing; if the workstation still fails, continue remote troubleshooting

Validity context: Active in January and early February 2022

CivilFEM 2020/2019 on Windows 11 with installer mismatch and expired license

Problem

The 2020 installer was reported as not fitting the PC, apparently because of Windows 11, while the installed 2019 version started but the license looked expired

Possible cause

The text suggests a possible Windows 11 compatibility issue and a separate expired-license problem, but neither is confirmed as the final root cause

Solution

Re-check that the installer download is complete, verify compatibility with the PC/Windows version, and issue a new license file if the current one is expired. Remote assistance was also discussed

Validity context: January-February 2022

LM-X CivilFEM license server stops unexpectedly and will not stay running

Problem

The CivilFEM LM-X license server/service starts, then later stops again; the user reports it stopped after February 24, 2022 and that restarting the service fails or produces no application-log error

Possible cause

The block points to an external exit signal or another process stopping the service; the LM-X team asks for Event Viewer logs, system/application logs, and checks for antivirus or other software/services that could be interfering

Solution

Collect the latest LM-X license-server log plus Windows Event Viewer Application and System logs, review installed services and antivirus, then use the scheduled online support session with LM-X/X-Formation

Validity context: Active from February 21, 2022 through March 7, 2022; still unresolved at the time of the latest troubleshooting messages

Local license file initially fails for one user, then is replaced with a working file

Problem

A specific user cannot load a local license file; after multiple attempts, a new local license is generated and reported as working

Possible cause

The block does not prove a root cause; the likely issue is that the earlier license files were invalid for that user or computer

Solution

Replace the local license file, verify it activates on the target machine, and confirm the user can run CivilFEM afterward

Validity context: Active on February 24 to March 1, 2022; confirmed working by February 28, 2022

CivilFEM fails to open correctly on a virtualized MESA/OpenGL setup

Problem

CivilFEM does not open correctly on a machine that is described as using a virtualized MESA environment; a related environment-variable change is discussed

Possible cause

The block suggests an OpenGL/MESA compatibility issue, with the environment variable value needing adjustment and a report requested if the problem persists

Solution

Verify the MESA OpenGL environment variable on the VM, restart the machine, and generate a CivilFEM Administration Utility report if the failure remains

Validity context: Active on March 2 to March 4, 2022; the user later reports the application became operational again

CivilFEM 2020 installer/download and license behavior on Windows 11

Problem

The user reports that the CivilFEM 2020 installer does not fit this PC, suspects Windows 11, and later says the 2019 version shows a connected license but still will not start

Possible cause

The block suggests a combination of installer/download issues and license problems; the installer size is questioned, and the team recommends re-downloading and testing CivilFEM 2020 rather than staying on 2019

Solution

Re-download the installer, confirm the archive is complete, test CivilFEM 2020, and replace the license file if needed; remote assistance was offered

Validity context: Active from February 23 to February 28, 2022, with follow-up confirming the 2020 install was obtained and then a license fix was pursued

License server service appears to run, but the LM-X vendor DLL keeps disappearing and the log stops updating

Problem

The service is reported as running, but the log file stops updating and the license behavior becomes inconsistent; the thread also mentions the issue returning after a specific date and a missing DLL on the machine

Possible cause

The support team believed a required license-server DLL was being removed from the computer, with antivirus or Windows Defender suggested as likely causes

Solution

Test the signed replacement DLL, keep a backup of the original, restart the service if needed, and verify behavior from another computer before repackaging the installer

Validity context: March 2022

Student installer download/extraction fails on multiple PCs

Problem

The student-version installer appears to download but fails during extraction or does not complete correctly on more than one machine

Possible cause

The download appears to be incomplete or corrupted, or the transfer path is being blocked; the support team moved the installer to an alternate delivery method

Solution

Retry the installer from the alternate delivery channel and confirm the archive completes correctly before rerunning installation

Validity context: April 2022

CivilFEM runs poorly on specific workstations unless a locale workaround is applied

Problem

Installation itself is reported as fine, but launching CivilFEM on some computers produces an error; the user then reports that the issue seems tied to a specific PC and Windows Defender

Possible cause

Support described this as a known issue on very few computers and recommended disabling the code path with an environment variable

Solution

Set `CF_USERLOCALE=no` in Windows environment variables and retest; if it still fails, use online support to walk through the workaround

Validity context: April 2022

Meshing failure in CivilFEM model does not appear to be license-related

Problem

The user cannot mesh a model and suspects Marc licensing, but support reports the same model meshes successfully on their side

Possible cause

Support’s first pass suggests the issue may be related to the work path or model-specific setup rather than licensing

Solution

Share the model and report, then use remote assistance or run targeted checks on the work path and related settings

Validity context: April 2022

License migration to a new server requires reissued files and machine data

Problem

The customer is changing servers and is asked to send generated machine data plus a completed machine-change form before new licenses can be issued

Possible cause

The license is tied to the old machine/server configuration and needs regeneration for the new host

Solution

Run the configuration tool, submit the generated text file and change form, then install the newly issued licenses on the new server

Validity context: March 2022

CivilFEM download link mismatch in training material

Problem

A user reports that the installation guide points to the wrong download target, and the follow-up confirms the link sent was for the commercial package instead of the student one

Possible cause

A wrong or outdated download link was included in the manual or forwarded instructions

Solution

Correct the manual and keep the proper Student/Commercial download paths aligned with the intended package

Validity context: Observed in early May 2022; historical only

Installer downloads fail because the host is unreliable or the file is incomplete

Problem

The download completes incorrectly or the installer cannot be loaded; multiple users report similar download problems in the same period

Possible cause

The hosting/download path was unstable, and at least some installers were incomplete or failed mid-download

Solution

Retry the download, verify the browser did not report errors, and use alternate mirrors or transfer links when available

Validity context: Observed in June 2022; the block says this affected multiple customers at the time

CivilFEM license server migration requires a machine change and TECS renewal

Problem

A customer asks how to move CivilFEM licensing to a new server during a migration and whether the existing license can be reused

Possible cause

The block indicates the license is tied to the current machine and the renewal status affects whether the change is free

Solution

Request a change of machine, and if possible renew TECS before moving the license server; support can then help install the key on the new host

Validity context: Observed in May 2022; the renewal discussion is tied to an expired maintenance period

CivilFEM and MSC license servers conflict on the same port

Problem

A report and screenshots indicate license communication problems in a mixed CivilFEM/MSC environment

Possible cause

The block says both license servers used the same port, and the MSC license server may also have had the wrong license file or a firewall/communication problem

Solution

Separate the ports, reinstall the MSC license server with the correct file, and then check firewall or connectivity issues if the problem remains

Validity context: Observed in June 2022 and confirmed as working after the fix

Service Pack update fails or starts with an error

Problem

CivilFEM starts an automatic Service Pack update, then an error appears and the update does not complete

Possible cause

Lack of administrator privileges was suspected, and support also mentioned a possible hosting/download issue

Solution

Retry the update with administrator rights; if it still fails, review the error screenshot and the download/update path

Validity context: June 16, 2022

Nodelocked MARC license only works locally, not over Remote Desktop

Problem

The MARC license works on direct local access but produces an error when the workstation is used remotely

Possible cause

The license is nodelocked, so it is intended for local use only and not for remote access sessions

Solution

Use the software locally with the dongle attached, or switch to a server license if remote work is required

Validity context: June 28 to June 29, 2022

License core count and MARC feature recognition mismatch

Problem

The installed license initially appears limited to 4 cores, and later the MARC features are not detected correctly

Possible cause

The default license was issued with 4 cores, and support later suspects the MARC license feature/path handling is not being picked up correctly

Solution

Issue a license with the required core count, and if the MARC feature is still missing, move the license file to a shorter path and update the administration utility

Validity context: June 27 to June 30, 2022

Research license provisioning and HostID-based installation flow

Problem

A research/academic user needs a license bound to one machine, then later needs guidance on which CivilFEM/Marc version to install

Possible cause

The license is tied to the HostID of the target computer, and the student version of Marc imposes limits that the research license is meant to remove

Solution

Generate the HostID-based license, install the commercial CivilFEM 2022 / Marc 2022.1 stack, and follow the provided installation instructions

Validity context: July 11 to July 27, 2022

Student installation / license failure after version mismatch

Problem

Student users report license failures, security check failures, or a license not being initialized after installing older or mismatched CivilFEM/Marc versions

Possible cause

Support points to an outdated installation mix, especially CivilFEM 2021 with Marc 2020 or the student edition instead of the newer CivilFEM 2022 / Marc 2022.1 stack

Solution

Uninstall the older CivilFEM and Marc components, install the 2022 versions, and send the 2022 report file if the problem remains

Validity context: July 18 to August 3, 2022

Large-model performance and graphics selection

Problem

A large model lags while rotating, zooming, and selecting entities, and node merges take far longer than expected

Possible cause

The model size and merge strategy are likely driving the slowdown; support also suggests the graphics selection may be using the wrong adapter

Solution

Force CivilFEM to use the discrete GPU in Windows or NVIDIA settings, switch to wireframe/line display, split node merges into groups, and share the model if deeper analysis is needed

Validity context: July 27 to August 3, 2022

Old LM-X license server version blocks a course setup

Problem

A course environment reports a rejected license-server response because an older LM-X server version is still present

Possible cause

The local license server is outdated relative to the current CivilFEM release

Solution

Remove or update the old LM-X License Server so the site is on the current supported version

Validity context: August 1, 2022

Solver fails on large structural model because the Marc security/input limit is exceeded

Problem

Error 13 appears when solving a large tower model; the model resolves up to a point and then fails as the number of structural elements grows

Possible cause

The Marc license security code depends on the input size, and the input becomes too large when the model contains too many structural elements

Solution

Reduce the number of structural elements, for example by using polylines/continuous columns instead of one structural element per floor; a later service pack was said to reduce input size further

Validity context: Reported across late August and early September 2022; partially addressed by a service pack released in early September 2022

Solver failure after merge because a beam collapses onto overlapping nodes

Problem

The solve fails, but the root cause is no longer the input limit; the solver output points to a specific beam and element after a merge operation

Possible cause

A merge operation produced a collapsed element, with two superposed nodes on the affected beam

Solution

Inspect the solver `.out` file, search for the word error, and check for overlapping nodes or collapsed geometry; the support note also mentions checking node distances below 1 mm

Validity context: Diagnosed on 2022-09-09; this is a different failure mode from the earlier input-limit issue

CivilFEM 2022 errors after removing CivilFEM 2021, with reinstall as workaround

Problem

After updating to CivilFEM 2022 and uninstalling CivilFEM 2021, models started showing new errors; a reinstall of CivilFEM 2022 fixed the issue

Possible cause

The installation or licensing state became inconsistent after removing the older version

Solution

Reinstall CivilFEM 2022; if the issue returns, use remote support to inspect the machine

Validity context: Reported and resolved in mid-September 2022

License regeneration required after changing USB dongle or HostID

Problem

CivilFEM starts on one machine but not on another after moving to a new USB network adapter; new license files are required for the new MAC/HostID

Possible cause

The license is bound to the dongle/MAC-derived HostID, so changing the adapter changes the licensing target

Solution

Generate new CivilFEM and Marc license files for the new HostID and stop using the old dongle once the new one is active

Validity context: Late September 2022

Crash after solving in student installation

Problem

CivilFEM crashes after solving, often when moving into results; the issue also occurs for static analysis, not only transient analysis

Possible cause

Support suspected an Intel Fortran-related issue on the system and suggested moving `MarcResults.dll` out of the dependencies folder into the main `win64` folder

Solution

Move the DLL as instructed and verify whether the crash persists

Validity context: Reported in late September 2022

License package format changed from `.lic` + `.dat` to two `.lic` files

Problem

The customer expected a `.dat` file with the license, but the new delivery contained two `.lic` files

Possible cause

A licensing format change in the delivered package, not a runtime failure

Solution

Treat both files as the license set; one file is renamed to distinguish the MSC/MARC component

Validity context: Late September 2022; discussed in a short back-and-forth and immediately clarified

Marc 2022.1 remeshing fails after a model change

Problem

A model meshed successfully earlier in the day, then failed on remesh after a dimension change; the same issue persisted after reinstalling Marc and the license server

Possible cause

Unresolved in the block; support suspected a Marc/Mentat 2022.1 installation issue or a related MSC/license/library problem

Solution

Remote assistance was scheduled; reinstall and license checks had already been tried

Validity context: October 2022; the issue is still open across multiple follow-ups in the block

CivilFEM Academic host-ID collection fails on a Windows 8.1 server

Problem

The customer could not generate the server host-ID with the first utility and saw an error on a 64-bit Windows 8.1 machine

Possible cause

The original host-ID utility likely required permissions or a platform path that was not available in that environment

Solution

Use the alternate utility that does not require administrator permissions; confirm the exact CivilFEM edition if you need to map this to a specific product line

Validity context: October 2022; part of an academic licensing onboarding flow

Marc Mentat Student appears to hit a Qt / DLL loading problem

Problem

The case being discussed is not Adams but Marc Mentat Student, and the support exchange points to a startup failure related to Qt libraries / DLL loading

Possible cause

A DLL conflict or wrong library being loaded; the block references a `tbb.dll`-style workaround from the external vendor, but it is not confirmed here

Solution

Continue with the joint vendor meeting and verify the DLL/workaround path before documenting anything as resolved

Validity context: Late November 2022; unresolved in the reviewed text

License migration to a new server, VM, or cloud host

Problem

The customer needs to move an existing CivilFEM license to another server after hardware failure and asks whether the license can run on Windows Server, virtual machines, or cloud infrastructure

Possible cause

The license is tied to a specific host ID and requires a compatible license server setup on the replacement machine

Solution

Provide a temporary test license, request the host-ID from the new server, and clarify that cloud-based licenses are not offered but VM/cloud self-hosting is allowed with the LM-X license server

Validity context: December 2022, with follow-up and holiday delays extending into January 2023

CivilFEM 2022 powered by Marc / MSC Marc Student Edition fails on one Windows machine

Problem

The student edition and commercial version both fail on the same computer with a library or "wrong image" style error before licensing is even reached; reinstalling, changing the user profile, and copying dependencies do not fix it

Possible cause

The thread points to a system-specific problem or third-party software conflict, with OS corruption also suggested as a possibility, but no root cause is confirmed

Solution

Try a clean reinstall, use the default location, test the alternate installer, or move to another computer; the case was ultimately closed without a confirmed fix

Validity context: December 2022

CivilFEM powered by Marc license renewal and 2023 compatibility

Problem

A user upgraded from 2021 to 2022 because a prior license had expired and requested new license files. The exchange also asked whether a 2023 release was coming soon

Possible cause

Expired CivilFEM 2021 license and the need to generate new local license files for the upgraded installation

Solution

New license files were issued and the user was told they would also be valid for the upcoming 2023 version

Validity context: Valid for January 2023

CivilFEM license migration to a new server or VM

Problem

A commercial CivilFEM license needed to move to a new server because the current license server OS had to be upgraded. A testing license was also used for a virtual environment before the commercial move

Possible cause

Hardware/OS change on the license host required a machine change and license reissue

Solution

The vendor issued a test license, then a machine-change form and a new license file were sent for the new machine

Validity context: Valid for January 2023 and tied to a December 2022-originated migration request

LM-X license server client does not open because Java is missing or incompatible

Problem

The LM-X License Server Client would not open on multiple Windows servers after installation. One attempt with an alternate runtime caused the application to crash, and another machine showed the `.jar` handler behaving incorrectly or missing the client icon

Possible cause

The LM-X client requires Java 8 or above; the installation either lacked the required Java runtime or the runtime used was not compatible in that environment

Solution

Install a compatible Java runtime, then open the LM-X License Server Client and configure the license. If the crash persists, provide screenshots. A later thread raised the constraint that Java is not permitted and explored a workaround or vendor alternative

Validity context: Valid for January 2023

CivilFEM Sismica license renewal after expiry

Problem

Two users reported that the Sismica license expired at year-end and asked for an extension/renewal so they could continue current and upcoming model work

Possible cause

Annual license expiration

Solution

Secretariat sent the requested files and the user later confirmed everything was updated and working

Validity context: Valid for January 2023, with a year-end expiry pattern

CivilFEM 2022 laptop license files expired or were deleted after upgrade/uninstall

Problem

A laptop that had been upgraded to CivilFEM 2022 powered by Marc reported missing or expired license files, and the customer was unsure which files to keep or replace

Possible cause

Old license files were deleted during uninstall, and the initial replacement files were expired or not the final correct set

Solution

Re-add the preserved license files in the Administration Utility, remove old references, and use the corrected license files generated by Secretariat

Validity context: Dated January 11-30, 2023; the thread ends with confirmation that the right files were sent

CivilFEM license migration to a newer server after hardware failure

Problem

A customer requested help moving a CivilFEM commercial license to another server after an OS upgrade or hardware failure scenario, and also requested more time for a test license

Possible cause

License-server migration due to hardware or OS change

Solution

Provide the machine-change flow and the temporary test-license extension already mentioned in the thread

Validity context: Dated December 2022 to January 2023, with the last visible follow-up on January 30, 2023

CivilFEM LM-X server license stops after a few days and requires manual restart

Problem

The server license is initially reachable from client machines, but later stops working after a few days or during weekends and needs a manual restart by logging into the server

Possible cause

Not confirmed in the block. The discussion points to LM-X server configuration issues, possible demo-mode misrouting, firewall/port blocking, or a missing DLL, but none is proven

Solution

Check the LM-X configuration on the server, verify the correct server URL is selected, confirm the license log and feature list, ensure port 6200 is not blocked, verify `liblmxvendor.dll` is present, and reinstall the LM-X server if needed

Validity context: Feb 23 to Mar 14, 2023

CivilFEM license reissue and installation on a new dedicated server

Problem

The team moved CivilFEM to a dedicated server, received a new host-ID file, and then had trouble installing the newly issued license on the new server

Possible cause

A machine change / server migration requiring a fresh license issuance and corresponding installation steps

Solution

Use the newly issued license file, complete the License Change Form if required, and finish installation via the CivilFEM LM-X License Server and Administration Utility

Validity context: Mar 2 to Mar 14, 2023

CivilFEM local license generation failed and was switched to a network license workaround

Problem

A user could not find where to load a new license file, and the local license path kept failing after overwrite/restart attempts

Possible cause

The local license generation flow was failing in the licensing backend, so support used a network-license workaround for the same machine

Solution

Install the license through the network-license server path, then point the Administration Utility at the localhost port entry so the machine can consume the network license

Validity context: April 3-4, 2023

CivilFEM server license stops after weekends or maintenance and needs restart

Problem

The server license repeatedly stopped working after periods of inactivity or over weekends, forcing a restart on Mondays

Possible cause

A shutdown signal or similar event from the OS or another third-party process appears to be stopping the license server; firewall, antivirus, or scheduled maintenance were suspected

Solution

Check Windows security logs and scheduled maintenance at the exact timestamp, review firewall/antivirus interference, and test with the newer LM-X build that support uploaded; escalate to the licensing vendor if it persists

Validity context: March 13-April 20, 2023

CFMarc evaluation license delivery and installation confusion

Problem

A user expected an evaluation package for CivilFEM with Marc but was unsure whether they had received the software link or the license file, then later confirmed installation

Possible cause

The evaluation workflow relied on a separate host-ID step and a commercial evaluation license, and the user initially only had account registration rather than the license payload

Solution

Provide the correct download path, obtain the machine information file, issue the evaluation license, and confirm the license is installed through the normal installer or Administration Utility path

Validity context: April 20-25, 2023

CFMarc local license file stopped being detected after a directory change

Problem

Meshing triggered a security message and the model could not continue; support concluded the local license was no longer being detected

Possible cause

The local MSC Marc-Mentat license file was likely moved, deleted, or changed location, so the Administration Utility no longer saw it

Solution

Generate the Administration Utility report, verify the license entry, and re-add the local license file if it is missing or pointing to the wrong folder

Validity context: May 10, 2023

CivilFEM license migration to a new server blocked by host-ID or MAC mismatch

Problem

A customer migrated to a new server and could not complete license issuance because the host-ID file and form did not match

Possible cause

The license is tied to a specific machine identifier, and the submitted host-ID/MAC values were inconsistent between files

Solution

Confirm the correct machine identifier, align the host-ID file and the change form, then generate the new license after the machine-change form is completed

Validity context: May 3-17, 2023

Cloud-hosted licensing on Google Cloud needs supported HostID handling

Problem

The customer wanted to move CivilFEM licensing and testing to Google Cloud and asked how to supply the right machine information for a cloud server

Possible cause

The licensing model depends on HostID-based binding, and the cloud deployment needed a supported cloud identifier plus a Windows LM-X License Server

Solution

Provide the cloud server HostID information using the stated utility, then validate whether the cloud platform’s identifier is supported for LM-X licensing. The thread also says the issue was escalated to the LM-X vendor team

Validity context: Late May 2023

New license file is rejected because the LM-X server is too old

Problem

The installer reported that the license was too new and that no licenses were available to serve

Possible cause

The new license file was issued for a newer CivilFEM release than the LM-X License Server version installed on the customer side

Solution

Update or reinstall the LM-X License Server to the latest available version, then retry the license installation. The thread says the newer license was intended for CivilFEM 2023 and would still work with CivilFEM 2022 if the server was updated

Validity context: June 2023

Renewal generated the wrong local-license target and triggered machine-binding confusion

Problem

After renewal, the customer received license files that did not match the machines they expected and asked for a single local license for a different computer

Possible cause

The renewal appears to have been generated against the prior machine set, and the request likely needed a machine-change confirmation or corrected MAC/hostname binding

Solution

Reissue the local license for the requested machine after confirming the intended target and checking whether a formal machine-change workflow is required

Validity context: May to June 2023

LM-X License Server client cannot be opened because a required file is missing

Problem

The license server setup step cannot be completed, and the LM-X client/tool referenced in the installation flow does not open on the target machine. In the same thread, CivilFEM startup also becomes slow or fails while trying to use the license

Possible cause

A required file is missing from the LM-X License Server security folder on some machines

Solution

Download the replacement archive from the provided support link, unzip it, copy the missing DLL into the expected folder, start the service, and retry the LM-X client. If it still fails, generate and send the full report file

Validity context: Valid for the July 24 to August 3, 2023 support window; the email says the fix is for the next release

Network license is tied to the wrong server or is blocked during communication

Problem

The user cannot get CivilFEM to resolve the license correctly even though the license files are present. The workflow suggests the license is being applied on a different machine, the server entry may be malformed, or the application hangs while trying to start

Possible cause

The license is bound to a specific server machine, the server name may have been entered incorrectly, or a firewall is blocking traffic between the client and the license server

Solution

Confirm the correct server machine, ensure the server service is running there, verify the server entry uses a single `@`, review firewall rules, and regenerate the report file if the issue continues

Validity context: Valid across July 21 to August 3, 2023; the same support thread cycles through server selection, report generation, and firewall troubleshooting

License server stopped working after CivilFEM 2023 update

Problem

CivilFEM had worked earlier, then stopped taking the license; the user could not use the software after an update and needed urgent support

Possible cause

The license-server side needed an update/reinstall to match CivilFEM 2023; the block also mentions checking firewall/ports, but the later diagnosis points to the server version mismatch

Solution

Reinstall or update the license-server component from the CivilFEM 2023 installer, then verify remote access and license checkout again

Validity context: August 2023; explicitly tied to CivilFEM 2023 and the matching license-server version

License report generation blocked by permissions or firewall

Problem

The user could not generate or access the quick/full report needed to diagnose the license problem, and an access-denied issue was mentioned

Possible cause

Missing administrative permissions and/or a firewall policy blocking the report generation or the license-server communication test

Solution

Run the Administration Utility with admin rights, generate the full report, and verify firewall/port access with IT

Validity context: August 2023; tied to the CivilFEM license diagnostics workflow

CivilFEM powered by Marc cannot mesh an element after installation

Problem

The user reports that the software installs, but when starting a mesh operation on an element, it fails and the software shows an error message

Possible cause

Unknown from the block. The user suspects an installation problem, but the excerpt does not confirm the root cause

Solution

Review the attached mesh-error screenshot and the exact software note; if needed, request the model or the minimal files used to reproduce the failure

Validity context: September 1-4, 2023

CivilFEM installation fails to start because of dongle or license-file configuration

Problem

After installation, the software opens and then closes immediately. The support thread later identifies a licensing configuration issue and then a dongle driver problem

Possible cause

The dongle driver was not working, and the license appeared to depend on the dongle/MAC binding

Solution

Fix the dongle driver or verify that the license is bound to the correct hardware, then retry launching the software

Validity context: September 6, 2023

Network floating license installation on a new host fails or stays offline

Problem

The user cannot get the license server running on a new computer, the LM-X client reports the server as offline, and later asks whether firewall/public settings are needed because the laptop cannot find the host

Possible cause

The host-side license services and client-side pointing were not fully configured, or network/firewall access is blocking the license server

Solution

Install the license files on the designated host, ensure both the MSC and LM-X license servers are configured, point clients to the server/ports in the Administration Utility, and verify admin and firewall access

Validity context: Seen from 2023-10-04 through 2023-10-11

Course or node-locked installation fails with no valid product

Problem

A user reports they cannot proceed past installation and later says the final error is "no valid product."

Possible cause

The local CivilFEM and MSC Marc licenses were not properly selected in the Administration Utility during setup

Solution

Use the Administration Utility to select the correct local `.lic` files for both products, then generate a new report and confirm the entries are green

Validity context: Seen on 2023-10-24

CivilFEM node-locked license is not accepted after installation

Problem

After installation, the user sees a license-validation failure such as no valid product / not valid product, even after generating reports and confirming the license information appears present

Possible cause

The local license setup was incomplete or conflicted with leftover licensing components or settings; the Administration Utility configuration was not in the clean final state expected by the product

Solution

Regenerate the report, verify the license paths in Administration Utility, remove any stale license-server component or other conflicting settings, and retry. If it still fails, continue with online support

Validity context: Late October to early November 2023, with follow-up resolution on October 27 and continued rework through November

Residual license-server settings interfere with local CivilFEM activation

Problem

The license appears to be installed, but the product still reports validation errors after the user removes one setting and before other cleanup steps are completed

Possible cause

A leftover CivilFEM LM-X License Server installation and an unnecessary Access Keyword value were still present and were interfering with local validation

Solution

Remove the unneeded license-server component, clear the Access Keyword setting, and re-test with the current license files only

Validity context: October 25 to October 27, 2023

CivilFEM license must be reissued for a different computer

Problem

The user cannot continue on the original machine and asks to move the license to a second PC; the flow then stalls on Host-ID generation

Possible cause

The license is tied to the specific computer, so a new machine requires a new Host-ID-based license issuance

Solution

Generate the Host-ID file on the new computer, confirm admin privileges, and issue a new license for that machine. If needed, complete the Host-ID capture in an online support session

Validity context: November 2 to November 27, 2023

CivilFEM for Ansys client install cannot find the MSC Marc license on the server

Problem

The client install appears to complete, but the client cannot resolve the MSC Marc license on the server or test the connection cleanly

Possible cause

A server-side license availability or communication issue affecting the MSC Marc component, while the CivilFEM license itself appears to be present

Solution

Check the server license setup, generate a client-side report file from the CivilFEM Administration Utility, and compare client/server availability to isolate the failure point

Validity context: November 10 to November 27, 2023

Marc solver license/security error on the license server

Problem

Running an analysis produced an error on the Marc solver, described as a license security error, and the solver license could not be found on the server

Possible cause

License server visibility or communication issue, or a configuration mismatch that required report-file analysis

Solution

Use the CivilFEM Administration Utility report file to inspect the configuration and confirm server license availability; if needed, reinstall on another machine while pointing to the existing license server

Validity context: November to December 2023

HostID changed after USB Ethernet driver update

Problem

A previously working license stopped working after the network adapter/driver changed, and the reported HostID no longer matched the license binding

Possible cause

A driver revision exposed a different adapter variant and changed the MAC/HostID used for licensing

Solution

Revert to the earlier driver version that preserved the original HostID, and keep a backup of the working driver for future recovery

Validity context: December 2023, with the issue confirmed resolved in follow-up mail

Permanent license binding needed confirmation for virtual machine versus MAC-only association

Problem

A renewed license was being prepared, but the team needed to confirm whether the license should remain bound to a virtual machine BIOS identifier or be simplified to MAC-only binding

Possible cause

Mixed licensing model in the previous file set, with CivilFEM and Marc components bound differently

Solution

Confirm the desired binding model before issuing the permanent license; if available, generate it using the simpler MAC-only association

Validity context: January 2024

License rebind and renewal tied to machine identifiers

Problem

Customers requested new CivilFEM/Marc license files, including permanent and local/network variants, with discussion about binding the license to a MAC address, BIOS/VM host ID, or another server

Possible cause

License generation depends on the correct host binding, and the existing setup included both virtual-machine BIOS identifiers and MAC-based identifiers

Solution

Confirm the intended binding method, regenerate the license against the chosen host identifier, and verify installation on the target machine or server

Validity context: January to April 2024; several messages also reference future CivilFEM 2024 compatibility and maintenance dates

Evaluation license issuance for multiple machines

Problem

Three local evaluation licenses were requested for different machines, then routed for delivery to the end customer

Possible cause

Trial licensing required host-ID-based issuance and partner-mediated distribution

Solution

Generate the requested evaluation licenses, verify the target host IDs, and send them through the designated distributor channel

Validity context: February 2024

CivilFEM website access blocked by reset/login/captcha issues

Problem

Users could not complete password resets, could not log in, were redirected to the wrong account, or hit captcha-related failures; support sometimes had to manually reset credentials or create a user

Possible cause

The block points to a mix of website security filtering, captcha problems, and possible firewall or hosting-provider interference, but the exact product surface is not fully specified

Solution

Manually reset the account or create a temporary access path, then confirm whether the blockage is in the customer firewall or the hosting layer. To identify the product more precisely, the exact portal/page or account context would be needed

Validity context: Late February to mid-April 2024

Manual installer and service pack delivery after portal/download failure

Problem

Support had to send direct download links for the latest installer and a service pack because users could not rely on the portal or auto-update path

Possible cause

The customer likely lacked portal access or the normal update workflow was unavailable

Solution

Provide the manual download package, confirm installation success, and capture whether the portal/download problem persists

Validity context: February and April 2024

Free-course/webinar registration blocked by captcha or access restrictions

Problem

A user could not register for the free course or access webinar models because of captcha problems, then support created an account manually to bypass the issue

Possible cause

The registration flow appears to be blocked by captcha or another access-control layer, but the exact product surface is not fully identified in the block

Solution

Create a manual account or local access path, then confirm enrollment. To identify the product more precisely, the exact course or portal context would be needed

Validity context: March to April 2024

Evaluation license was too limited for the intended CivilFEM use

Problem

An evaluation user could not define soil and rock material behavior with Mohr-Coulomb or Hoek-Brown criteria, and the user compared it against a student version that did allow those material models

Possible cause

The thread says the wrong license tier was sent at first, described as an "Intro" license instead of the intended "Expert" license; the body text itself does not identify the module, so the exact product would need the original request or license header to confirm

Solution

Issue the correct Expert license and make sure the CivilFEM license on the client side is updated with the replacement file

Validity context: June 18, 2024 to June 27, 2024

Marc license installation failed because the license file/header or server version was wrong

Problem

The license installation/update kept failing, and later messages say the software was rejecting the license because the server version was old

Possible cause

The thread points to two closely related causes: an outdated LM-X license server and an updated Marc license whose header was not adjusted correctly during an LMTools-based update

Solution

Reinstall the Marc license server so the header is regenerated correctly, or copy the correct header from the prior license file; update to the latest LM-X license server installer if the server version is outdated

Validity context: July 4, 2024 to July 11, 2024

CivilFEM license installation/update failed until the license-server setup was corrected

Problem

The customer could not get the software to accept the license during installation/update and repeatedly requested remote help; the issue persisted across several follow-ups

Possible cause

The earliest messages do not identify the product/version precisely; later replies point toward a license-server update problem, including a missing/incorrect header and a nonstandard port on the customer side. The full screenshot or report file would be needed to pin down the exact failing product state

Solution

Reinstall the license server, correct the license file handling, and verify the installed port and license-server configuration in a remote session if needed

Validity context: July 4-15, 2024

Student/evaluation CivilFEM by Marc was misconfigured to use the wrong licensing target

Problem

The software initially appeared to work, then started showing a licensing issue. The report later showed the Administration Utility pointing to an internal server name instead of the local student license

Possible cause

The licensing configuration was set incorrectly for a student installation. The support reply says the student version should use its bundled local student license by default, not a commercial server target

Solution

Clear the licensing settings in the Administration Utility, attach the local student license, and reinstall if the issue persists

Validity context: July 22-24, 2024

Evaluation license worked only when the laptop network adapter was active

Problem

The software installed successfully and could run, but the license was not read when the laptop was connected only through Wi-Fi

Possible cause

The reply states the license is tied to a MAC address and the corresponding adapter must remain active. This points to adapter selection/state rather than a software defect

Solution

Keep the chosen adapter active or issue the license against a more suitable MAC address for the machine

Validity context: July 29-August 6, 2024

CFMarc solver fails with license error at solve time

Problem

The model runs up to the solve step, then returns an error code, and support requests a report from the CivilFEM Administration Utility to inspect the installation status

Possible cause

Initial vendor diagnosis points to a licensing issue, but the exact cause is not established in the excerpt

Solution

Review the Administration Utility report and screenshots, verify installation status, and continue support diagnosis for the solver/license path

Validity context: September 12, 2024

New-machine license migration was confusing

Problem

The customer was unsure what to install on a new computer, whether anything needed to be signed, and which download/package to use

Possible cause

The machine-change workflow and installer bundle were not obvious to the user

Solution

Confirm the machine-change form, return the signed acceptance if required, and point the user to the single installer that includes both Marc and CivilFEM

Validity context: 2024-09-17 to 2024-10-09; appears resolved after the EULA was returned and the license reissue was offered

Marc license was not found until the license-server configuration and firewall/port settings were corrected

Problem

CivilFEM took a long time to open, and Marc reported that it could not locate the license entry even though the server was visible

Possible cause

The Marc license server configuration was not resolving correctly until the daemon/path settings and network access were adjusted

Solution

Reinstall or manually correct the Marc license file, then ensure the required firewall ports are open and the Marc daemon uses a fixed port

Validity context: 2024-11-12 to 2024-11-13; resolved when the customer forced the Marc port and added the missing firewall rule

CivilFEM 2024 beta update removed the expected language option

Problem

After an automatic update from the beta/release line, the Chinese language no longer appeared in the language dropdown

Possible cause

The update path changed the language files available in the install; the final release at that point only shipped English and Spanish

Solution

Copy the provided translation file into the `lang` folder, or wait for the first service pack that includes it

Validity context: 2024-09-24; the issue was explained as an update/beta artifact, with a manual workaround provided

Network license renewal requires a new server host ID

Problem

Users requested updated license files after moving to a different server and asked for the latest software version to validate on the new platform

Possible cause

The license is bound to the server host identity, so changing the server requires reissuing the license files

Solution

Reissue the license files for the new host and attach the machine-change paperwork required for the transfer

Validity context: January 2025 through March 2025, with a later follow-up in March confirming the new server license

Academic network license deployment and seat-count clarification

Problem

A distributor asked for licenses before class start, requested installation guidance, and later asked whether the server license would allow all student machines to run at the same time

Possible cause

The deployment is a multi-seat academic network install, and the workflow depends on receiving host IDs and correctly pointing clients to the license server

Solution

Generate the academic licenses once host IDs are received, use the installation guide, and confirm the available seat count on the server before rollout

Validity context: March 2025

CivilFEM startup delay while searching for Marc license

Problem

CivilFEM opens very slowly, taking several minutes before the license is acquired

Possible cause

Support suspected the client was still searching for the Marc license because the license configuration was not correct on the server

Solution

Install the definitive server license, remove the old one, and verify the server/client license configuration through remote assistance

Validity context: May 7-12, 2025

Expired laptop license renewal

Problem

A laptop CivilFEM license was reported as expired and needed renewal

Possible cause

The renewal cycle and internal license-tracking process were pending, so the updated license had not yet been issued

Solution

Generate and send the renewed license, then confirm that it loads on the laptop

Validity context: April to May 2025; the user confirmed the renewed license worked

Academic license request and activation failure

Problem

An academic license was requested for opening student models, but the registration path denied access; the generated license file initially could not be loaded

Possible cause

The license needed to be generated from host ID and then loaded through the Administration Utility; there may also be an environment-specific issue since the utility was checked against Windows 11

Solution

Collect the host ID, generate the nodelocked/university license, load it with the Administration Utility, and verify on the target Windows machine

Validity context: May 29-30, 2025

License server appears tied to a problematic machine

Problem

The program sometimes blocked on open with errors, then later worked again; the user suggested the issue might be with the machine hosting the license and asked about moving the license to another team machine

Possible cause

The license-hosting machine or its network path appears unstable or misconfigured

Solution

Use remote assistance to inspect both the client and the license-server machine; if needed, generate a temporary node-locked license or move the server license to another computer

Validity context: June 3-4, 2025

License warning after CivilFEM upgrade

Problem

After upgrading to the latest CivilFEM version, the application showed a license-related warning on launch

Possible cause

The latest CivilFEM and Marc licenses needed activation, and the Marc server file may have required hostname/path adjustments

Solution

Activate the latest licenses that were resent by support and, if needed, update the hostname and path in the Marc license file

Validity context: July 2, 2025

License and machine-change administration thread with mixed CivilFEM/Marc signals

Problem

The thread shows a new machine being brought up, licenses being located or resent, remote support links being exchanged, and a signed machine-change form being requested

Possible cause

Administrative delay and remote-support coordination, not a clearly isolated product fault. To identify the product, the missing detail would be the exact license/module referenced by the attachment and the machine-change form

Solution

The licenses were eventually made available, and the paperwork was deferred; the block does not show a deeper technical failure

Validity context: September 2025

CivilFEM license configuration fails with registry or admin-rights errors

Problem

The LM-X End User Configuration Tool reports an access/registry error when entering the license server name, and later the related license setup also shows license errors

Possible cause

Insufficient administrator privileges or a configuration step that needs elevation; the block explicitly points to admin rights and to the CivilFEM Administration Utility as the workaround

Solution

Run the tool as administrator or use the Administration Utility, then reboot and retry if needed

Validity context: Supported by the 2026-03-03 registry-error thread and its follow-up

CivilFEM 2025 deployment needs silent-install or packaging support for multiple PCs

Problem

An organization asks for an MSI/package or a command line for silent installation because the software must be deployed on multiple machines

Possible cause

Standard deployment constraint, not a defect; the block shows a response with the InstallShield response-file flow and silent-install parameters

Solution

Use the documented extract-and-silent-install process with a response file and log output for validation

Validity context: Supported by the 2026-02-23 installation thread

Academic/university license selection or path is broken

Problem

A user reports that a university license file is loaded in the administration utility, but the expected academic option does not appear or the license file path seems wrong

Possible cause

The thread points to an error in the university license file path or configuration, but the exact failure mode is not fully proven in the block

Solution

Check the university license file path and request a report from the Administration Utility to validate the license setup

Validity context: Supported by the 2026-02-24 thread

CivilFEM license transfer and server IP change questions

Problem

A customer asks whether changing the server IP or moving from a local/node-locked license to a network/floating license will affect CivilFEM licensing

Possible cause

This is a licensing-administration concern rather than a defect; the block says the license is based on HostID/MAC information, not IP

Solution

Changing IP alone should not affect the license; if moving to another machine or changing license type, involve the administration side

Validity context: Supported by 2025-11-26 and 2026-02-26

LM-X configuration tool throws a registry access error

Problem

Entering the license server name in the LM-X End User Configuration Tool triggers an "Unable to access registry" error

Possible cause

The tool lacks sufficient Windows privileges or cannot write to the registry from the current user context

Solution

Run the LM-X tool with administrator rights or use the CivilFEM Administration Utility, which can request elevation automatically; reboot if the problem persists

Validity context: Observed on 2026-03-03 and resolved in-thread the same day

CivilFEM 2025 client cannot find the license after server/client reinstall

Problem

After reinstalling the server and client software, the client cannot find the license

Possible cause

The license server was still using an older license file instead of the CivilFEM 2025 license set

Solution

Install the latest license files for CivilFEM 2025 from the license portal and verify the server is using the correct version

Validity context: Observed on 2026-03-04; the block indicates a likely fix by 2026-03-04

Floating licenses are not reachable from other devices

Problem

CivilFEM works on the server machine, but a laptop cannot find the license; Marc cannot be run independently; later reports also mention meshing not progressing

Possible cause

Communication to the license server is being blocked, most likely by firewall or endpoint security software restrictions

Solution

Generate report files from the server and client machines, review firewall/security exceptions, and test whether disabling CrowdStrike changes the behavior; arrange remote support if needed

Validity context: Observed from 2026-06-10 to 2026-06-11 and still under investigation in the block

License server runs but does not issue licenses until configuration is corrected

Problem

The server appears to be running, but clients still see no available licenses or a grayed-out server status; later the issue is traced to server configuration details

Possible cause

The license server configuration is incomplete or split across old and new directories, including a missing port-setting line in the config file

Solution

Add the required port setting, restart the service, point CivilFEM to the correct license address, and if needed use the newer server configuration utility to generate a report or auto-configure the machine

Validity context: Observed across 2026-03-24 to 2026-04-13; resolved in-thread by 2026-04-13

Floating licenses cannot be reached from other devices because security policy blocks license-server communication

Problem

Users cannot access floating licenses from another device; connectivity tests from the laptop to the license server do not receive responses

Possible cause

Communication is being blocked before it reaches the licensing services, likely by CrowdStrike or a firewall policy on the client or network path

Solution

Verify IT-approved whitelist and firewall exceptions, then re-test communication to the license server from the affected machine

Validity context: Supported by emails from June 11-17, 2026; likely case-specific to that environment

Whitelist change may need to cover both MSC licensing services and CivilFEM LM-X License Server

Problem

An initial whitelist effort appears to focus on one license server, but the issue may persist unless all relevant licensing endpoints are allowed

Possible cause

The security exception may be incomplete if it only covers the MSC/Beryllium side and does not include the CivilFEM LM-X License Server

Solution

Confirm that the whitelist or firewall exception includes both the MSC licensing services and the CivilFEM LM-X License Server, then validate connectivity to both

Validity context: Supported by the June 12-16, 2026 messages; context is limited to this support thread