Xml disassembler failing with reason start element does not match end element


hi,

i'am using wcf-wshttp adapter send simple message wcf service biztalk. service can return response or throw businessfault or systemfault.

i responses , faults returned , captured part of time . 1 in hundred message fails below error when businessfault or systemfault thrown . soap faults

there failure executing response(receive) pipeline: "microsoft.biztalk.defaultpipelines.xmlreceive, microsoft.biztalk.defaultpipelines, version=3.0.1.0, culture=neutral, publickeytoken=31bf3856ad364e35" source: "xml disassembler" send port: "xy.integration.customapplication.customservice" uri: "https://xyz.xyz.co.xy/customservice/customservice.svc" reason: start element 'nz/faults/201' not match end element 'reason'. line 1, position 677.

i use below xpath inbound biztalk message body

/*[local-name()='fault']/*[local-name()='detail' or local-name()='detail']/* | /*[not(local-name()='fault')]

my node encoding xml.

i have enabled service trace on biztalk server capture incoming message , noticed messages not broken .

beleive 1 of item microsoft has fixed biztalk 2009 in cu 1. couldnt notice similar 1 biztalk 2010 http://support2.microsoft.com/kb/981422

any tips appreciated.

thanks

suresh

use passthrureceive pipeline instead of xmlreceive pipeline.

examine output adapter, , verify output in fact valid xml.

morten la cour



BizTalk Server  >  BizTalk Server Adapters and Adapter Pack



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more