Number of notifications triggered - Debug
Issue: At times, the EWS service gets throttled and thus impacting the mail sending process
Debug: Since, there isn't much information about the number of mails triggered in a given period, debug traces has been enabled to print the relevant traces. Kindly follow the below steps to place this debug file
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, 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.
New to ADSelfService Plus?
Related Articles
Debug: Mail sending failed in Graph due to Semaphore issue
Issue: Mail sending via Graph triggered from Job Scheduler (system notifications) are failed due to internal Semaphore acquire timeout. This may happen when two threads initiated from Job scheduler are holding the thread for long time. Debug: The ...Logout Debug
Fjars for Logout DebugQuery to find the list of Notifications high in number (outofoffice and microsoft emails) with a limit of 10 requests
MSSQL: Select top 10 WorkorderId, (Select Count(*) from Notify_WorkOrder where Notify_WorkOrder.WorkorderId = WorkOrder.WorkorderId) AS NotificationCount from Workorder Order by (Select Count(*) from Notify_WorkOrder where ...Mail Fetching : Out Of Storage Notifications Are Triggered Incorrectly
Issue: In some cases, out of storage notifications are triggered incorrectly while fetching mails. Issue ID: SD-119798 Fix: Use the provided fix JAR file to resolve the issue. Note: Before applying the .fjar file, kindly verify its compatibility in ...Query to show total number of conversations, incoming and outgoing conversations (MSSQL & PGSQL)
Tested in build PGSQL (14300) and MSSQL (14306) Total Number of Conversations: SELECT wo.WORKORDERID AS "Request ID", wo.TITLE AS "Subject", pd.PRIORITYNAME AS "Priority", aau.FIRST_NAME AS "Requester", ad.ORG_NAME AS "Account", std.STATUSNAME AS ...