Interpretation of alerts
We send alerts if we set a timeframe for sync and it doesn’t sync within that time. It will continue to send email alerts every hour on the hour after it starts until it syncs again. Sometimes it happens when many items change and it pushes back the other modules from syncing.
Slow syncs can also happen because there is an erroneous cert prompt, or it can also happen because the module is not ”turned on” and set to sync. Once it resumes a successful sync, it will stop sending alerts.
In the email, the first paragraphs are important:
Add2Exchange 'Template' Alert
Last Start: 3/21/2025 1:12:53 PM
Last End: 3/21/2025 1:14:59 PM
Last Duration: 00:00:02:05
Last Relationship(s) Count: 1
In this system we have one template and it took 2:05 seconds to complete adding and removing relationships.
In this example, the last successful sync was a day ago.
This alert is for Template Alert, which is also known as Relationship Group Management, Relationship Management, Relman, or Template Validation.
This process does the creation and removal of off-boarded users to add and remove relationships.
Last End Difference From Date/Time 03/22/25 2:39:37 PM DD:HH:MM:SS: 01:01:24:38
This line says the system has not synced Relman in one day, one hour 24 minutes and 38 seconds
Interval DD:HH:MM:SS: 00:06:00:00
This says the system is set to run Relman every 6 hours
Interval Alert DD:HH:MM:SS: 00:20:00:00
This says the system is set to alert if not synced within 20 hours
Success Overdue DD:HH:MM:SS: 00:05:24:38
This says the system is overdue the set alert time of 20 hours by 5:24:38
Fortunately, each Alert message has an attachment, which lists the last 6 hours of Add2Exchange Event logging during processing. See the bolded items below
3/22/2025 2:35:08 PM SuccessAudit
Relationship Process For Profile Sa_GALSync@Domain
Synchronization Contact Item 291 Of 295
In this example, syncing was almost done, and was on relationship 291 of 295
ID # 755 Mailbox – Shared Contacts - Contacts To User@domain.com – Shared Contacts Sync
As Of: 3/21/2025 12:43:51 PM And 00:00:00:10 Last Duration (DD:HH:MM:SS)
The last time it synced it took 10 seconds and none were changed “0 Last Source Count Prior 0 Last Destination Count Prior”
EVENT PROCESS ENDED At 3/22/2025 2:35:08 PM And 00:00:05:08 DURATION (DD:HH:MM:SS)
This last relationship took 5:08 minutes to sync completely
IF we do the math, and If it took 5 minutes for each relationship, it would take 24 hours to sync completely. In the original alert email it said
Relationship Process Statistics Report
3/22/2025 2:30:00 PM Last Start
3/22/2025 2:35:07 PM Last End
1 Last Source Count
80 Last Destination Count
This alert reported it had 80 changed items and one new item. This is usually a larger number of items. “1 Last Source Count 80 Last Destination Count“
3/21/2025 12:43:51 PM Last Start Prior
3/21/2025 12:44:01 PM Last End Prior
0 Last Source Count Prior
0 Last Destination Count Prior
01:01:46:09 Last Start Prior To Last Start Duration (DD:HH:MM:SS)
00:00:00:14 Average Duration (DD:HH:MM:SS)
00:00:05:07 Maximum Duration (DD:HH:MM:SS)
Add2Exchange v27.3.3812.3179 | Process ID 2360
This build was from March 2025
Add2Exchange Agent v6.23.1025 20250311 08:38:14 ID 1680
This installation was installed on March 11 2025 at 8:38:14 AM
Summary
The system is taking 5 hours more than we set it to alert for. You should have gotten 5 of these alerts, one every hour
Action Suggested:Do the “Level 2” upgrade from (bottom right) the Tools section of the DidITBetter Support Menu PowerShell (run as powershell)
If that Level 2 option isn’t available yet, do the Add2Exchange Upgrade at the top Right in the same Support Menu
Or let us do it as part of your Premier Support you have on account
Reply back and Request a Premier Support Remote Session and from the replication server.
Logged in as the service account, Go to join.diditbetter.com and use the code provided.