Question on Error Log

[Jon Melin]

I have a couple questions regarding an error I am seeing in my error log. Every now and again I have an A08 fail in one of my routes and I am not able to find the issue. This doesn’t happen on the vast majority of A08 messages just one every now and again. I am also not able to pinpoint the difference between a message that works and a message that doesn’t because there aren’t noticeable variances. Also when I go grab the message from the SMAT file and run it through the xlate (it is running through in the route) it works just fine – no errors. Just wondering if anyone has a quick idea.

Thank you in advance.

Here is my error log:

msg: 0x0xb731103c

   msgType           : DATA

   msgClass          : PROTOCOL

   msgState          : Tcl failure in IB data TPS (201)

   msgPriority       : 5120

   msgRecoveryDbState: Log:update (3)

   msgFlags          : 0x8006

   msgSrcMidGroup    : midNULL

  msgDriverControl  : {CONNID 0} {IPVERSION 4}

   msgRecordFormat   :

   msgRoutes         :

   msgUserData       : Application Error (AE) – APPLICATION ERROR WHILE PROCESSING MESSAGE

   msgStaticIsDirty  : 0

   msgVariableIsDirty: 0

   msgTimeStartIb    : 1376406514.107(Tue Aug 13 10:08:34 2013)

   msgTimeStartOb    : 1376406514.132(Tue Aug 13 10:08:34 2013)

   msgTimeCurQueStart: 0.000(Wed Dec 31 18:00:00 1969)

   msgTimeTotalQue   : 1.990

   msgTimeRecovery   : 1376406517.624(Tue Aug 13 10:08:37 2013)

   msgEoConfig       : 0x(nil)

   msgData (BO)      : 0x0xb7311124

TPS ERROR disposition

Previous recovery db state is 14.

Topic

[Levy Lazarre]

Jon,

The message was in recovery state 14, indicating a successful delivery to the receiving system. It appears that the receiving application had a problem processing the message and therefore returned a negative acknowledgment to you (AE = Application error). This is reported as msgState 201 (Failure in IB Data TPS eval).

I suggest you save the ACKs from that system. Sometimes there is more information in the MSA segment to indicate the cause of the failure. It could be as simple as a required field missing in the A08 message or some other internal receiving application problem.

I hope this helps.

[Jon Melin]

Yes. That helps. I thought it had something to do with their end but I wasn’t seeing anything in the logs that would explain the error. I will notify them and see what they can tell me.

Thank you,

Jon

[Brandon Grudt]

A lot of times a 201 error is the effect of a clinical user manually keying in incomplete or bad data.  I’ve seen issues stem from users not waiting for an ADT feed and manually keying in patient demographics.  This causes the receiving system to reject the message for one reason or another.  My answer to this is I keep an Excel file that logs these errors.  I try to investigate these sporadic errors during my downtime.  I’ll get third party support or a server admin involved, as we don’t always know where to look to find out why a system didn’t like a message.

[Jon Melin]

Thank you for the advice. Very helpful. How do you output specifically the 201 errors to an excel file? Through engie output? I’ve been reviewing most of these through command line so that would be great. I’d like to set this up as well so any direction you can offer would be great.

Thank you,

Jon

[Brandon Grudt]

I’m sure there’s a more technical way of it, but I simply run the Database Administrator tool for the error database, then copy that data to Excel.  I track the messages per error ratio and try to push myself to raise that number each month.

[Jon Melin]

Good approach. I’m sure there is a better way as you said but, I do something similar with the command line, but mine gets saved to a text file that is not formatted very well. I will have to try it your way to see if it’s formatted better.  

Thank you,

Jon

[Author]

Replies