|
Home > Archive > BizTalk Server General > June 2005 > Help with error message
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Help with error message
|
|
| Rohan Sootarsing 2005-06-24, 7:50 am |
| Hi all I am getting the following error message and I was wondering if anyone
could shed some light on what might be causing it
Uncaught exception terminated service
Thanet.CouncilTax.Request.Orchestration_1(b2f1d68e-12a1-a58a-310e-eed31cb84d6b), instance 253092e7-1379-41bd-b3cf-9d6bf0731061
Received unexpected message type 'Thanet.CouncilTax.Request.Northgate,
Thanet.CouncilTax.Request, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=742c41c5e3ec5699' does not match expected type
'Thanet.CouncilTax.Request.Northgate, Thanet.CouncilTax.Request,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=fbd692175b2fd2f7'.
Exception type: UnexpectedMessageTypeException
Source: Microsoft.XLANGs.Engine
Target Site: Void _verifyPublisherSchema()
Help Link:
Additional error information:
Thanks
Rohan
| |
| Marvin Smit 2005-06-24, 7:50 am |
| Hi Rohan,
you seem to have 2 different versions of the
"Thanet.CouncilTax.Request" object you're dealing with.
The message type encountered:
"Received unexpected message type
'Thanet.CouncilTax.Request.Northgate, Thanet.CouncilTax.Request,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=742c41c5e3ec5699"
(Take a good look at the PublicKeyToken value)
"does not match expected type 'Thanet.CouncilTax.Request.Northgate,
Thanet.CouncilTax.Request, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=fbd692175b2fd2f7'"
As you can see the namespaces & classnames are identical, but the
PublicKeyToken is not. This means that they are NOT considered to be
'the same'.
Seems like you changed your signing key somewhere down the line. The
current orchestration seems to be expecting the "previous version" of
the object mentioned, but it getting a "newer version".
Hope this helps,
Marvin Smit
On Fri, 24 Jun 2005 03:28:01 -0700, "Rohan Sootarsing"
<RohanSootarsing@discussions.microsoft.com> wrote:
>Hi all I am getting the following error message and I was wondering if anyone
>could shed some light on what might be causing it
>
>Uncaught exception terminated service
>Thanet.CouncilTax.Request.Orchestration_1(b2f1d68e-12a1-a58a-310e-eed31cb84d6b), instance 253092e7-1379-41bd-b3cf-9d6bf0731061
>
>Received unexpected message type 'Thanet.CouncilTax.Request.Northgate,
>Thanet.CouncilTax.Request, Version=1.0.0.0, Culture=neutral,
>PublicKeyToken=742c41c5e3ec5699' does not match expected type
>'Thanet.CouncilTax.Request.Northgate, Thanet.CouncilTax.Request,
>Version=1.0.0.0, Culture=neutral, PublicKeyToken=fbd692175b2fd2f7'.
>
>Exception type: UnexpectedMessageTypeException
>Source: Microsoft.XLANGs.Engine
>Target Site: Void _verifyPublisherSchema()
>Help Link:
>Additional error information:
>
>
>
>Thanks
>Rohan
| |
| Rohan Sootarsing 2005-06-24, 5:54 pm |
| Thanks for that any suggestions on fixing the problem
"Marvin Smit" wrote:
> Hi Rohan,
>
> you seem to have 2 different versions of the
> "Thanet.CouncilTax.Request" object you're dealing with.
>
> The message type encountered:
>
> "Received unexpected message type
> 'Thanet.CouncilTax.Request.Northgate, Thanet.CouncilTax.Request,
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=742c41c5e3ec5699"
>
> (Take a good look at the PublicKeyToken value)
>
> "does not match expected type 'Thanet.CouncilTax.Request.Northgate,
> Thanet.CouncilTax.Request, Version=1.0.0.0, Culture=neutral,
> PublicKeyToken=fbd692175b2fd2f7'"
>
> As you can see the namespaces & classnames are identical, but the
> PublicKeyToken is not. This means that they are NOT considered to be
> 'the same'.
>
> Seems like you changed your signing key somewhere down the line. The
> current orchestration seems to be expecting the "previous version" of
> the object mentioned, but it getting a "newer version".
>
> Hope this helps,
>
> Marvin Smit
>
>
> On Fri, 24 Jun 2005 03:28:01 -0700, "Rohan Sootarsing"
> <RohanSootarsing@discussions.microsoft.com> wrote:
>
>
>
| |
| Marvin Smit 2005-06-24, 5:54 pm |
| Hi,
what you probably have to do is:
- Undeploy the orchestration/assembly
- Recompile (making sure the reference to the external object is set
to the latest one)
- Deploy again.
The issue being that the publickeytoken is a part of the fully
qualified name used by BizTalk. No other solution than to provide the
original object which was signed with that key or recompile with the
new version so the new keytoken will be included in the 'refreshed'
reference.
Hope this helps,
Marvin Smit
On Fri, 24 Jun 2005 07:09:04 -0700, "Rohan Sootarsing"
<RohanSootarsing@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for that any suggestions on fixing the problem
>
>
>"Marvin Smit" wrote:
>
| |
| Rohan Sootarsing 2005-06-24, 5:54 pm |
| Sorry prob being a bit stupid here the thing that is sending the message to
biztalk is a third party app do I have to reference that in biztalk somehow?
Or do I just redeploy everything one i have undeployed it
Thanks
"Marvin Smit" wrote:
> Hi,
>
> what you probably have to do is:
>
> - Undeploy the orchestration/assembly
> - Recompile (making sure the reference to the external object is set
> to the latest one)
> - Deploy again.
>
> The issue being that the publickeytoken is a part of the fully
> qualified name used by BizTalk. No other solution than to provide the
> original object which was signed with that key or recompile with the
> new version so the new keytoken will be included in the 'refreshed'
> reference.
>
> Hope this helps,
>
> Marvin Smit
>
>
> On Fri, 24 Jun 2005 07:09:04 -0700, "Rohan Sootarsing"
> <RohanSootarsing@discussions.microsoft.com> wrote:
>
>
>
| |
| Marvin Smit 2005-06-24, 5:54 pm |
| Hi Rohan,
I assume there is an orchestration in your environment that uses an
external .Net class. The messages do not change for this. The only
thing we have to do is 'refresh' the reference to that external object
from the orchestration. To do this you will have to recompile the
orchestration (this will embed the fully qualified name of the
referenced assembly with the external object).
Then we can deploy again. Since the only thing changed is the
assembly-reference from the orchestration to the external objewct, all
messages will still be the same and should work correctly.
(Unless the external object call creates new messages in another
format now).
Hope this helps,
Marvin Smit
On Fri, 24 Jun 2005 07:41:06 -0700, "Rohan Sootarsing"
<RohanSootarsing@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry prob being a bit stupid here the thing that is sending the message to
>biztalk is a third party app do I have to reference that in biztalk somehow?
>
>Or do I just redeploy everything one i have undeployed it
>
>Thanks
>
>
>
>"Marvin Smit" wrote:
>
|
|
|
|
|