Hi

What does that error means ?

 

 

Microsoft.XLANGs.Core.UnexpectedMessageTypeException: Received unexpected me
ssage type '' does not match expected type 'http://xxx.schemas.xxxxxxx.com/#
Response'.


at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope e
nv, Int32 operationId, Context ctx)


at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelo
pe& env, Boolean topOnly)


at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Se
gment currentSegment, Context cxt, Envelope& env, CachedObject location)


at xxxxxxx.xxx.BizTalkServices.Orchestrations.ClientProfile.ReceiveClientPro
file.segment2(StopConditions stopOn)


at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditi
ons stopCond, Exception& exp)

Microsoft.XLANGs.Core.UnexpectedMessageTypeException

Scoped@

ReceiveClientProfile.??__scope0

ReceiveClientProfile.ReceiveClientProfile

fa8207d8-3d31-41b3-a19b-8ef1ec216156

[ Post a follow-up to this message ]

I received the same error couple of days ago. There were two problems - the
first was that an adapter was submitting a solicit response with different
schema then expected, the second problem was that I was not encoding the
response properly.

Try both in your case.

Best regards,
Vladimir

"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message
news:#U5arpLTEHA.2988@TK2MSFTNGP09.phx.gbl...
Hi

What does that error means ?





Microsoft.XLANGs.Core.UnexpectedMessageTypeException: Received unexpected
message type '' does not match expected type
'http://xxx.schemas.xxxxxxx.com/#Response'.


at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env,
Int32 operationId, Context ctx)


at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx,
Envelope& env, Boolean topOnly)


at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription,
Segment currentSegment, Context cxt, Envelope& env, CachedObject location)


at
xxxxxxx.xxx.BizTalkServices.Orchestrations.ClientProfile.ReceiveClientProfil
e.segment2(StopConditions stopOn)


at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
StopConditions stopCond, Exception& exp)

Microsoft.XLANGs.Core.UnexpectedMessageTypeException

Scoped@

ReceiveClientProfile.??__scope0

ReceiveClientProfile.ReceiveClientProfile

fa8207d8-3d31-41b3-a19b-8ef1ec216156

[ Post a follow-up to this message ]

Thank you for the help, I already spent a lot of time trying to get this
bloody adapter to work, it just not giving back what is wrong with it, I
tried it with everything that I could try it with :-(



Now it is time to use an important windows feature, the drag and drop, drag
the adapter, and drop it in the recycle bin, where it meant to be.



I switch to custom components, they do work, easy to debug, and when
something is wrong with them, they will trigger the proper error message.





"Vladimir Tchalkov" <vlado@act-soft.nspam.com> wrote in message
news:%23gZ4eaSTEHA.3844@TK2MSFTNGP11.phx.gbl...
> I received the same error couple of days ago. There were two problems -
the
> first was that an adapter was submitting a solicit response with different
> schema then expected, the second problem was that I was not encoding the
> response properly.
>
> Try both in your case.
>
> Best regards,
> Vladimir
>
> "G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message
> news:#U5arpLTEHA.2988@TK2MSFTNGP09.phx.gbl...
> Hi
>
> What does that error means ?
>
>
>
>
>
> Microsoft.XLANGs.Core.UnexpectedMessageTypeException: Received unexpected
> message type '' does not match expected type
> 'http://xxx.schemas.xxxxxxx.com/#Response'.
>
>
>    at
> Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope
env,
> Int32 operationId, Context ctx)
>
>
>    at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx,
> Envelope& env, Boolean topOnly)
>
>
>    at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription
subscription,
> Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
>
>
>    at
>
xxxxxxx.xxx.BizTalkServices.Orchestrations.ClientProfile.ReceiveClientProfil
> e.segment2(StopConditions stopOn)
>
>
>    at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
> StopConditions stopCond, Exception& exp)
>
> Microsoft.XLANGs.Core.UnexpectedMessageTypeException
>
> Scoped@
>
> ReceiveClientProfile.??__scope0
>
> ReceiveClientProfile.ReceiveClientProfile
>
> fa8207d8-3d31-41b3-a19b-8ef1ec216156
>
>

[ Post a follow-up to this message ]

