Spool Folder

[T_Winkler]

Last week problem was solved. The reason was, that one or more of the left jobs stucked the normal process of deleting finished job. After manual deleting the Jobs on the surface, the function of the automatic is running well again.

[GhostSkunk]

---

@DavidU54339-XRX wrote:

These files should be removed from the spool directory when they are removed from the Job Management GUI. Contacting Xerox support to get to the bottom of this is the best option. greatpeople

---

No the jobs are leaving the frontend after 24 hours. But the folders are left in the spool folder, also with PDFs and XML description. So we made a script that removes old PDF files out of the folders.

[DavidU54339-XRX]

These files should be removed from the spool directory when they are removed from the Job Management GUI. Contacting Xerox support to get to the bottom of this is the best option.

[T_Winkler]

No the jobs are leaving the frontend after 24 hours. But the folders are left in the spool folder, also with PDFs and XML description. So we made a script that removes old PDF files out of the folders.

But now the mass of folders slows down the explorer and FreeFlow itself.

[DavidU54339-XRX]

Are the jobs still visible in the Job Management GUI? If not, the components of the jobs should not be in the spool folder.

[DavidU54339-XRX]

The optimal way to get progress on this, is for a customer (e.g., you) to contact Xerox support and submit a problem fix request.

[T_Winkler]

Hello David,

we have now about 500000 folders in our spool. We purge the PDF files out of it, but the amount of files seems to be too large now. FreeFlow needs over 90 min to restart.
What can we do help the system?

In our mind, the folders with control files are listed in the FreeFlow database .
So we would like to delete all the folders, that are not in that list (dbo.ResourceDescriptionAttributes).

Are there any other ideas from the developers?

A purge of the finished files should delete the spool files, also.

[DavidU54339-XRX]

Be careful with the .xml files. If you set a Preflight node to use xml for the output of a preflight report, you may want to hold on to it. The temp.xml files are usually always candidates for deletion.

[DavidU54339-XRX]

Correct. The pdf, xpf and xml files are associated with jobs (not component settings e.g., job characteristics).

[mpeters]

Thanks David. I did in fact run into that prompting a Veeam VM restore from previous day backup. So, good advice!   :-)   So, just to be clear, we would be safe as long as we script the delete to only remove PDF, XPF, and XML?