The simulation isn’t running. Now comes the temptation to change a few settings, press Run again and hope one of them was the problem.
Before doing that, let us find out how far it got. Did the solver start at all? Did it reach a particular stage? Or did it stop because it reached a condition you selected?
Read the message with its surrounding lines
If no solver output appeared, open Start a Computation again. Check the host, working directory and action. Write input file only doesn’t launch a calculation, even when it finishes successfully.
For a license message, use the licensing post. For a host problem, go to host configuration. Neither is normally fixed by changing the blankholder force.
If the solver started, open Solver Messages and read the first relevant error with nearby output. Follow any named object, element or stage into the model.
An early finish may also be a stop criterion. Look at progression, pinch or convergence settings before calling it a crash.
What changed since it last worked?
A thickness edit may need rebuilt tools. Orange in Tool Editor means an update is waiting. The solver input may also be older than the setup you are looking at.
If you used both the Process Editor and manual tree edits, inspect the final attributes. Applying the editor can replace an earlier change.
For the 2025 kept-zone trimming error, choose a kept-zone element away from the trim line. The trimming post explains that particular message.
Keep the next trial useful
For an element error, inspect the local mesh and contact. For unexpected movement, play the kinematic check. For a missing object or contour, check the display, state and requested output first.
Save a variation, make one reasoned correction and rerun from the appropriate point. If it still fails, you now have an exact message and a reproducible sequence to share with support.
If you leave a comment asking for help, include those details too. “It doesn’t work” is understandable, but the stage and message give someone a chance to help.
Previous: Restart or Recompute a PAM-STAMP 2025 Study
Next: Non-uniform and Physical Drawbeads in PAM-STAMP 2025
[…] the error text or environment differs, return to the general troubleshooting post and follow the message you actually […]