Hi Eric -
Thanks for your reply. Yes, the error happens when the HIPAA subsytem is
processing inbound EDI (raw to XML) for handoff to the BizTalk messaging
framework. In our environment, I have a BT Host (HIPAA HOST) set for that
machine. All receive and send ****ts that use the HIPAA trans****t run on
that
host and that machine. All file & other messaging activity run on other
machines in our environment. I did notice that the HIPAA subsystem tuning
was
set for 20 worker threads and 30 connections in the DB pool. Not sure if
that's a low setting, but I guess it would depend on the physical machines
available resources as well as other SQL dependencies and competing
clients.
I will look up the servers resources and post back a listing of setup and
an
inventory of major services running as well.
Any other ideas for tuning or reducing this error?
Thanks again -
--
Dameon
"Eric Stott" wrote:
> The error is happening between steps 2 and 3 I would assume.
> What else is going on on the box at that time?
>
> Eric
> http://blog.biztalk-info.com
>
> "Dameon" <Dameon@[EMAIL PROTECTED]
> wrote in message
> news:3B6D82FA-49FA-4544-8158-C96104A748AB@[EMAIL PROTECTED]
> > Very often I receive this error in my HIPAA Accelerator environment.
> > Eventually the message gets translated and accepted, but sometimes it
will
> > go
> > through 20 to 30 of the below message. This makes for a very slow
HIPAA
> > processing environment and seems to be the bottleneck of my process
flow
> > right now. My process is this:
> >
> > 1. Receive source HIPAA EDI
> > 2. EDI goes through HIPAA 3.0 Accelerator
> > 3. Receive ****t is assigned to SenderID - receives msg
> > 4. Msg routed to Send****t and Translated to flat file.
> >
> > My environment is: BT2004 Enterprise SP1, HIPAA 3.0, Clustered SQL
Server,
> > Win 2003.
> >
> > Error MSg:
> >
> > COM_SendMessage(): Cant make a connection to BizTalk for do***ent
> > #XXXXXXX.
> > Errorcode is -2074 ()Host=[localhost], Service=[(null)],
Protocol=[tcp],
> > ****t=[11021]
> > System message: (10061) No connection could be made because the target
> > machine activelyrefused it.
> >
> > (XXXXXX being whatever do***ent is getting hung up here)
> >
> > Any suggestions for getting past this, making my system more
efficient,
> > tuning the HIPAA accelerator, etc?
> >
> > Thanks!!
> > --
> > Dameon
>
>
>
|
