Fix: Asset Replenishment Notification failure in Non-ESM setups
Issue:
In non-ESM setups, when Graph is configured in the Outgoing settings, Asset Replenishment Notifications aren't sent. It failed with the below trace.
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.tasks.ChangeMigrationTask]|[INFO]|[183]: ChangeMigrationTask has been Instantiated|
[07:42:18:034]|[09-09-2024]|[com.adventnet.servicedesk.common.MailUtilities]|[INFO]|[362]: Inside setEsmMailOperation|
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.mail.sender.MailSender]|[INFO]|[362]: Going to get enabled MailSender instance|
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.mail.sender.MailSender]|[INFO]|[362]: Enabled outgoing server graph|
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.mail.sender.MailSender]|[INFO]|[362]: Going to get graph MailSender instance|
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.mail.sender.JavaMailSender]|[INFO]|[362]: Going to send mail using javamail|
[07:42:18:034]|[09-09-2024]|[com.manageengine.servicedesk.mail.sender.GraphMailSender]|[INFO]|[362]: Going to send mail using graph sender|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: com.manageengine.servicedesk.mailutils.MailException: No mail server found for given mailserver ::graph and serverId ::null|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: at com.adventnet.servicedesk.common.MailUtilities.getOutgoingConnectionMap(MailUtilities.java:3686)|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: at com.adventnet.servicedesk.common.MailUtilities.getOutgoingConnectionMap(MailUtilities.java:3620)|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: at com.manageengine.servicedesk.mail.sender.MailSender.getInstance(MailSender.java:124)|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: at com.adventnet.servicedesk.notification.util.NotificationFactory.sendMail(NotificationFactory.java:872)|
[07:42:18:034]|[09-09-2024]|[SYSERR]|[INFO]|[362]: at
Fix:
This issue due to internal handling has been fixed now. Kindly follow the below steps to fix this
Steps to apply the fix
1. Download the attached .fjar file corresponding to your build version.
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 https://bonitas2.zohocorp.com/. Select the product as "ServiceDesk Plus" and provide the proper ticket number.
Note: If you already have .fjar files in the fixes folder, kindly upload those fjar files using the above link (select debug option) and cross verify with the support technician on any conflicts with the new fjar file due to existing ones.
Jar compatibility:
Build | Fjar file name |
14503 | 14503_10288947.fjar |
14820 | 14820_10288947.fjar |
7530 | 7530_10479819.fjar |
Issue ID: SD-123810
New to ADSelfService Plus?
Related Articles
Assign Technician for the unassigned requests using Notification Custom Function
Requirement: When a technician addresses an unassigned request, the corresponding ticket is automatically assigned to that technician. Steps to configure: 1. Download the attached scripts. Copy the contents into Notification custom functions. 2. Goto ...Query to show Non IT assets or the assets that does not consume license (MSSQL & PGSQL)
Tested in Build PGSQL (14300) or MSSQL (14306) SELECT MAX(resource.RESOURCENAME) AS "Asset Name", MAX(resource.ASSETTAG) AS "Asset Tag", MAX(product.COMPONENTNAME) AS "Product", MAX(productType.COMPONENTTYPENAME) AS "Product Type", ...AD Sync issue_Rootpath failure
Error trace: 09:48:46:989]|[10-31-2019]|[com.adventnet.servicedesk.asset.util.WorkStationDiscoverUtil]|[INFO]|[62064]: Log message from WMI task : mwc-dc-01 - LDAP Search : Root Path Failure. (0x8007052e)| ...Fix for Frequent Out of storage notification
Issue: Frequent "Out of storage" notifications in Bell notifications. What's happening in the backend. 1. Some of the mails aren't deleted from the mailbox after getting processed. 2. These mails are fetched again by SDP since SDP fetches all mails ...Debugging JAR for ESM outgoing configuration failure
Issue: Unable to save ESM outgoing configuration. Note: The fjar is only for debugging purpose. Before applying the .fjar file, kindly verify its compatibility in the "Jar Compatibility" section below. Steps to Apply the Debug FJAR and Collect Logs: ...