Autodesk Moldflow - Error 99998 ((better))

The Case of the Phantom Partition

It was 2:00 AM on a Tuesday, and the coffee in the breakroom had long since turned into a sludge resembling the amorphous polymer Eduardo was trying to simulate.

Eduardo stared at his dual monitors. On the left, the assembly file for the 'Aero-Spacer'—a complex, thin-walled aerospace component. On the right, the Autodesk Moldflow Insight analysis log. Or rather, the abrupt, crushing end of it.

The simulation had run for four hours. It had navigated the intricate gating system, filled the cavity perfectly, and began the packing phase. Then, exactly at 99% completion, the progress bar froze. A heartbeat later, the dreaded dialog box popped up:

Error Code: 99998

Eduardo groaned, the sound echoing in the empty office. In the world of injection molding simulation, error codes were usually specific. "Element 452 is intersecting." "Injection time too short." But 99998? That was the "General Unspecified Fatal Error." It was the engineering equivalent of a doctor saying, "Well, you're sick, but we don't know why."

He clicked "View Log," though he knew what he would find. The text file was a graveyard of matrix calculations and pressure iterations. Near the bottom, the error sat there, mocking him. "Partition file write failure. External library exception. Code 99998."

"Write failure?" Eduardo muttered. "I have two terabytes of free space."

He did what every desperate engineer does at 2:00 AM. He opened Google. The forums were a tapestry of misery. One user suggested increasing the RAM. Another blamed the graphics card. A third claimed the software was haunted by the ghost of a failed toolmaker.

Eduardo rubbed his temples. The client presentation was at 8:00 AM. He needed that warp prediction. Without it, he couldn't tell them if the part would warp into a useful shape or a potato chip.

The Hunt

He started with the basics.

1. Disk Space: Checked. Plentiful.
2. RAM: Task manager showed 60% usage. Not the bottleneck.
3. File Path: He had seen Moldflow fail on long file paths before. He moved the project to C:\Project. No change.

He ran the analysis again. Crash. 99998.

He simplified the mesh. Crash. 99998.

He turned off the cooling analysis to save processing power. Crash. 99998.

The clock ticked to 3:30 AM. Desperation began to set in. Eduardo walked to the window, looking out at the parking lot lights. Why does a write error happen when there is space?

His mind drifted back to his internship, an old mentor named Silas who used to smoke a pipe by the server racks. Silas used to say, "Software doesn't crash because of magic, kid. It crashes because it's trying to put a square peg in a round hole, or it's trying to count to infinity and runs out of numbers."

Eduardo snapped back to the screen. "Count to infinity."

The error log mentioned a "Partition file." Moldflow, during a dual-domain or 3D analysis, slices the model into millions of tiny tetrahedra (pyramids). Sometimes, during the packing phase, the pressure equations become unstable at specific nodes. If the calculation produces an impossible number—

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.

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. autodesk moldflow error 99998

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.

Error 99998 Autodesk Moldflow typically indicates that the required solver license

(AMI_STANDARD, AMI_PREMIUM, or AMI_ULTIMATE) is unavailable or cannot be reached

. While the Synergy interface (the UI) may open correctly, this error triggers the moment you attempt to start an analysis because the solver—which requires its own license—fails its check. Autodesk Community, Autodesk Forums, Autodesk Forum Common Causes Missing or Expired Licenses

: The license for the specific solver (e.g., MFIB, MFIP, or MFIA) is missing from the server or has expired. Incorrect License Configuration

: The software is pointing to the wrong license server, or the "License Configuration" utility hasn't been set up on the local machine. Mismatched Software Versions

: Moldflow Synergy and Moldflow Insight are not on the exact same update version (e.g., Synergy is 2023.1 but Insight is still 2023.0). Network Connectivity

: The computer cannot resolve the license server's hostname to an IP address, common when using a VPN or across different network domains. Step-by-Step Troubleshooting Verify License Status (LMTools) on your license server, go to the Server Status tab, and click Perform Status Inquiry

