If the user is doing his/her import of the Icsbatch file using the procedures they had always used, it may be that a corrupted program is causing your problem.

To determine if the program is causing this behavior please do the following. Try the same procedure but use sample data and see if it behaves in the same way. If sample data Icsbatch file does not get purged then I would recommend reinstalling the programs.

If we rule out the program as the problem, you may want to check network rights/permissions (if networked), the attributes of the icsbatch file (read only vs. read write).

Try this and let’s see how you make out.