The adapter Microsoft Dynamics AX 2009 raised an error message: "The message does not contain a body part."

I experienced this error when trying to update a data synchronously with AIF. This same error also happens with delete service.

For now, Rasmus Jaeger said that the workaround is:

A simple check, in the AIF update and delete services in AX, which checks if the message part is empty. If the message part is empty, AX returns a predefined static xml document to BizTalk. 

So, we are waiting for the hot fix ............

Note to Self: Invoking Static Members of a Class in BRE

To invoke static members of a class, StaticSupport must be added in the registry:

• For 32 bit, the location is in:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BusinessRules\3.0\StaticSupport
• For 64 bit, the location is in:
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BusinessRules\3.0\StaticSupport

The Messaging Engine encountered an error during the processing of one or more inbound messages

I experienced this error when a receive port disassembles a flat file in 2 cases: 

• A 1 MB flat file contains more than 10000 rows
  The work around that I did is by throttling the Threads per CPU to 100.
• A 30 MB flat file contains more than 300000 rows
  I noticed that the Memory used by the receive host has grown up more than 3 GB. The receive host is a 32-bit only host. Thus, it recycles the host. So, by using 64-bit host and also throttling the Threads per CPU, the flat file was processed successfully. The 64-bit receive host consumed more than 6 GB of memory.