We've just implemented a server level trigger on our SQL Server 2014 instance. It's working as expected ... except it breaks the Dynamics CRM which is hosted on premise on the same server.
In short, no developer is able to alter an entity. Whenever they do, they get this error:
A SQL Server error occurred.
Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #EFBBF1B9
If we disable the trigger then it's fine. There is nothing in the SQL Server logs. And the trigger itself is a pretty standard auditing type trigger.
Any ideas?
Leaving this out there for people in the future. It was due to permissions.
I gave the user that CRM logs on to db_owner rights, and it worked, so I'm going to work backwards from here and find the minimum they need.