BAM removes XML declaration using passthru pipelines

I just created a simple messaging solution, using passthru pipeline on both send and receive ports. When I deployed this simple solution everything worked fine. However when I added BAM to the solution, tracking receive and sent time on the ports, the BAM interceptor removed the XML declaration in the beginning of the file.

I have not yet found a workaround for this problem, but a solution is to NOT use BAM.

UPDATE: Microsoft have acknowledged this. They will not provide a fix fort it.

Comments

Post a Comment

Popular posts from this blog

Illegal 'activate' predecate

Image
I am creating a orch that has filter on the initial receive shape. When building I got these error: Error 1 : identifier 'MySolutionname' does not exist in 'MyOrchName'; are you missing an assembly reference? Error 2: cannot find symbol 'MySolutionname' Error 3: an 'activate' predicate rvalue must be a string, character, boolean or numeric literal Error 4 : illegal 'activate' predicate The solution to this is to put the filter expression in sting literals (i.e. “double quotes”)
Read more

BizTalk Host "Stop Pending"

When restarting a BizTalk host I experiences that it would not restart. The service was stuck in a "Stop Pending" state. It seem that the only way to get the host back up, is to terminate the process and the start it. When i tried to restart fro BizTalk Administration Console nothing happen. I had to user the End Task function in Task Manager To get the correct instance i needed to find the correct instance. The only way to be sure to get the right one is to find the Process ID (PID) This might be found by using the command prompt using tasklist /SVC /fi "imagename eq btsntsvc.exe" This will list all BizTalk hosts like this Image Name              PID  Services ============= ================================ BTSNTSvc.exe            2376 BTSSvc$Rcv_x32_1_FTP_H BTSNTSvc.exe            2396 BTSSv...
Read more

The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process

Image
When deploying a wcf service to biztalk the is a good chance you will run into: The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process" Solution When installting a SOAPm HTTP or WCF service on the same WebServer then seperate app pools must be created for each adapter. Using seperat app pools will solve the issue. Note the this is only a problem om win servers as desktop version of windows does not have an app pool concept.
Read more