Add2Exchange Synchronization FAILURE source message
Older versions of Add2Exchange may experience this known issue after long periods of synchronization if the Add2Exchange Service gets interrupted without being able to exit gracefully.
We can assist and remotely log in as a Level 2 support incident and make sure it works correctly for you. We will also do it at no additional charge if you have purchased a critical or priority support incident.
The following error message appears in the Add2Exchange Event Viewer log:
Event 1004 Add2Exchange Synchronization FAILURE source message: Cass Blevins of Relationship: Public – Contacts To Bob Charles – Contacts
Event 9997 20100426123653: FAILURE_1: RC <> 0. A2EMsgObjectSRC.saveMessageObject method failure to save message object for Destination Message. | Calling program: A2ESP
The failure you are experiencing could occur on these previous versions because older versions of Add2Exchange did not employ SQL transaction logic and when the server was rebooted during the synchronization processing or you did a Microsoft update without stopping the Add2Exchange Service prior and rebooting afterwards, the older version filled the table with partially completed rows. The newer versions of Add2Exchange have transaction processing technology and indexing to avoid this from happening going forward, but you should still stop the service prior to any reboot or Microsoft update to be safe.
To fix the issue, you must be running the current version.
Go to the Downloads area on our website to upgrade to the newest release.
Make sure you select the correct version you are licensed for — Standard or Enterprise Edition.
Before you install it, please go into the Add2Exchange Console and make sure you have valid software subscription (date expires today or in the future) and then get the new version for free or if it is expired, you will have to purchase a Current Version Upgrade license prior to installing.
Upgrade instructions here.
You will also need to run the sanitizedb utility, located in the zip file download prior to opening the Add2Exchange Console. More information here.
Then open up the Console. There may be a pause where it says it is creating the indexes. Let it continue even though it may say not responding. When the Console opens, you can continue as normal, your system is not updated and stable. While in the Console, check for to make sure licensing is current.
Effects on synchronization
The effect of having invalid rows in the database allowed by prior versions is that some deleted items may come back and/or some changed items may revert (just once) after the rows are deleted. What happens in a specific environment is determined by the kind of relationships set up in the Add2Exchange Console.
Deleting the invalid rows does not directly change the source or destination folders, just the meta data (data about the data) information A2E uses to determine what do on edits and deletes of an item. Saving the information will do nothing either, but people needed that option to feel safer.
These items with invalid rows were not replicating correctly anyway, and once the invalid rows are deleted, after just two complete sync cycles, the normal rules of the replication relationship will work as designed again. The first sync may revert a change to another users changed copy in a bidirectional relationship which may not be the intended result.
The tips here are to stop the A2E Service, upgrade to the latest MS Critical Service packs and then (always) reboot, then make sure you download and run the latest version of diditbetter.com software, and then run the sanitize DB tool as soon as possible.