Feb 10
There was a failure executing the receive pipeline… failed to load. Verify the schema for this do...
Recently after installing a new version of one BizTalk Application, in order to provide a new service and after having validated all the normal steps of
Sep 5
BizTalk Server 2010 – List of Known Issues and Solutions (Part 1)
The following are the known issues in BizTalk Server 2010: Known Issues with Orchestration Issue: When redeploying an existing Orchestration solution,
May 8
BizTalk – How to debug Custom Pipeline Components running on Isolated Host
Normally we can debug almost all pipeline components in run-time mode by attaching Visual Studio to “BTSNTSvcexe” process (see: Debugging External
Jan 18
BizTalk Pipeline component – Unable to copy file “…\Pipeline Components\MyPipelineCom...
When building BizTalk Project it gives the following error: Unable to copy file "…\Pipeline Components\MyPipelineComponentdll" to "bin\Debug\
Oct 10
BizTalk Pipeline component – cannot copy “custom pipeline component” as the ear...
This problem occurs many times when we are trying to deploy pipeline components (copy the DLL to the folder: “C:\Program Files\Microsoft BizTalk Server
Oct 10
BizTalk Pipeline Component problem – Component ‘…’ could not be initialized. Pi...
Some days ago I was trying to make some changes in a pipeline component that was deployed earlier and when I tried to test the component he originated the
Oct 8
There was a failure executing the send pipeline: “Please ensure that exsmime.dll has been r...
For no reason, one of my BizTalk 2006 R2 Lab environment begin to appear the following error: “message sent to adapter "FILE" on send port
Aug 23
BAM API – Using MessagingEventStream to write BAM Events from pipeline components
MessagingEventStream (MES) is used inside a BizTalk pipeline component to write Bam as part of the messaging transactions ensuring that your BAM event
Jul 29
BizTalk Pipeline Component – The specified module could not be found. (Exception from HRESU...
Recently I tried to install an old BizTalk pipeline component project into a new environment, but it failed, giving the following error: “The
Apr 8
Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name i...
While trying to debug custom pipeline component using “Pipelineexe” utility, I keep getting the following error message: Pipeline file name is already
