using the BC.Net with Ax2009 et Ax4 on the same machine might result in a AccessViolationException

using the BC.Net with Ax2009 et Ax4 on the same machine might result in a AccessViolationException

  • Comments 1

I was working on a case where a partner was having problems with the Business Connecter for Ax2009. Calling a method on the AOS resulted under certain circumstances in a AccessViolationException:

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Unfortunately I wasn’t aware that the partner was using Ax4 and Ax2009 on the same server, so it took a while to identify the Microsoft.Dynamics.ClrBridge assembly as the cause. Unfortunately the Ax2009 BC.Net did load the wrong version of the ClrBridge, and that caused that AccessViolationException.

By copying the ClrBridge assembly in the same directory as the executing program resolves this problem.

Known issues with Ax2009 are listed here.

Leave a Comment
  • Please add 2 and 7 and type the answer here:
  • Post
  • I was working on a case where a partner was having problems with the Business Connecter for Ax2009. Calling

Page 1 of 1 (1 items)