|
Home > Archive > BizTalk Server > February 2004 > Clustered Servers; AIC Registration
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 |
Clustered Servers; AIC Registration
|
|
| Paula DiTallo 2004-02-08, 8:39 am |
| Hello Techies--
Maybe one of you has seen this problem. Here's the short version.
I have a primary and secondary set of Clustered BizTalk Servers. On
the primary server, I have a message port with a homegrown AIC as its
method of transport. I've registered the AIC [via regsvcs (COM+) and
under the gacutil (Assembly)] on both boxes. They look exactly the
same. [same app id, same versions, same paths] . I have 2 receive
functions--one coming from the primary box, one coming fron the
secondary box both polling for incoming docs. The primary works
without a glitch. The secondary box fails with the
CIS_E_XMITFAILED_W_DETAILS as "The server encountered a transport
error while processing the message port "%1", which has a transport
component with a Prog ID of "%2".
Any clues on what's going on? Is it a configuration thing? Is it a
DLL registration thing? BTW, I tried setting up two message ports--
one connected to the AIC (same name) on each machine, another set of
channels, the whole bit--but the same results.
Yikes! I'm not doing something right! All clues, flames, torches,
theories, etc. will be warmly received!;-)
Thanks,
Paula DiTallo plditallo@m...
www.metro-design-dev.com
Sent via http://www.biztalkug.com
everything about BizTalk Server
| |
| Sameer.Surve@ilg.com 2004-02-08, 8:39 am |
| I have seen this specific error when a COM component is not registered
or the current compiled version is not the same one that was orginally
registered (with VS.NET).
This occurs quite frequently on my dev box when I try to access a
newer release of the component which is not the same one which was
registered.
This error goes away after un-registrying and registring the component
again.
With this background, I think your AIC is either not registered
properly or has a different GUID.
You can verify with by searching the registry and ensuring your GUID's
match.
Hope this helps.
Paula DiTallo <plditallo@metro-design-dev.com> wrote in message news:<Dtyaz1DJ1Q@biztalkug.com>...
> Hello Techies--
>
> Maybe one of you has seen this problem. Here's the short version.
> I have a primary and secondary set of Clustered BizTalk Servers. On
> the primary server, I have a message port with a homegrown AIC as its
> method of transport. I've registered the AIC [via regsvcs (COM+) and
> under the gacutil (Assembly)] on both boxes. They look exactly the
> same. [same app id, same versions, same paths] . I have 2 receive
> functions--one coming from the primary box, one coming fron the
> secondary box both polling for incoming docs. The primary works
> without a glitch. The secondary box fails with the
> CIS_E_XMITFAILED_W_DETAILS as "The server encountered a transport
> error while processing the message port "%1", which has a transport
> component with a Prog ID of "%2".
>
> Any clues on what's going on? Is it a configuration thing? Is it a
> DLL registration thing? BTW, I tried setting up two message ports--
> one connected to the AIC (same name) on each machine, another set of
> channels, the whole bit--but the same results.
>
> Yikes! I'm not doing something right! All clues, flames, torches,
> theories, etc. will be warmly received!;-)
>
> Thanks,
> Paula DiTallo plditallo@m...
> www.metro-design-dev.com
>
>
> Sent via http://www.biztalkug.com
> everything about BizTalk Server
|
|
|
|
|