. Ensure your Insight solver licenses (e.g., AMI_STANDARD) are listed and not fully checked out by other users. Run the License Configuration Utility

Close all Moldflow instances and go to the Windows Start Menu: Navigate to Autodesk Moldflow Insight 202X License Configuration 202X Confirm the License Mode (Network), License Level (Standard/Premium/Ultimate), and Server Name are correct. Check Version Matching

Open your Windows Control Panel and check "Uninstall a program." Ensure the version numbers for Autodesk Moldflow Synergy Autodesk Moldflow Insight

match exactly. If one has an update applied (e.g., Update 1), the other must have it as well. Address Linux-Specific Solver Issues If running solvers on a Linux machine, ensure the ADSK_SERVICE_ADDRESS environment variable is set correctly in the mfclient.env (thin client) or /etc/opt/Autodesk/ami-20XX (workstation) files to point to the Autodesk Licensing Service Kill Rogue Solver Tasks Check your Task Manager for "ghost" solver processes like

. If a previous analysis crashed but didn't release its license, ending these processes manually can free up the license for a new run. command line steps for manually resetting the license server address using the AdskLicensingInstHelper tool

The infamous Autodesk Moldflow error 99998. It was a mysterious code that had been plaguing engineers and designers for years, striking fear into the hearts of those who relied on the software to design and optimize their injection molded parts.

For Emily, a young design engineer at a small plastics manufacturing company, the error code was more than just a frustrating anomaly - it was a recurring nightmare. She had been working on a critical project, designing a complex part for a high-profile client, and Moldflow was her go-to tool for simulating the injection molding process.

As she worked tirelessly to fine-tune her design, Emily encountered the error 99998 for the first time. She tried restarting the software, checking her model for errors, and even reinstalling Moldflow, but nothing seemed to work. The error persisted, taunting her with its cryptic message: "Error 99998: Unknown internal error."

Desperate for a solution, Emily turned to online forums and Autodesk support resources, only to find that she was not alone in her struggle. Many others had encountered the same error, but few had found a reliable fix. Some reported that it was related to corrupted files, while others claimed it was a compatibility issue with certain graphics drivers.

As the deadline for her project loomed closer, Emily became increasingly frustrated. She spent hours trying to troubleshoot the issue, but every potential solution led to a dead end. Her client was breathing down her neck, and she knew that if she couldn't deliver a working design, her company's reputation would suffer.

One evening, as she was about to give up, Emily stumbled upon a posting from a Moldflow expert who claimed to have encountered the same error. The expert suggested that the issue might be related to a specific mesh setting, which was causing the software to crash.

Emily decided to give it a try, adjusting the mesh settings according to the expert's recommendations. To her surprise, the error 99998 disappeared, and Moldflow ran smoothly. She was ecstatic, feeling like she had finally tamed the beast.

But her relief was short-lived. A few days later, Emily encountered the same error again, this time on a different project. It seemed that the fix was not a permanent one, and the error had simply been lying in wait, ready to pounce.

As the days turned into weeks, Emily became obsessed with finding a reliable solution to the error 99998. She worked closely with Autodesk support, providing detailed logs and crash reports, and even participated in beta testing for a new Moldflow release.

And then, one morning, Emily received an email from Autodesk with a breakthrough. A new patch had been released, specifically addressing the error 99998. The patch was a game-changer, resolving the issue once and for all.

Overjoyed, Emily applied the patch and verified that her designs were running smoothly. She breathed a sigh of relief, feeling a sense of closure and vindication. The error 99998 had been vanquished, and she could finally focus on her work without interruption.

As she looked back on her ordeal, Emily realized that the error 99998 had taught her a valuable lesson. It had shown her the importance of persistence, collaboration, and staying up-to-date with software updates. And it had reminded her that even in the face of frustration and uncertainty, a solution was always just around the corner.

Error 99998 in Autodesk Moldflow is a license-related error that occurs when the solver fails to obtain a valid license for Insight (AMI) Adviser (AMA)

