May 2010 Blog Posts


Had a problem recently with the JDE Adapter (OneWorld) where the devenv send port worked for design time discovery but wouldn’t work at runtime.

Here is the error message (for all that google index goodness)

The Messaging Engine failed to create the transport adapter "JDEAdapter".

OutboundAssemblyPath: "NULL"

OutboundTypeName: "Microsoft.BizTalk.Adapters.JDEOneWorldTransmitter, Microsoft.BizTalk.Adapters.CoreTransmitter, Version=1.0.5025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

Exception Details: "Could not load file or assembly 'Microsoft.BizTalk.Adapters.CoreTransmitter, Version=1.0.5025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

The resolution was to switch the BizTalk host from 64bit to 32bit.

A good example of a time when I wish BizTalk would have better error messages.



Here’s something that is going to keep everyone wondering about the future for a while.

“Company officials have said Microsoft also is working on a new “major” version of BizTalk, which it is calling BizTalk Server vNext. This release will be built on top of Microsoft’s Windows AppFabric platform. So far, the Softies have not provided a release target for BizTalk Server vNext.”