While I understand you have moved on with development work, as a side note,
what was most likely happening was that you were using a passthru pipeline
in the response portion of your solicit response port. When you use a
passthru pipeline we do not inspect the data and so do not determine the
message type. Orchestration, however, requires typed messages and so when
it gets this untyped message it is throwing an exception indicating that
the type "" (null value) is not what it expected. To fix this, probably all
you had to do was switch the pipeline used in the response portion of your
solicit response port to use an xml pipeline.

HTH and sorry we did not get you the help in a timely fashion.
Lee

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------[vbcol=seagreen] 
<#gZ4eaSTEHA.3844@TK2MSFTNGP11.phx.gbl>[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
.phx.gbl[vbcol=seagreen] 
drag[vbcol=seagreen] 
different[vbcol=seagreen] 
unexpected[vbcol=seagreen] 
location)[vbcol=seagreen] 
il[vbcol=seagreen] 

[ Post a follow-up to this message ]

From curiosity, I created a very simple test project today to try to change
the receive pipeline to xml, the adapter is connected to the database
request/response, the request is storing the data to the database, the
response is failing as before, here are the error messages:



With the pass-through pipeline:



Microsoft.XLANGs.Core.UnexpectedMessageTypeException: Received unexpected
message type '' does not match expected type
'http://updatagrams.xxx.xxxxx.com/attachments/#Response'.

at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env,
Int32 operationId, Context ctx)

at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx,
Envelope& env, Boolean topOnly)

at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription,
Segment currentSegment, Context cxt, Envelope& env, CachedObject location)

at
TDSecurities.Cairo2.Orchestrations.TermSheet.Processing.segment1(StopConditi
ons stopOn)

at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
StopConditions stopCond, Exception& exp)
Microsoft.XLANGs.Core.UnexpectedMessageTypeException
Scoped@
Processing.Processing
SubmitTermSheet.SubmitTermSheet
2dcd74e4-e549-4f5a-a4a0-78f3244bdcbd






With the xml pipeline:



Microsoft.XLANGs.Core.XlangSoapException: An error occurred while processing
the message, refer to the details section for more information


at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env,
Int32 operationId, Context ctx)


at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx,
Envelope& env, Boolean topOnly)


at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription,
Segment currentSegment, Context cxt, Envelope& env, CachedObject location)


at
TDSecurities.Cairo2.Orchestrations.TermSheet.Processing.segment1(StopConditi
ons stopOn)


at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
StopConditions stopCond, Exception& exp)

Microsoft.XLANGs.Core.XlangSoapException

Scoped@

Processing.Processing

SubmitTermSheet.SubmitTermSheet

2dcd74e4-e549-4f5a-a4a0-78f3244bdcbd





"Lee Graber [MSFT]" <leegr@microsoft.com> wrote in message
news:5%23EgHnNVEHA.2436@cpmsftngxa10.phx.gbl...
> While I understand you have moved on with development work, as a side
note,
> what was most likely happening was that you were using a passthru pipeline
> in the response portion of your solicit response port. When you use a
> passthru pipeline we do not inspect the data and so do not determine the
> message type. Orchestration, however, requires typed messages and so when
> it gets this untyped message it is throwing an exception indicating that
> the type "" (null value) is not what it expected. To fix this, probably
all
> you had to do was switch the pipeline used in the response portion of your
> solicit response port to use an xml pipeline.
>
> HTH and sorry we did not get you the help in a timely fashion.
> Lee
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team
> -------------------- 
> <#gZ4eaSTEHA.3844@TK2MSFTNGP11.phx.gbl> 
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
> phx.gbl 
> drag 
message.[vbcol=seagreen] 
problems -[vbcol=seagreen] 
> different 
the[vbcol=seagreen] 
> unexpected 
Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase. VerifyTransport(Envelope[vbcol=seagreen]
 
ctx,[vbcol=seagreen] 
> location) 
> 
> il 
>

[ Post a follow-up to this message ]

Did your transport actually succeed in sending the message. You got a SOAP
error which is either caused by the fact that your transport is making a
web service call which is retruning a soap exception which is then causing
the orchestration to fail, or your transport simply did not succeed and so
we internally generate a failure message for the orchestration engine to
consume. If you transport is failing, you should get other errors in the
event log. If it is simply a SOAP exception, you should be able to use HAT
and look at the contents of the SOAP exception message to see why your web
service threw an exception.