. It typically indicates that the software cannot communicate with the license server, all available seats are in use, or the configuration is incorrect. Primary Causes Missing or Incorrect Configuration License Configuration Tool

has not been run or contains the wrong server name/IP address. License Exhaustion

: All purchased licenses are currently checked out by other users. Network/Firewall Blocks

: Communication between the workstation and the license server is blocked, or the server is down. Installation Conflicts

: Using an incorrect product key during installation, such as using a Synergy key for Insight, or having old beta versions installed. Server Timeout

: The license request times out before receiving a reply from the server. Troubleshooting Steps Run License Configuration Close all Moldflow instances. License Configuration

tool (found in the Windows Start menu under the Moldflow folder). Ensure the License Mode License Level (Standard, Premium, Ultimate), and Server Name are correct. Verify License Availability LMTools Utility to perform a "Status Inquiry". Check for active solver tasks (like

) in the Task Manager that may be "hanging" and holding onto a license. Adjust Environment Variables If you experience timeouts, create a system variable named FLEXLM_TIMEOUT with a value of (10 million) to allow more time for the license handshake. Verify the ADSKFLEX_LICENSE_FILE

variable in the Windows registry points to the correct server. Special Considerations for Linux Ensure the Autodesk Licensing Service (ALS) is running.

Verify that the Linux machine has unrestricted access to required URLs if using Named User licensing User Perspectives The Case of the Phantom Partition It was

Users often find that separate installations for the UI and solver can cause confusion.

“Assuming the license server has been configured correctly... this error is typically associated with an incorrect product key being entered when initially installing the software.” Solved: ** ERROR 99998 ** - Autodesk Community Autodesk Community, Autodesk Forums, Autodesk Forum · 7 years ago

“Moldflow simulations fails with Error 99998 - AMI_STANDARD license not available after timeout is reached.”

Troubleshooting Autodesk Moldflow Error 99998 Error 99998 in Autodesk Moldflow typically indicates that a required license (such as AMI_STANDARD AMI_PREMIUM AMI_ULTIMATE

) is unavailable or cannot be reached by the solver. This error prevents an analysis from solving and often appears in the analysis log or a pop-up window. Common Causes License Configuration:

The license level or server information has not been correctly set in the local or network computer. Network Connectivity:

The client machine cannot communicate with the license server due to firewalls or incorrect server hostnames. Product Key Mismatch:

An incorrect product key was used during the initial installation of Insight or Synergy. SCM Issues: For newer versions (2021+), the Simulation Compute Manager (SCM) may not have access to the licensing information. Operating System Specifics:

On Linux, the licensing service might not be running or URLs for Named User licensing could be blocked. Standard Solutions for Windows

For Moldflow Insight or Adviser 2023 and newer, follow these steps provided by the Autodesk Support Technical Article Close all Moldflow instances: Ensure no Synergy or Insight processes are active. Open License Configuration: Go to the Windows Start Menu, expand the Autodesk Moldflow Insight 202X folder, and select License Configuration 202X Verify Settings: Ensure the License Mode (e.g., Network) is correct. Confirm the License Level

matches your purchased subscription (Standard, Premium, or Ultimate). Add the correct License Server Hostname or IP address. Apply Changes: and wait for the confirmation message before clicking Advanced Troubleshooting

Step 4: Add Exclusion Rules to Antivirus Software

Configure your antivirus to exclude the following folders:

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

For Windows Defender: Go to Virus & threat protection → Manage settings → Exclusions → Add exclusion (Folder).

6. Update or Roll Back Drivers

• Update GPU drivers (less likely, but known to cause OpenGL solver visualization crashes).
• For network licenses, ensure FlexNet service is updated.

When All Else Fails

If Error 99998 persists:

• Test on another computer – Isolates hardware or OS issues.
• Reduce model scale – Simulate only a representative section (e.g., a 1 mm slice of a thick part).
• Contact Autodesk Support – Provide the solver log (*.out or *.log file from the study directory). Look for lines near the end just before "FATAL ERROR."

Prevention Tips

