Product: Dynamics 365 for Finance and Operations
Issue: When importing or exporting messages through the Electronic Data Interchange (EDI) module in Dynamics 365 for Finance and Operations, the following exception is thrown: 'The type initializer for 'net.sf.saxon.Configuration' threw an exception.'
Reason: The Saxon 9 library — used for XQuery processing within the EDI module — fails to initialize properly. This is caused by a threading lock conflict (LockRecursionException) within the Saxon library, preventing EDI document processing from completing. This is a known platform-level bug that Microsoft has identified and addressed in later platform releases.
Workaround - Use Batch Import/Export
While a permanent fix is being applied, you can avoid this error by switching to a Batch Import or Batch Export instead of a standard import or export — or vice versa, depending on which process is currently triggering the error in your environment.
Solution - Remove Saxon Version 9 Dynamic Link Library Files
Outdated Saxon Version 9 Dynamic Link Library (DLL) files remaining in your source control or Azure server may cause initialization conflicts. Removing them and performing a full rebuild can resolve the issue.
Remove from Source Control
Delete the old Saxon 9 Dynamic Link Library files from source control so they are no longer included in the build.
Search the Azure Server
Search all drives on your Azure server for any Saxon Version 9 files and remove them. Note that backup copies of Version 9 files may also be present during the search — remove all instances found.
Rebuild
Once all Saxon Version 9 files have been removed, perform a full build and sync.
Solution - Enable the Flight Feature
Microsoft can provide a query to enable the Flight Feature on the server, which resolves this issue
Microsoft can only apply this fix directly on Tier 1 environments.
For User Acceptance Testing (UAT) and Production environments — which are managed directly by Microsoft — you will need to contact Microsoft to have the Flight Feature enabled there if the error occurs in those environments.
This issue is similar to one previously observed in Dynamics 365 for Finance and Operations version 10.0.23, later identified by Microsoft as a platform-related bug and fixed in a subsequent release:
Microsoft Lifecycle Services (LCS) Issue 976195 — "LockRecursionException Fix by reducing the lock scope"
Release: 10.0.49 / Platform Update 73
Status: Quality Assurance (Step 3 of 3)
rev 07/31/26