Morten Lehrmann - BizTalk Blog

A map to for a large schema cannot compileBizTalk

Posted by Morten Lehrmann 2017-03-14 14:45:55

Open the map in a text editor a change tag


to No

The SMTP Adapter needs helpBizTalk

Posted by Morten Lehrmann 2016-10-13 11:10:22

You just need to preserve the original file name in a mail - this guy has a simple pipeline to do this:

FTP Send port with XML Validator pipelineBizTalk

Posted by Morten Lehrmann 2016-10-10 12:52:06

Had a serious issue on our "old" BizTalk 2010 server. When sending a document to a FTP send port with a pipeline which does XML validation against a schema the below happened.

1. Sending a document which fails the XML validation.

2. The document fails correctly (although the error message is strange):

A message sent to adapter "FTP" on send port "XXX" with URI "XXX'" is suspended.  Error details: An unexpected failure occurred when processing a message. The text associated with the exception is "Attempted to read or write protected memory. This is often an indication that other memory is corrupt.".  

Error details: The data send failed unexpectedly. Inner Exception details: "XXX".

3. Then the host instance running the FTP send port fails:

The BizTalk Service BizTalk Group : XXX service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

4. And when this host instance restarts it now transmits the failed document! Also although there is tracking on the Send port it does not show that this document was transmitted.


Moreover, the above happened on the production server only. In the test system it failed correctly.


I tried:

1. Redeploying the application

2.Restarting the BizTalk server.

3.Repairing the BizTalk server installation.

4.Changing the pipeline in various ways.

Nothing helped.

The issue has therefore not been resolved - instead I did a work-around so the schema validation takes place on a FILE adapter (not FTP). That works.


A theory is that the issue stemps from a combination of the pipeline and the FTP file name which is something like:


Still that cannot explain why it works on the test-system.

Connecting Dynamics AX 2009 and IBM Mainframe via WebSphere MQBizTalk

Posted by Morten Lehrmann 2015-11-13 11:21:58

A really nice article on character encoding issues:

Verify the schema for this document specification is deployed and is in the Global Assembly Cache.BizTalk

Posted by Morten Lehrmann 2015-10-15 15:42:36

Got this error in an application:

There was a failure executing the receive pipeline:
Source: "Flat file disassembler" Receive Port: ... URI: ... Reason: The document specification ... from assembly
... failed to load.
Verify the schema for this document specification is deployed and is in the Global Assembly Cache.

Google gave a lot suggestions. Tried them - they did not work.
Ended up renaming the schema.
And after several deployment issues (some requirering restore of BizTalk databases) it ended up working.

BizTalk Server: List of Errors and Warnings, Causes, and SolutionsBizTalk

Posted by Morten Lehrmann 2014-07-15 15:22:53

Orchestration Types UndefinedBizTalk

Posted by Morten Lehrmann 2013-12-17 17:41:57

Developing a BizTalk application with several orchestrations. All of a sudden an orchestration which has not been edited does not compile because some of its types are undefined.

Checking many things to no avail. Lastly shelved all changes to Team Foundation Server. Fetched the last working version from Team Foundation Server, compiled it without errors. Unshelved the previous version which did not compile, compiled it - and now it compiled!

Not sure what happened - but problem was solved.

BizTalk Server 2010. Visual Studio 2010 Ultimate.

No subscribers were foundBizTalk

Posted by Morten Lehrmann 2013-11-15 11:32:40

Got this error:

xlang/s engine event log entry: An unrecoverable exception (see the 'inner exception' below) has occurred.
Service Name: ...Orchestrations....
Service Id: 7775e43e-2928-5821-8737-f631173baa4bInstance Id: 41996c13-9c48-4871-a3d9-9c69fc350faa
Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.ScheduleComplete(Boolean terminate)
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
at Microsoft.XLANGs.Core.ServiceContext.OnCommit()
at ....Orchestrations.....segment0(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:
A batch item failed persistence Item-ID 9b93ec04-a050-45f5-8ddd-fd935dbd34f3 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. .
Exception type: PersistenceItemException
Additional error information:
Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. with status -1061151998.
Exception type: PublishMessageException

developing a fairly complicated integration involving several orchestrations with complicated filtering.

However, it turned out to be the filtering on the last Send Port which, as it happens, contained a space infront of one of the filter expressions.
Does not love BizTalk on handling and displaying these filters!'