Error Restarting Transient Particle Tracking
 

I've been running a transient particle tracking simulation with fortran Particle User Routines for erosion calculations but have come across an error when trying to restart the simulation. I get the below error at the end of the 4th outer loop and it seems to be to do with the wall erosion routines not being transferred/located. Has anyone seen something similar before or know a workaround?


Parallel run: Received message from slave
-----------------------------------------
Slave partition : 9
Slave routine : ErrAction
Master location : PRB_MESSAGE
Message label : 001100279
Message follows below - :

+--------------------------------------------------------------------+
| ERROR #001100279 has occurred in subroutine ErrAction.
| Message:
| Unknown user routine ZN1


Parallel run: Received message from slave
-----------------------------------------
Slave partition : 9
Slave routine : ErrAction
Master location : PRB_MESSAGE
Message label : 001100279
Message follows below - :

+--------------------------------------------------------------------+
| ERROR #001100279 has occurred in subroutine ErrAction.
| Message:
| USER ROUTINE: I¦ ˜ could not be loaded. Please check the Lib-
| rary Path, Library Name and Calling Name. For FORTRAN user routin-
| es, the Calling Name should be in lower case.

Parallel run: Received message from slave
-----------------------------------------
Slave partition : 9
Slave routine : ErrAction
Master location : PRB_MESSAGE
Message label : 001100279
Message follows below - :

+--------------------------------------------------------------------+
| ERROR #001100279 has occurred in subroutine ErrAction.
| Message:
| Stopped in routine PT_WALL_USER

+--------------------------------------------------------------------+
| An error has occurred in cfx5solve:

| The ANSYS CFX solver exited with return code 1. No results file |
| has been created.
+--------------------------------------------------------------------+

The solution was as simple as changing the name of the input file (.def) so it was different from the result (.res), classic!