using WCF adapter with WCF-SQL adapter


hi all,

i have implemented scenario wcf adapter bidirectional when message receive sends bidirectional adapter wcf-sql adapter , poll information database , again in response wcf send information user created orchestration this

 

 

 

which port1 wcf category , second 1 wcf-sql purpose of creating use add generated item , add meta data fits wcf-sql adapter , wcf adapter expose orchestration wcf service using wizard after test in .net application use wcf service crashes , when check event viewer see error :

 

there failure executing receive pipeline: "microsoft.biztalk.defaultpipelines.xmlreceive, microsoft.biztalk.defaultpipelines, version=3.0.1.0, culture=neutral, publickeytoken=31bf3856ad364e35" source: "xml disassembler" receive port: "wcfreceiveport_fff/wcfservice_fff" uri: "/fff/wcfservice_fff.svc" reason: cannot locate document specification because multiple schemas matched message type "http://schemas.microsoft.com/sql/2008/05/tableop/dbo/sabtahval#select".

 

can body me possible?

hi jalal,

it appears deployed multiple schema's match message, verify how many schema's have performing following query:

select msgtype, assemblyid, clr_namespace, clr_assemblyname
bt_documentspec
msgtype = ‘your messagetype'

messagetype targetnamespace#rootelement message, reference see use ful post abdul.

hth

regards,

steef-jan wiggers
mvp & mcts biztalk server 2010
http://soa-thoughts.blogspot.com/
if answers question please mark accordingly

biztalk


BizTalk Server  >  BizTalk Server General



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