Autodesk Moldflow Error — 99998 Exclusive __exclusive__

Troubleshooting Autodesk Moldflow Error 99998: Solving the Exclusive Lock Issue

If you are a simulation engineer using Autodesk Moldflow, encountering an error code is part of the territory. However, few are as frustrating as Error 99998, specifically when it mentions an "exclusive" access violation or licensing lock.

This error typically halts your analysis before it even begins, often appearing in the analysis log as: ** ERROR 99998 ** Analysis failed due to an exclusive lock or licensing conflict.

In this guide, we will break down why this happens and how to get your simulations back on track. What Causes Error 99998?

At its core, Error 99998 is a communication failure. Moldflow is a modular software; the User Interface (Synergy) must communicate with the Solver (Insight) and the License Manager. When this chain is broken, the software throws a generic 99998 code.

The "exclusive" variant of this error usually points to one of three things:

Solver Termination Issues: A previous analysis crashed, but the solver process is still "holding" the project files.

Network/Permission Conflicts: The temporary working directory is set to a location where the software doesn't have exclusive read/write rights.

License Seat Competition: The Simulation Job Manager (SJM) is trying to pull a license that is already "exclusively" checked out by another process or user. Step-by-Step Solutions 1. Clear "Ghost" Processes

The most common cause is a hung process. Even if Moldflow looks closed, the solver might still be running in the background. Open Task Manager (Ctrl+Shift+Esc).

Look for processes named flow.exe, cool.exe, warp.exe, or adsk_cad_import.exe. End Task on all of them. Restart the Autodesk Simulation Job Manager service. 2. Clean the Temporary Directory

Moldflow generates massive amounts of data during a solve. If the temporary folder is cluttered or restricted, Error 99998 occurs. Go to Simulation Job Manager settings. Identify the Temporary Directory path. Navigate there in Windows Explorer and delete old files.

Pro Tip: Ensure this directory is on a local drive (like C: or D:). Running simulations across a network drive often triggers "exclusive lock" errors due to latency. 3. Reset the Simulation Job Manager (SJM)

The SJM is the "traffic cop" for your analyses. If it becomes corrupted, it fails to hand off licenses correctly. Close Moldflow. Go to C:\Program Data\Autodesk\SJM. Rename the Jobs folder to Jobs_Old.

Restart your computer and try the solve again. This forces the SJM to create a clean database. 4. Check for Firewall or Antivirus Blocks

Sometimes, security software sees the "exclusive" handshake between Synergy and the Solver as a threat.

Ensure that amls.exe (Autodesk Moldflow Licensing Service) and the solver executables are added to your Antivirus Whitelist.

Verify that ports 2080 and 27000-27009 (default FlexLM ports) are open. Prevention Tips autodesk moldflow error 99998 exclusive

Avoid Project Overlap: Don't try to run an analysis on a project file that is currently open in another instance of Moldflow.

Local Solving: Always keep your .sdy files on your local hard drive during the analysis. Move them to the server only after the solve is complete.

Update SJM: Ensure you are running the latest version of the Simulation Job Manager, as Autodesk frequently releases patches for these communication errors.

While Autodesk Moldflow Error 99998 sounds like a fatal crash, it is almost always a file management or process conflict issue. By clearing your background tasks and ensuring your temporary directories are local and clean, you can resolve the "exclusive lock" and get back to optimizing your parts.

Are you running your simulations on a local machine or using a remote server/cluster setup?

In Autodesk Moldflow, Error 99998 typically indicates that the software is unable to obtain a license for the solver (Insight), either because the license is unavailable, all seats are in use, or the connection to the license server has failed. Common Causes

License Availability: All available licenses are currently checked out by other users or "zombie" processes (e.g., flow.exe, cool.exe) that didn't close properly.

Server Connection: The client machine cannot communicate with the license server due to firewall blocks, incorrect server names, or IP address resolution issues.

Configuration Errors: The "License Configuration" tool has not been run or points to the wrong server, or the wrong product key was used during installation.

Version Mismatch: Using a product key for a different version (e.g., trying to run 2024 with a 2023 key).

System Clock: A significant time/date difference between the client machine and the license server. Recommended Solutions 1. Check License Status

Use the License Manager Tool (LMTools) on the server to verify license availability:

Navigate to the Server Status tab and click Perform Status Inquiry.

Look for the Insight solver features (e.g., MFIB, MFIP, or MFIA) to see if any are available.

If all licenses are shown as "in use," you must wait for a seat to be released or end "rogue" processes like flow.exe in the Task Manager. 2. Run the License Configuration Utility

For Windows users, ensure the solver is pointed to the correct server: Close all instances of Moldflow Synergy.

Go to the Start Menu > Autodesk Moldflow Insight 202X > License Configuration 202X. Fix 3: Disable Antivirus Real-Time Scanning for Moldflow

Select the correct Network License type and enter the hostname of your license server. Click Apply and OK before restarting the analysis. 3. Increase Retrieval Timeout

If your network is slow, the request might time out before the server can grant it. You can increase this by adding an environment variable: Variable Name: FLEXLM_TIMEOUT

Variable Value: 10000000 (10 million, which equals 10 seconds). 4. Verify Firewall Settings

Ensure the necessary ports are open for both inbound and outbound communication on both the client and server. The default ports for Autodesk licensing are usually 27000-27009 and 2080. 5. Registry Cleanup (Advanced)

If the software is pointing to an old or incorrect server, you may need to clear the registry:

Check HKEY_CURRENT_USER\Software\FLEXlm License Manager\ADSKFLEX_LICENSE_FILE.

Ensure only the current, correct license server address is listed.

For more detailed technical steps or specific product keys, you can refer to the Autodesk Support article on Error 99998.

