Email fetching stops intermittently
Error Trace
[17:36:08:969]|[07-05-2021]|[com.adventnet.servicedesk.kbase.util.AttachmentUtil]|[SEVERE]|[168]: exception occurred while writing to temporary attachment file |
java.io.FileNotFoundException: G:\fileAttachments\fileAttachments\Conversation\365001_370000\368734\CONVERSATION_DESCRIPTION.html (The file or directory is corrupted and unreadable)
Cause and Solution
The path where the email attachment is stored is not reachable. Under Admin >> Self Service Portal >> Check if the Path is set properly
New to ADSelfService Plus?
Related Articles
Fix: Mail fetching stops due to invalid characters in the attachment name
Issue: Mail fetching being stopped due to invalid characters "?" , ":" in the filename. In this case, the eml file's subject contains ":" character and so, while uploading the .eml as attachment, error is thrown (Only in windows server) Trace: ...Mail Fetching - Error while processing attachment and inline image.
Issue During the process of fetching emails, attachments are dropped as a result of the presence of directory traversal characters. Furthermore, an issue arises when processing inline images, this particular error related to inline images results in ...Mail Fetching: Inline Images Dropping Due to Invalid Extension
Issue: The inline image's file name from the email doesn't contain the extension. Example: filename = sys_attachment.dosys_id=5bb0751c8303b5dc96a238226daad371 As a result, the inline image gets stripped during the mail fetching process. The sender of ...Mail fetching stops intermittently_IndexOutOfBoundsException
Error trace: [com.adventnet.servicedesk.helpdesk.mail.task.MailFetchingTask]|[SEVERE]|[129]|: General Exception - Exception when trying to get messages. SO RETURNING...|java.lang.IndexOutOfBoundsException at ...Mail fetching issue: Fetching stops when mail sent from unapproved user (with huge description)
Issue : Mail fetching stops when mail sent from an unapproved user Issue found in Build number : 14200 Issue fixed in Build number : 14300 Issue ID: 20438 Error trace: ...