Unsupported Trxid (101) ACK

[Don Anderson]

I’m getting intermitent ACKs (1 in 1500 transactions) that end up in the error db with a Unsupported Trxid (101)description. Mssage looks good and matches whats in SMAT, driving me nuts

from error db

‘MSH|^~&|OMNICELL|GALVESTON|HNAM|D_PROD|20100908072230||ACK|Q37618427T47801859X6|P|2.3x0d

MSA|AA|Q37618427T47801859X6x0d’

SMAT

MSH|^~&|OMNICELL|GALVESTON|HNAM|D_PROD|20100908072230||ACK|Q37618427T47801859X6|P|2.3 MSA|AA|Q37618427T47801859X6

Example that didn’t error

MSH|^~&|Omnicell|GREENVILLE|HNAM|D_PROD|20100908072806||ACK|Q37618457T47801904X6|P|2.3 MSA|AA|Q37618457T47801904X6

Send OK Proc = save_ob_msg

TPS Inbound Reply = validate_hl7 ACK

Reply Generation = resend_ob_msg

Topic

[Jim Kosloskey]

Don,

Sounds to me like some of the replies are not getting killed. Normally the replies are killed and thus should never try to be routed (thus never get an Unsupported TrxID error).

I would start by checking the validating proc and make sure there are no situations under which it will not KILL the reply.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[James Cobane]

Don,

I suspect that for some reason intermittently you are not receiving ACKs within the specified timeout period and are then resending the message.  At some point the first ACK comes back, which then trips the ‘Await Replies’ flag to turn-off, and then the second ACK comes back when the engine isn’t expecting the reply.  Thus, the engine thinks this is inbound data.  If you don’t have routes defined, it will treat it as an error condition.  Do you have the ‘Outbound Only’ option checked on the Inbound configuration tab of that thread?  If not, check the box; this will tell the engine that if something comes in on the thread when it’s not expecting a reply, just ignore it.  

Hope this helps.

Jim Cobane

Henry Ford Health

[Don Anderson]

I didn’t have the Outbound only checked but I do now, Thankyou

[Author]

Replies