99998 Best: Autodesk Moldflow Error
While running a high-stakes simulation in Autodesk Moldflow, encountering the cryptic "Error 99998" can be a major roadblock. This error is a generic "unexpected termination" signal, meaning the solver crashed before completing the analysis. Because it acts as a catch-all for various internal failures, finding the "best" fix requires a systematic approach to troubleshooting.
Here is the definitive guide to resolving Autodesk Moldflow Error 99998 and getting your studies back on track. Check Local System Resources
The most common cause for an unexpected solver crash is a lack of hardware resources. If the solver cannot access the memory or disk space it needs, it will shut down abruptly.
Free Up Disk Space: Moldflow generates massive temporary files during calculation. Ensure your "Temporary Directory" (defined in Simulation Job Manager or Synergy preferences) has at least 50GB to 100GB of free space.
Monitor RAM Usage: For complex parts with high element counts, you may be exceeding your physical RAM. Close unnecessary background applications or increase your system's virtual memory (page file).
Clear Temporary Files: Navigate to your temporary folder and delete old .trm, .msh, and .res files from previous failed runs to prevent file path conflicts. Audit Your Mesh Quality
A "bad" mesh is the leading technical cause of Error 99998. If the solver encounters an element with zero volume or extreme distortion, the mathematical matrix becomes unsolvable. autodesk moldflow error 99998 best
Scan for Overlaps: Use the Mesh Repair Wizard to find and fix overlapping elements or intersections.
Fix Aspect Ratios: High aspect ratio elements (above 50:1 for Dual Domain or 100:1 for 3D) can cause the solver to "diverge" and crash. Aim for an average aspect ratio below 3:1.
Check for Connectivity: Ensure there are no disconnected nodes or "islands" in your mesh. A "Connectivity Diagnostic" should show a single continuous body. Reset the Simulation Job Manager (SJM)
Often, Error 99998 isn't a problem with your model, but a glitch in the communication between Synergy (the UI) and the Solver.
Restart Services: Open the Windows Task Manager, find the "Simulation Job Manager" service, and restart it.
Check Firewall Settings: Ensure that flow.exe, cool.exe, and warp.exe have full permissions to communicate through your firewall. Even local simulations use "internal" network ports that can be blocked by overly aggressive security software. While running a high-stakes simulation in Autodesk Moldflow,
Update the SJM: Autodesk frequently releases patches for the Job Manager. Ensure you are running the latest version available via the Autodesk Desktop App or Account Portal. Simplify Analysis Settings
If the error persists, the solver may be struggling with a specific physical calculation. Try simplifying your parameters to isolate the cause:
Toggle Inertia/Gravity: If you have "Inertia effects" or "Gravity" turned on in the Solver Statistics, try turning them off.
Material Data: Check if your material UDB file is corrupted. Try running the simulation with a "generic" material from the Moldflow library; if it works, the issue lies in your custom material data.
Time Steps: If you are using manual time steps for a transient cool or warp analysis, try switching back to "Automatic" to see if the solver can find a stable path. The "Clean Slate" Method
If none of the above works, the study file itself might be corrupted. Export your mesh as a .udm or .pat file. Create a brand-new Moldflow project. Import the mesh into a fresh study. Re-apply your injection points and process settings. Launch the analysis. Corrupted Study File: The
By stripping away the metadata associated with the old project, you often bypass the specific internal conflict triggering the 99998 error.
If you can share a few more details, I can provide a more tailored solution:
The exact point it crashes (e.g., 5% into Filling, during Cooling)? The Analysis Technology you're using (Dual Domain vs. 3D)?
Any specific warnings in the Analysis Log right before the error?
Resolving Autodesk Moldflow Error 99998: A Comprehensive Guide
Encountering error 99998 while working with Autodesk Moldflow can be frustrating, especially when it disrupts your workflow and delays project completion. This error is often associated with issues that prevent Moldflow from functioning correctly, ranging from software installation problems to data corruption or compatibility issues. Here’s a step-by-step guide to help you troubleshoot and resolve error 99998 efficiently.
3. Material and Data Corruption
- Corrupted Study File: The
.mpior study file may have database corruption. - Material Data Mismatch: Using a material record with incomplete rheological data (e.g., missing viscosity curves) in a calculation mode that requires them.
3. Study-Specific Fixes
🔁 Rebuild the Study
- Export your model as Study Archive (.mfs).
- Create a new project and import the archive.
- Re-run analysis.
The Best Step-by-Step Fix for Error 99998
Do not waste time on random tweaks. Follow this structured, best-practice workflow:
⚙️ Solver Settings
- Switch to a different solver (if available):
- For 3D analysis: try “Iterative” instead of “Direct” solver.
- Reduce analysis sequence (e.g., run Fill only before Fill+Pack).
🖥️ Windows & Hardware
- Update graphics drivers (OpenGL issues can cause solver launch failures).
- Disable antivirus real-time scanning for Moldflow’s working folders.
- Set Windows virtual memory to “System managed” or increase to >16 GB.
Step 4 – Mesh repair (most common fix)
- Run Mesh > Mesh Statistics:
- For Dual Domain: Target connectivity index > 90%.
- For 3D: Check for zero-volume elements (use Mesh > Quality > 3D Mesh Diagnostics).
- Remedy:
- Use Mesh > Smooth (iterative, 3–5 passes).
- Mesh > Thickness > Auto-detect (for Dual Domain).
- If 3D: Reduce Maximum edge length by 10–20% and remesh.