Moldflow’s solver engine, inherited from legacy code (Moldflow Plastics Insight 6.1 and earlier), struggles with modern file paths containing spaces, parentheses, or non-English characters.
If you generate a Dual-Domain mesh (midplane equivalent for thin parts) and then convert it to a 3D tet mesh, the conversion algorithm can sometimes leave "zero-volume" elements or elements with negative Jacobians. Most mesh statistics look fine, but the solver chokes on the first iteration of the filling phase. Result: Error 99998.
Ensure that your Autodesk Moldflow software is up to date. Autodesk periodically releases updates and patches that fix known issues.
Remember: Moldflow’s solver stops at Error 99998 to prevent you from trusting a nonsense result. Respect the error, fix the physics, and your simulation (and your part) will converge to success.
Autodesk Moldflow Error 99998 is a generic "unspecified error" that occurs during the analysis stage, typically indicating that the solver has crashed or been terminated by the operating system. Because it is a general catch-all code, troubleshooting requires a systematic look at hardware, software environment, and model integrity. Understanding the Root Causes
Memory Exhaustion: The solver runs out of RAM or Page File space.
Software Conflicts: Antivirus or firewall software blocking the solver executable.
Model Complexity: Excessively high element counts or extreme mesh distortions.
Permission Issues: Lack of write access to the temporary working directory.
Connectivity: Loss of connection to the Job Manager or Simulation Compute Manager (SCM). Phase 1: Hardware and System Check
Before digging into the model, ensure your machine can handle the simulation.
Check RAM Usage: Open Task Manager during the "Initializing" phase. If RAM hits 90%+, the solver may trigger Error 99998.
Increase Virtual Memory: Set your Windows Page File to at least 2x your physical RAM.
Clear Temp Files: Delete files in %TEMP% to ensure there are no naming conflicts with old studies.
Update Drivers: Ensure your GPU drivers are current, as Moldflow uses the GPU for certain calculations. Phase 2: Software and Connectivity
If the hardware is sufficient, the issue is often a communication break between the interface and the solver.
Restart the SCM: Open "Services" in Windows, find Autodesk Simulation Compute Manager, and click Restart.
Whitelist Executables: Add flow.exe, cool.exe, and warp.exe to your Antivirus/Firewall exceptions.
Check Disk Space: Ensure the drive containing the temporary folder has at least 50GB of free space for large result files. Phase 3: Model and Mesh Integrity
A "bad" mesh is the most common reason for a solver to give up mid-calculation.
Scan for Overlapping Elements: Use the Mesh Repair Wizard to find and fix overlaps or intersections. autodesk moldflow error 99998
Fix High Aspect Ratios: Elements with an aspect ratio over 50:1 can cause mathematical instability.
Simplify Geometry: Remove small fillets, logos, or tiny chamfers that create dense, unnecessary clusters of elements.
Check Connectivity: Ensure the injection location is properly connected to the mesh. Phase 4: Project Management
Sometimes the project file itself becomes corrupted or points to a path the solver cannot reach.
Shorten File Paths: Save your project in a simple directory like C:\Simulations\. Long paths (over 256 characters) often trigger 99998.
Avoid Network Drives: Always solve on a local SSD. Solving over a VPN or a shared network drive frequently leads to timeout errors.
Create a "Clean" Study: Export your model as a .udm or .step file and import it into a brand-new project. Summary Checklist for Quick Recovery Restart the Simulation Compute Manager (SCM).
Verify the mesh for intersections or "zero-volume" elements.
Move the project to a local C: drive with a short folder name. Disable antivirus temporarily to rule out a software block.
If the error persists after these steps, it is likely a specific solver bug related to a unique combination of material data and process settings. To help you get back to your simulation, could you tell me: Which version of Moldflow (2021, 2023, 2024) are you using?
Does the error happen immediately or at a specific percentage (e.g., 5% in)? What is the mesh type (Midplane, Dual Domain, or 3D)?
I can provide a more targeted fix once I know the analysis sequence you are running.
Troubleshooting Report: Autodesk Moldflow Error 99998 Error 99998 is a critical licensing error in Autodesk Moldflow that occurs when the solver cannot obtain a valid license to run an analysis. It typically indicates that the required license is either missing, currently in use by other users, or incorrectly configured. Core Causes
License Exhaustion: All available seats for a specific license level (e.g., AMI_STANDARD, AMI_PREMIUM, or AMI_ULTIMATE) are currently checked out by other users.
Configuration Mismatch: The License Configuration tool is set to the wrong license type or is pointing to an incorrect license server.
Expired or Missing License: The license file on the server has expired or does not contain the specific feature code for the solver being used.
SCM Issues: Problems communicating with the Simulation Compute Manager (SCM), often seen in versions 2021 and newer.
Parallel Job Limits: Exceeding the configured limit for parallel solves allowed by your license type. Step-by-Step Solutions 1. Verify License Configuration (Windows)
The most common fix for versions 2023 and 2024 is re-running the configuration utility: Close all instances of Moldflow Synergy.
Open the Windows Start Menu and find the Autodesk Moldflow Insight 202x folder. Title: The 2 AM Visit from Error 99998
Launch License Configuration 202x (alternatively located at C:\Program Files\Autodesk\Moldflow Synergy 202x\bin\mlc.exe). Ensure Network License is selected.
Set the Insight level to match your actual entitlement (Standard, Premium, or Ultimate). Enter the correct License server hostname and click Apply. 2. Check Server Status with LMTools
If configuration is correct, the issue may be on the server side: Open LMTools on the license server machine.
Go to the Server Status tab and click Perform Status Inquiry.
Check if the solver codes (MFIB, MFIP, or MFIA) are listed and if there are any "Total: 0" or "Expired" messages.
Verify if all licenses are currently checked out by other users. 3. Address Linux-Specific Environments
For solvers running on Linux, the environment variables must point correctly to the Autodesk Licensing Service:
Workstation Install: Edit /etc/opt/Autodesk/ami-20XX and ensure ADSK_SERVICE_ADDRESS is set to the correct host:port.
Thin Client Install: Edit the mfclient.env file in the installation folder to update the ADSK_SERVICE_ADDRESS.
Ensure the Autodesk Desktop Licensing Service is running using systemctl status adsklicensing. 4. Reinstall License Components If the license request isn't reaching the server at all:
Uninstall the Autodesk Moldflow Insight License Configuration from the Control Panel.
Reinstall it by running the original Moldflow Insight installer; it will detect the missing component and reinstall only the licensing portion. Summary Table: Error Variants Reported Error Likely Context AMI_STANDARD Standard solver license missing or busy. AMA_PREMIUM / ULTIMATE Moldflow Adviser license level mismatch. Warning 99997
Often precedes 99998; specifically refers to missing Fiber license.
Are you running Moldflow on a local workstation or a remote Linux cluster? Identifying this will help narrow down the exact configuration file to check.
Required license for fiber is not available..." or " Error 99998
Here’s a short, relatable story about encountering the Autodesk Moldflow Error 99998 — perfect for a forum post, internal report, or just sharing with colleagues.
Title: The 2 AM Visit from Error 99998
Scene: A quiet product development lab. Friday, 4:55 PM.
Protagonist: Sarah, a senior molding engineer with a deadline on Monday.
Sarah had spent two weeks building her simulation model. It was a complex, thin-walled medical device housing with tight tolerances for flatness. She had meticulously repaired the mesh, assigned the correct fiber-filled material (DuPont Zytel®), and set the injection location to a tricky center diaphragm gate. Sarah whispered, “You have got to be kidding me
She clicked Launch Analysis.
The solver spun. The clock ticked past 5:30. Her colleagues left. The office lights dimmed automatically. Sarah didn’t notice. She was watching the Fill + Pack progress bar.
97%… 98%… 99%…
Victory lap in her head.
Then — a hard stop.
The screen flickered. The command line interface, usually so clinical and quiet, threw up a wall of red text. At the very bottom, framed by asterisks, was the message:
*** FATAL ERROR ***
AUTODESK MOLDFLOW ERROR 99998
Analysis terminated.
Sarah whispered, “You have got to be kidding me.”
She clicked Help. Nothing. She Googled it. Three results — two in Korean, one dead link. Error 99998 was the ghost of the moldflow world. No documentation. No clear cause. Just a black hole where her weekend used to be.
She restarted the solver. Same error. She reduced the solver memory allocation. Same error. She turned off parallel processing. Same error.
Frustrated, she opened the .out file manually. Buried between lines of thermal conductivity data, she found a tiny clue:
“Node 1847292 — residual flow front temperature exceeds 50°C delta from melt temp. Numerical instability suspected.”
That was it. The solver couldn’t handle a sudden thermal spike at a single node near the end of fill. Instead of a graceful warning, Moldflow just threw up the generic 99998 — a “catch-all” for when the math inside the solver loses its mind and doesn’t know what else to call it.
Sarah fixed it by:
She reran the job at 10:30 PM.
At 11:45 PM, the simulation finished. Success.
She packed her bag, looked at the error log one more time, and muttered, “Error 99998. You’re not an error. You’re a personality.”
Moral of the story: When you see Error 99998, don’t trust the solver’s silence. Go hunting in the output files. It’s almost always a localized mesh or thermal instability near the end of fill — or occasionally a disk full, memory limit, or a corrupted material file. But mostly? It’s the solver saying “something went wrong” without telling you what.
And if you ever meet Sarah at a conference, don’t ask her about 99998. She’s still not over it.
Running Moldflow studies from a mapped network drive (e.g., Z:\Projects\) is risky. A brief network drop or latency spike during the initial solver handshake will cause the solver to abort with Error 99998.
Moldflow is RAM-hungry. A 3D mesh of 2 million tetrahedral elements can easily require 16-32 GB of RAM. If your physical RAM is full, Windows uses a page file on the SSD/HDD. If the page file is too small or the drive is full, Windows denies memory allocation requests. The Moldflow solver, unable to allocate memory, crashes with Error 99998.