|
Home > Archive > BizTalk Server General > April 2006 > Biztalk only allows one adaptor conection at a time
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 |
Biztalk only allows one adaptor conection at a time
|
|
| M Stuart 2006-04-10, 7:34 pm |
| Hi all,
Came a cross a very strange situation in that I have two seperate assemblies
which both use the same custome adaptor on solicit receive response. When I
run both orchestrations together only one orchestration processes messdages
correctly and the messages from the other orchestration are just stacking up
in the HAT.
Whe I stop either one of the orchestrations and then restart the services
all is fine. When I then start both orchestrations then the first onoe to
initialise wins.
I ahve even tried splitting them out into using seperate Hosts but to no
avail.
Regards
Mike
| |
| Adrian Hamza [MSFT] 2006-04-18, 12:46 am |
| Any particular errors in the event log?
This reminds me of some similar error I've seen when the same process tried
to load both .Net Framework versions (1.1 and 2.0) in the same process,
which is not supported. For that reason, only one component worked, based
on whichever .Net Framework was loaded first.
There's not enough data to draw that conclusion though, can you look for
some errors in the event log.
This posting is provided "AS IS" with no warranties, and confers no rights.
Adrian Hamza [MSFT]
http://blogs.msdn.com/ahamza/
My blog on BizTalk 2006
Windows SharePoint Services adapter
--------------------[vbcol=seagreen]
assemblies[vbcol=seagreen]
I[vbcol=seagreen]
messdages[vbcol=seagreen]
up[vbcol=seagreen]
| |
| M Stuart 2006-04-18, 12:46 am |
| The Server has BizTalk 2004 SP1 but has not yet had the post SP1 hotfixes. I
think this may be root of the problems.
Regards
Mike
"Adrian Hamza [MSFT]" wrote:
> Any particular errors in the event log?
> This reminds me of some similar error I've seen when the same process tried
> to load both .Net Framework versions (1.1 and 2.0) in the same process,
> which is not supported. For that reason, only one component worked, based
> on whichever .Net Framework was loaded first.
>
> There's not enough data to draw that conclusion though, can you look for
> some errors in the event log.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Adrian Hamza [MSFT]
> http://blogs.msdn.com/ahamza/
> My blog on BizTalk 2006
> Windows SharePoint Services adapter
>
> --------------------
> assemblies
> I
> messdages
> up
>
>
|
|
|
|
|