Are you using a standalone or network license, and which version of Moldflow are you currently running?

Error 99998 in Autodesk Moldflow is a critical licensing issue that occurs when the software cannot verify the required license for your simulation

. It essentially means the solver has started but cannot "checkout" a license to run the actual math behind the study. Common Causes & Solutions License Not Available:

All available licenses are currently being used by other team members. LMTools Utility on your license server. Go to the Server Status tab and click Perform Status Inquiry to see how many licenses are in use. Incorrect License Configuration: This is common in versions 2023 or newer

, where the license level (Standard, Premium, Ultimate) hasn't been set correctly. Moldflow License Configuration

tool (found in the Windows Start Menu under Autodesk Moldflow Insight/Adviser 202x) and ensure the License Level License Type Server Name are all correct. "Rogue" Processes:

Sometimes a previous simulation crashes but stays in your computer's memory, holding onto a license. Task Manager and look for processes like . Select them and click Service Communication (SCM): Simulation Compute Manager (SCM) might be having trouble talking to the license server. Ensure the Autodesk Simulation Compute Manager service is running in your Windows Services (services.msc). Specific Scenarios

In Autodesk Moldflow, Error 99998 typically indicates a license failure where the required "feature" (the specific product level or solver) cannot be found or accessed by the software.

Common features that trigger this error if they are missing or misconfigured in your license file include: AMI_STANDARD (Moldflow Insight Standard) AMI_PREMIUM (Moldflow Insight Premium) AMI_ULTIMATE (Moldflow Insight Ultimate) AMA_ULTIMATE (Moldflow Adviser Ultimate) Common Causes & Solutions Expired or Missing License on your license server, go to the Server Status tab, and click Perform Status Inquiry . Look for features like to ensure they are active and not expired. Mismatched License Levels The entire Moldflow installation folder (e

: If you installed the Ultimate update but only have a Premium license, the software will fail. Ensure your License Configuration

(found in the Windows Start menu under Autodesk Moldflow) is set to the correct license level. All Licenses in Use : Check if "rogue" solver tasks ( ) are running in your Task Manager . Ending these processes can release stuck licenses. Incorrect Product Key

: For older versions (2019 and below), ensuring the correct product key was used during installation is critical, as Synergy (the UI) and Insight (the solver) require different keys.

For more detailed troubleshooting, you can check the official Autodesk Support Page for Error 99998 Are you seeing a specific feature name

(like AMI_ULTIMATE) in your error log, or would you like help checking your license server status

Fix 3: Disable Antivirus Real-Time Scanning for Moldflow Folders

Configure your antivirus to exclude:

• The entire Moldflow installation folder (e.g., C:\Program Files\Autodesk\Moldflow 2025)
• Your Moldflow project directory (e.g., D:\MF_Projects)
• The temp folder (%TEMP%\Moldflow)

After adding exclusions, reboot and test.

Fix 2: Reset Project Database Permissions

Error 99998 exclusive often hides a permissions problem. Use this PowerShell script (run as Administrator):

$projectPath = "D:\Moldflow_Projects\YourProject"
takeown /F $projectPath /R /D Y
icacls $projectPath /grant "$env:USERNAME:(OI)(CI)F" /T
icacls $projectPath /reset /T

This forces full ownership and resets ACLs. After running, retry the study.

3. Network Latency & Mapped Drives

Are you running the study from a network drive (Z: or Y:)? Moldflow struggles with high-latency connections. When the solver asks for exclusive write access over a slow VPN or WiFi, the handshake times out and throws Error 99998.

The Fix:

• Never run a solver job from a network drive.
• Copy the entire study folder to your local C:\Moldflow_Temp\ drive.
• Run the analysis locally. Copy the results back to the network when finished.

Fix 1: Manual Deletion of Lock Files (The Classic Solution)

1. Navigate to your project folder: \\Server\Share\Moldflow_Projects\YourProject\
2. Close Moldflow entirely.
3. Enable "View Hidden Items" in File Explorer.
4. Look for files with these extensions:
   • *.lck
   • *.lock
   • *.~lock.*
   • A hidden folder named __lock__
5. Delete all lock files. Do not delete study files (.sdy, .mfj, .mfr).
6. Also check the subfolder for the specific study: YourProject\Study_001\ for any .lck files.
7. Reopen Moldflow and access the study.

Note: On some network systems, lock files are stored in a central \Locks directory. Consult your IT admin.

3. Train Users on Clean Exit

Never force-close Moldflow using Task Manager while a study is open. Always use File > Close Study and File > Exit.

The User Experience: Sudden and Merciless

The "Exclusive" error does not mess around. Unlike other errors that offer a helpful suggestion (e.g., "Mesh has overlapping elements"), Error 99998 is a gatekeeper. It usually manifests at the very beginning of an analysis, often during the "Initialization" or "Input deck processing" phase.

The error message is blunt:

Error 99998: The file is locked exclusive by another process.

In layman’s terms, Moldflow is trying to read a file (usually the .stud or results file), but something else has grabbed it and refuses to let go. It is the software equivalent of walking into your own house and finding the door bolted shut from the inside.

The "Exclusive" Context

In Moldflow, certain operations—particularly 3D Tetrahedral meshing, Flow-Pack-Warp (FPW) simultaneous solves, or Fiber Orientation analysis—require an exclusive license. This means:

1. No other process on your machine can use that license feature simultaneously.
2. The license cannot be borrowed from a network server in a "shared" or "concurrent" state.
3. The solver demands a write-lock on specific temporary folders and memory addresses.

When Moldflow throws Error 99998 exclusive, the solver has identified a conflict. It could be a stale license handle, a conflicting background process, a network latency issue, or even a corrupted temp file from a previous crash.