HTH
Lee

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------[vbcol=seagreen] 
<#gZ4eaSTEHA.3844@TK2MSFTNGP11.phx.gbl>
<#3Wi2iVTEHA.2944@tk2msftngp13.phx.gbl>
<5#EgHnNVEHA.2436@cpmsftngxa10.phx.gbl>[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09
.phx.gbl[vbcol=seagreen] 
change[vbcol=seagreen] 
env,[vbcol=seagreen] 
subscription,[vbcol=seagreen] 
ti[vbcol=seagreen] 
processing[vbcol=seagreen] 
env,[vbcol=seagreen] 
subscription,[vbcol=seagreen] 
ti[vbcol=seagreen] 
pipeline[vbcol=seagreen] 
when[vbcol=seagreen] 
your[vbcol=seagreen] 
13[vbcol=seagreen] 
this[vbcol=seagreen] 
it, I[vbcol=seagreen] 
of[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hey Guys,
Thanks for the solution.
I was pestered with this problem throughout the day.
This post helped me solve it in seconds !

Basically I was getting the same error with my socket adapter.

Microsoft.XLANGs.Core.UnexpectedMessageTypeException: Received
unexpected message type '' does not match expected type

And I was using the Passthru pipeline for my receive.
Was able to get it working with the Default Xml one






Lee Graber [MSFT] wrote:
> Did your transport actually succeed in sending the message. You got a
SOAP
> error which is either caused by the fact that your transport is
making a
> web service call which is retruning a soap exception which is then
causing
> the orchestration to fail, or your transport simply did not succeed
and so
> we internally generate a failure message for the orchestration engine
to
> consume. If you transport is failing, you should get other errors in
the
> event log. If it is simply a SOAP exception, you should be able to
use HAT
> and look at the contents of the SOAP exception message to see why
your web
> service threw an exception.
>
> HTH
> Lee
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team
> -------------------- 
> <#gZ4eaSTEHA.3844@TK2MSFTNGP11.phx.gbl>
> <#3Wi2iVTEHA.2944@tk2msftngp13.phx.gbl>
> <5#EgHnNVEHA.2436@cpmsftngxa10.phx.gbl> 
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09[vbcol=seagreen]
> .phx.gbl 
microsoft.public.biztalk.orchestration:6683[vbcol=seagreen] 
to[vbcol=seagreen]
> change 
database[vbcol=seagreen] 
the[vbcol=seagreen] 
unexpected[vbcol=seagreen] 
> 
[vbcol=seagreen]
> env, 
ctx,[vbcol=seagreen] 
> subscription, 
location)[vbcol=seagreen] 
> 
> ti 
> processing 
> 
[vbcol=seagreen]
> env, 
ctx,[vbcol=seagreen] 
> subscription, 
location)[vbcol=seagreen] 
> 
> ti 
side[vbcol=seagreen] 
[vbcol=seagreen]
> pipeline 
use a[vbcol=seagreen] 
determine the[vbcol=seagreen] 
so[vbcol=seagreen]
> when 
indicating that[vbcol=seagreen] 
probably[vbcol=seagreen] 
portion of[vbcol=seagreen]
> your 
no[vbcol=seagreen] 
> 
> 13 
microsoft.public.biztalk.orchestration:6429[vbcol=seagreen] 
get[vbcol=seagreen]
> this 
with[vbcol=seagreen]
> it, I 
and drop,[vbcol=seagreen] 
be.[vbcol=seagreen] 
when[vbcol=seagreen] 
error[vbcol=seagreen] 
with[vbcol=seagreen] 
encoding[vbcol=seagreen] 
message[vbcol=seagreen] 
Received[vbcol=seagreen] 
> 
Context[vbcol=seagreen] 
Microsoft.XLANGs.Core.PortBase. GetMessageId(Subscription[vbcol=seagreen
] 
CachedObject[vbcol=seagreen] 
> 
> of 
Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,[vbcol=seagreen] 

[ Post a follow-up to this message ]