• Always run Mesh > Diagnostics before analysis.
• Save studies incrementally (e.g., project_v01, project_v02).
• Avoid running other memory-intensive software (CAD, browsers) simultaneously.
• Keep Moldflow updated with the latest service packs.

Conclusion

Error 99998 is a broad "catch-all" failure, but in most cases it stems from either mesh issues or insufficient memory. By systematically checking system resources, repairing the mesh, and resetting process parameters, you can resolve the error and get back to simulation. If the problem remains, the solver log file is your best ally in diagnosing the root cause.

Have you encountered Error 99998 with a specific material or part geometry? Share your experience in the comments below.

Autodesk Moldflow Error 99998 is a licensing error that indicates the software cannot find or access the required solver license (Insight) to run an analysis

. It typically occurs when the "Synergy" user interface is licensed correctly, but the "Insight" solver is either unlicensed, misconfigured, or unreachable. Common Causes Expired or Missing License

: The license file does not include the Insight solver (MFIB, MFIP, or MFIA) or the license has expired. All Licenses in Use

: Every available solver seat is currently occupied by other running analyses. Server Connection Issues

: The client machine cannot communicate with the license server due to firewall blocks, network domain differences, or an incorrect server IP/name. Incorrect Installation/Configuration

: The wrong product key was used during installation, or the LICPATH.LIC file points to the wrong server. Version Mismatch

: Using an Ultimate license level feature while only a Premium license is installed or configured. Troubleshooting Steps

To resolve this error, follow these technical solutions based on your environment:

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.

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. Disk Space: Checked

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:

1. Remeshing the problem area around node 1847292 (refining locally).
2. Slightly increasing the injection speed to reduce shear heating variation.
3. Changing the solver temperature convergence tolerance from 0.1 to 0.5°C.

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.

Autodesk Moldflow Error 99998 is a critical licensing issue that occurs when the software's solver (Insight) cannot acquire a valid license from the server. The error message typically states: "Required license for AMI_STANDARD, AMI_PREMIUM or AMI_ULTIMATE is not available, or all licenses are currently in use". Core Causes This error often stems from one of three primary areas:

Availability: All available licenses are currently checked out by other users or active jobs.

Configuration: The client machine is pointing to the wrong license server, uses an incorrect port, or has an outdated Network License Manager (LMTools).

Connectivity: Firewalls are blocking communication, or the network timeout is reached before a license is granted. Top Troubleshooting Solutions

According to Autodesk Support, you should try these fixes in order:

Run the License Configuration UtilityClose Moldflow and search for "License Configuration 202X" in your Windows Start Menu. Ensure the License Mode, Level (Standard/Premium/Ultimate), and Server Name exactly match your subscription.

Increase License TimeoutIf your connection is slow (e.g., using a VPN), add a system environment variable named FLEXLM_TIMEOUT with a value of 10000000 (10 million) to give the server more time to respond.

Check Firewall PortsEnsure the specific ports for your Moldflow version are open for inbound and outbound traffic. For example: 2023: TCP 44100, 44200. 2021: TCP 43100, 43200. 2019 and older: TCP/UDP 43911, 42911, 43921.

Release "Stuck" LicensesOpen Task Manager on the server or client and look for rogue processes like flow.exe, cool.exe, or warp.exe. Ending these tasks can manually release a license that didn't check back in properly.

Verify Product KeysEnsure you used the correct product key during installation. Moldflow Synergy (the UI) and Insight (the solver) require separate keys, which change with every version. Expert Review Summary Commonality

Very High – It is one of the most frequent licensing hurdles in Moldflow environments. Complexity

Moderate – Usually solvable via configuration, but complex for Linux or distributed solve setups. Recommendation

Always check the Autodesk License Parser first to confirm your .lic file actually contains the Insight solver feature.

To address error 99998 or similar issues in Autodesk Moldflow, consider the following general troubleshooting steps:

Conclusion

