We have a strange problem with BizTalk input queue. Our application sends
events on different times to BizTalk but occasionally BizTalk process some
of these events twice. We checked BizTalk input queue and we found some
events twice at the exactly same time in input queue. Although we are sure
that our application sent them only once for some reason BizTalk receives
them twice. We use BizTalk Server Interchange Application for doing an
asynchronous submit (we use Interchange.Submit method).
Any advice is welcomed.

[ Post a follow-up to this message ]

I assume "events" means "messages", right?
What BizTalk are you using, BizTalk 02 or BizTalk 04? Also, queue indicates
that the transport is either MSMQ or MQ SEries, right? Which one?
It's hard to tel anything without this information,
Regards, Eldar

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

EBusiness Server Team
--------------------[vbcol=seagreen] 
some[vbcol=seagreen] 
sure[vbcol=seagreen] 

[ Post a follow-up to this message ]

Eldar thanks for you Reply.

BizTalk 2002

events=messages

We use BizTalk Server Interchange Application for doing an 
that means that the client computer is calling the biztalk server using
BizTalk.Interchange COM component.

queue doesn't mean MSMQ or MQ Series. We spotted the duplicate messages in
InterchangeDTA database, tables dta_interchange_details and
dta_interchange_data, where BizTalk stores all its messsages.



"Eldar Musayev (MSFT)" <Eldar_Musayev@online.microsoft.com> wrote in message
news:sY0h%23JEaEHA.2688@cpmsftngxa06.phx.gbl...[vbcol=seagreen]
> I assume "events" means "messages", right?
> What BizTalk are you using, BizTalk 02 or BizTalk 04? Also, queue
indicates
> that the transport is either MSMQ or MQ SEries, right? Which one?
> It's hard to tel anything without this information,
> Regards, Eldar
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team
> -------------------- 
sends[vbcol=seagreen] 
> some 
> sure 
receives[vbcol=seagreen] 
>

[ Post a follow-up to this message ]

That's tough, I did not worked with it. From what you describe, the problem
is likely to be in the code calling the API for this COM component, unless
some exotic configuration is involved. If you have a preprocessor - it's
unlikely to result in such an effect because these APIs and code are widely
used/tested.
Hope somebody else seen that before and can help,
--Eldar


This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
--------------------[vbcol=seagreen] 
<sY0h#JEaEHA.2688@cpmsftngxa06.phx.gbl>[vbcol=seagreen] 
in[vbcol=seagreen] 
message[vbcol=seagreen] 
process[vbcol=seagreen] 
some[vbcol=seagreen] 
are[vbcol=seagreen] 
an[vbcol=seagreen] 

[ Post a follow-up to this message ]