Hundreds of files are accumulating in the document_ticket_temp_path
Hi,
Recently we had a customer where documents in the document_ticket_temp path are getting piled up drastically. These files are not with the usual file naming format. But formed with different characters.
Ex: 9fa28a97-0248-4d49-8c1a-d91d04a38cc2 with type “File”.
These files are not getting deleted, but daily hundreds of these types of files are accumulating.
Unfortunately, still we were not able to find from where these files are coming.
We checked ‘Application Messages’ at the same time that the documents are getting generated inside the Temp path.
Then checked whether any integrations are dealing with this. No clue for this was found.
Took an IFS_HOME dump to see whether we would get any help.
Has any of you experienced these types of issues, where “9fa28a97-0248-4d49-8c1a-d91d04a38cc2” randomly named files are getting generated but not getting deleted inside the document_ticket_temp_path?
Is there any way that we could analyze the IFS_HOME (IFS_dump) of the customer to recognize these files and where they are getting generated?
Any direction to analyze this is highly appreciated.
Hi Pilar. Thank you for this. But customer seems doesn’t like to go for this solution, since we are not aware about the exact reason for generating these files.
Hi Mathias,
With regard to the complete path and the filename, please find the below screenshot. We got another case today, which is having the same issue.
Document_Ticket_Temp_Path
There's something strange going on there, perhaps some customization or integration? The folders with random names are generated by Docman's middle tier for sure, but the file names under each folder should have names reflecting the key values of the document, plus a valid extension. Is there no file extension or is the file extension .file?
Check in EdmFile.FileName for files with such random names.
Lastly, at least during normal operation of Docman, if the files are more than a few hours or days, they can be removed.
Hi @Mathias Dahl , Thank you for the explanation. The extension of these files are related to type ‘file’. Recently we got another customer as well, which reported the same issue. But they came up with a customization, which might cause the issue. It is currently under investigation.
I checked this EdmFile.FileName, from the customer environment at the beginning of this task, but we were not able to find any recourses as far as I remember.
“Lastly, at least during normal operation of Docman, if the files are more than a few hours or days, they can be removed.” , with regard to this statement, can we follow the same thing in these types of scenarios, without knowing the exact path of the file generation process?
@Hiroshi Perera
Did you find any more clues on this one?
If you don't know where the files comes from, I would not dare deleting them. Can you try to guess what is the actual file type, rename them, and try to open them and see? I think IFS does not create any files with .file as file extension unless the customer actually has such a strange file type defined, and check in such files...
Hi Mathias..
No.. Not actually. It’s investigations are still ongoing. We did try what you suggested. We noted, that, most of the files ( the files that were randomly checked) were related to invoices. They were .pdf files. (Invoices). In the application they have proper names, not the system generated names. Then we searched from where theses invoices have been come from. Then we noted they were in Manual Supplier Invoices. But we were unable to find the way how these files have been generated. We felt that it was not the standard way, how these files need be attached as recommended by IFS. So, we requested customer to check this path internally and try to find out a test plan to recreate the issue. Also, this customer used DMS vap. But this is not actively used by them. I found out another case, who has reported the same issue, but they have directly mentioned this document issue temp path file accumulation is due to DMS VAP, and the case was to request the schedule task to delete the files in the document ticket temp path. I could not find more information about this issue other than that. Then I checked with an expert who involved with developing DMS vap, but as confirmed, this issue cannot be happened, unless codes have been customized on top on the codes of DMS vap. So, they mentioned that DMS vap doesn’t touch the standard IFS functionality but use the same paths used by the standard process.
Since we were able to find that randomly checked invoices are attached in the attachment panel, can we assume that it is ok to delete them if they reside in the EDM_FILE_STORAGE_TAB? There are some files that have been created more than years ago. So, customer mentioned that they would check whether they can delete very old files that have been generated in the document ticket_temp_path (May be once more than years ago).
There is another customer who reported the same issue. But seems they gave some DOCMAN related customizations. This customer is not using DMS VAP. So, the next step of this customer also, to check the files that have been created inside the temp path, and to map them from the application side.
