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

[ Post a follow-up to this message ]

Hello Paula,

I'm not sure if this will help or not but here is the process that I would
recommend for copying a .NET AIC from one machine to another:

1. Copy primary interop assemblies Interop_MscsCore.dll,
Interop_PipeComplib.dll, and Interop_BTSComplib.dll from the source machine
to the Program Files\Microsoft.NET\Primary Interop Assemblies\ directory on
destination machine.

2. Register the Interop DLLs by running the following commands from the
Visual Studio.NET command prompt:

regasm "C:\Program Files\Microsoft.NET\Primary Interop
Assemblies\Interop_PipeComplib.dll"

-and-

regasm "C:\Program Files\Microsoft.NET\Primary Interop
Assemblies\Interop_MscsCore.dll"

-and-

regasm "C:\Program Files\Microsoft.NET\Primary Interop
Assemblies\Interop_BTSComplib.dll"

3. Load the Interop DLLs into the Global Assembly Cache (GAC) by running
the following commands from the Visual Studio .NET command prompt:

gacutil /i Interop_MscsCore.dll

-and-

gacutil /i Interop_PipeComplib.dll

-and-

gacutil /i Interop_BTSComplib.dl

4. Copy over the .NET AIC dll from the source machine to a folder on the
destination machine.

5. Register the .NET AIC dll by running the following command from the
Visual Studio.NET command prompt:

regasm "C:\<folder where .NET AIC dll is located>\<name of .NET dll>

6. Load the .NET AIC dll into the GAC by running the following command from
the Visual Studio .NET command prompt:

gacutil /i <name of .NET dll>

7. If the .NET AIC is a pipeline AIC then the supporting ASP pages must be
copied from the Program Files\Microsoft BizTalk
Server\MessagingManager\pipeline\ directory on the source server to the
Program Files\Microsoft BizTalk Server\MessagingManager\pipeline\ directory
on the destination server.

If this process is not followed then you may have difficulties
instantiating the AIC on the destination machine(s) (machines that the AIC
was not originally compiled on).

Regards,

Trace

--------------------
| 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
|
|

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]