Mail Fetching : Inline Image URL Replace error.

Mail Fetching : Inline Image URL Replace error.

Mail fetching is stopping due to inline image Handling. The problem with replacing inline image URLs is the underlying cause of the issue. The issue will occur during addition of conversation not in new request creation.

java.lang.NumberFormatException: For input string: "098f121299a04f708cb00ed4b247e42a.png"
at java.lang.NumberFormatException.forInputString(
at java.lang.Long.parseLong(
at java.lang.Long.valueOf(
at com.manageengine.servicedesk.v3api.utils.InlineImageUtil.getMediaIdFromMediaUrl(
at com.manageengine.servicedesk.v3api.utils.InlineImageUtil.handleHTMLContent(
at com.manageengine.sdpod.v3api.handlerimpl.DefaultEntityHandler.processInlineMediaFiles(
at com.manageengine.sdpod.v3api.handlerimpl.DefaultEntityHandler.handleHTMLContent(
at com.manageengine.sdpod.v3api.handlerimpl.RequestNotificationHandler.handleHTMLContent(
at com.manageengine.sdpod.v3api.handlerimpl.PreDefaultEntityHandler.add(
at com.manageengine.sdpod.v3api.handlerimpl.RequestNotificationHandler.add(
at com.manageengine.sdpod.v3api.handler.AbstractEntityHandler.handleAPICall(
at com.manageengine.common.util.CommonAPIUtil.invokeAPICall(
at com.manageengine.servicedesk.v3api.utils.SDPAPIUtil.invokeAPIInternally(
at com.manageengine.servicedesk.v3api.utils.SDPAPIUtil.invokeAddAPI(
at com.manageengine.sdpod.v3api.workflow.action.InternalAPICallActionDispatcher.fireAction(
at com.manageengine.sdpod.v3api.workflow.action.InternalAPICallActionDispatcher.invokeInternalAPICall(
at com.manageengine.sdpod.v3api.workflow.action.InternalAPICallActionDispatcher.invokeInternalAPICall(
at com.manageengine.sdpod.v3api.workflow.action.InternalAPICallDetail$InternalAPICallBuilder.buildAndInvoke(
at com.manageengine.servicedesk.mailutils.RequestMailUtil.addConversationViaAPI(
at com.manageengine.servicedesk.mailutils.RequestMailHandler.processRequestAddition(
at com.manageengine.servicedesk.mailutils.RequestMailHandler.handleMailObject(
at com.manageengine.servicedesk.mailutils.ModuleHandler.handleMailObject(
at com.adventnet.servicedesk.mailutils.MailProcessor.processEMail(
at com.manageengine.servicedesk.mail.core.fetcher.EwsMailFetcher.fetchAndProcessMails(
at com.manageengine.servicedesk.mail.core.fetcher.MailFetcher.startFetching(
at com.adventnet.servicedesk.helpdesk.mail.task.MailFetchingTask.executeTask(
at com.adventnet.taskengine.internal.SchedulerBean.executeTask(
at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at com.adventnet.mfw.bean.BeanProxy.lambda$invoke$0(
at com.zoho.mickey.api.DefaultCodeBlock.execute(
at com.adventnet.mfw.bean.BeanProxy.invoke(
at com.sun.proxy.$Proxy4.executeTask(Unknown Source)
at com.adventnet.taskengine.internal.ScheduleExecutor.executeNextTask(
at java.util.concurrent.Executors$
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Apply the attached fix jar to resolve the issue.

Before applying the .fjar file, kindly verify its compatibility in the "Jar Compatibility" section below.

Steps to apply the fix:
1. Download the attached .fjar file.
2. Click here for steps to apply the .fjar file.
3. Restart the application service.
4. If the issue occurs again, enable the email debug in the application, recreate the issue after enabling the email debug then immediately zip the logs (<server_home>\logs folder. For eg: C:\Program Files\ManageEngine\ServiceDesk\logs folder) and share it with us for analysis. If the size of the log file is huge, you can send it to us using our FTP link Select the product as "ServiceDesk Plus" and provide the proper ticket number.

Jar Compatibility:

Compatible Jar
14504, 14505, 14506 & 14600

Issue ID:
Please verify the mentioned issue ID in the readme. If it's not listed, please wait while we address the issue. Once the fix is implemented in a build, we will update the issue ID in the readme.‚Äč

                    New to ADSelfService Plus?

                      • Related Articles

                      • Mail Fetching Stopped Due to Inline Image Handling

                        Issue Cause : While fetching a mail, in certain mail servers, cid of inline image is not parsed correctly. Once inline stream is converted to image, cid in src attr will be replaced with image url. cid for uploaded inline image in mail content is not ...
                      • 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 ...
                      • Troubleshooting Oauth configuration for mail server settings

                        Oauth in ServiceDesk Plus / AssetExplorer for Mail SDP supports Oauth configuration for Office365 and GSuite mailboxes since 11106 build. Office365 mailboxes can be configured with Oauth authentication using EWS (since 11106) and IMAP / SMTP (since ...
                      • Fix JAR for Parse Error Exception Raised during Mail Fetching

                        Issue : Some mail are fetched and created as ticket without description due to message corruption temporarily. The issue is can be identified with the below trace. Fix : The issue is not recreated when the mail is skipped to next schedule and fetched ...