Recently with the Microsoft Exchange changes Sage CRM has been working hard to allow for the integration to continue to work seemlesly.

However we have had a couple of support cases from customers with integrations doing rather strange syncs. We have found that CRM customers that have quite a historical upgrade path are the ones with this issue compared to clean and fresh instances of CRM and Exchange integrations.

The insert error is basically because of the long-tail upgrade of a CRM database that was originally installed using version 5.6 or 5.7 (back in 2007, so almost 18 years ago).  Back then, CRM relied on stored procedures to provide primary key values for all record inserts.  Since then, the CRM schema uses SQL IDENTITY on all primary key columns.

So, as a quick fix, could you please insert the failed statement manually along with the USet_SettingId. This will not give any error once you have manually entered it.

For some cases deleting the Exchange integration from CRM versions 2022 and above supported version and reinstalling the latest patches have fixed this issue.

On top of that this has also been officially fixed in CRM 2025R2.

Should you have any current Exchange integration issues with your environment please do not hesitate to create a support ticket in your local area and Sage Support will be able to assist with further details and in depth instructions on how to solve your issue.