Autodesk Moldflow Error 99998 is intimidating because it is silent. It does not tell you "your mesh is bad" or "your RAM is insufficient." Instead, it forces you to be a detective. However, in nearly all cases, the culprit is mundane: a space in a folder name, an overactive antivirus, or a full page file.

By systematically eliminating environmental factors (file path, permissions, antivirus, virtual memory) before diving into mesh quality, you will resolve 95% of Error 99998 occurrences. For the remaining 5%, a reinstallation or solver version change is the key.

Remember: Moldflow is telling you that it failed outside of its own error-handling logic. Listen to what your operating system is doing at the moment of failure. Use Windows Event Viewer (look for "Application Error" or "Faulting module name") to pinpoint the exact system-level crash. Armed with this guide, Error 99998 will no longer be a showstopper but a solvable puzzle.

Need further help? Contact Autodesk Support with your solver log file (*.mfl), Windows Event log, and a copy of your study. Mention that you have already excluded path and antivirus issues to accelerate the support ticket.

Last updated: October 2025. Applies to Autodesk Moldflow Insight 2021 through 2025.

Preventing Error 99998 in Future Projects

Once resolved, you can minimize recurrence with these best practices:

• Establish a "Moldflow Root" folder: e.g., E:\MF_DATA\. Never use Desktop, Downloads, or network drives.
• Use naming conventions: ProjectName_Date_StudyType – underscores instead of spaces.
• Monitor memory usage: Use Windows Task Manager while running. If RAM hits 100% and the disk page file spikes, reduce mesh density or use "Dual-Domain" instead of 3D.
• Regularly clean temp files: Automate with a weekly script that clears %temp% and C:\Users\Public\Documents\Autodesk\Moldflow\Temp.
• Keep Moldflow updated: Autodesk releases hotfixes specifically for solver crashes. Always run the latest minor version.

What is Error 99998?

In Moldflow, Error 99998 is a numerical solver’s white flag. It means: “I tried to calculate the flow front, pressure, and temperature, but after thousands of iterations, the numbers won’t settle into a stable solution.”

Physically, this simulates the real world: If your injection molding process settings or part design are too extreme, the actual melt front might oscillate, hesitate, or stall. Moldflow raises Error 99998 to warn you: This part may not fill properly in real life.

But in simulation terms, the solver failed to meet the fill tolerance—a tiny internal threshold for how much the pressure or temperature can change between iterations.

Step 1: Shorten Your File Path Immediately

This solves 70% of Error 99998 cases.

• Move your study folder to a root directory. Example: D:\MF_Studies\
• Rename your study file to a short name (e.g., part1.sdy instead of Left_Hand_Handle_v7_final.sdy).
• Ensure no folder in the path uses spaces or special characters (though spaces are allowed, they can cause issues with older job managers).

Conclusion

Autodesk Moldflow Error 99998 is rarely a bug in the software itself; it is almost always an environmental issue involving file paths, permissions, or security software. By systematically shortening your file paths, cleaning temporary directories, and running locally as an administrator, you can resolve the error in less than 10 minutes.

Remember: When you see 99998, think “file system,” not “mesh quality.”

Keywords: Autodesk Moldflow Error 99998, Moldflow solver error 99998, Moldflow file path error, Error 99998 fix, Moldflow job manager failed, Autodesk Moldflow troubleshooting.

Title: The Midnight Case of Error 99998

Setting: The Product Development Lab, 11:47 PM. A launch deadline looms in 72 hours.

The Character: Sarah, a senior plastics engineer. She has just finished a complex 3D mesh on a thin-walled electronic enclosure. She clicks “Analyze Now.” The progress bar crawls to 32%, then freezes. A red dialog box appears:

“Error 99998: Solution did not converge. Unable to meet fill tolerance.”

Her stomach drops. Not a crash. Not a memory error. Convergence failure.

Fix C: Recreate the Study via Export/Import

If the .sdy file is partially corrupted:

1. Open the problematic study.
2. Go to File → Export → Study Archive (.mfa).
3. Create a new, empty study in a short path.
4. Import the .mfa file.
5. Rerun the analysis.