Troubleshooting
Problem
Alerts with Type AGENTEXCEPTION ErrorType NONREPROCESS with no OrderNo reference
Symptom
PART: Yantra-Console 5.0 SP2 Platform
PRODUCT: Distributed Order
Management
COMPONENT: Alert Management
NonReprocess Errors logged by
the Agent framework do NOT have any data describing the actual Document ID /
Key that had the error.
The user needs to go to the log file for that time
period and look up the trace to see which Order errored out.
Yantra's agent
framework needs to be intelligent enough to log the Name Value Pair as
Identifiers on the Alert or as References on the Alert.
Cause
Resolving The Problem
Resolution:
This is currently a limitation in the product.
and has been
forwarded to Product Management
The workaround would be to look into the
yantra error logs for the time corresponding to the INBOX_KEY and find the
document ID from that log section.
We also have a SQL query that can be
used to review all such AGENTEXCEPTIONS during a period of time and take
corrective action.
Please use this query after testing for
performance.
It can be very slow if the INBOX table is huge.
select
count(*), yir.value, yeca.CAUSE, yeca.ACTION
from yfs_inbox yi,
yfs_inbox_references yir , yfs_error_cause_action yeca
where
rtrim(yir.VALUE) = rtrim(yeca.ERROR_CODE_KEY)
and yi.exception_type =
'AGENTEXCEPTION'
and yir.inbox_key=yi.inbox_key
and yi.inbox_key >
'200408'
and name='ERRORCODE'
group by yir.value, yeca.CAUSE,
yeca.ACTION
COUNT(*),VALUE,CAUSE,ACTION
2,YCP0061,The base drop
status is not uniquely determinable.,Pass the base drop status for the
transaction in the input XML or Setup atleast one base drop status for the
transaction, and then invoke the API.
1,YDM00105,Ship node must have an
address key to help us determine whether a shipment is domestic or
international based on the ship node country.,Modify ship node to have an
address.
4,YFC0009,Update failed because of councurrent modification to the
same record..Please try the operation again,
13,YFS10001,No record found in
YFS DB,No record that has the matching search criteria.
1,YFS10048,Ship node
doesn exist,Enter existing ship node
1,YFS10290,Order can not be
allocated,Check to see if order is held, if the customized function failed, or
if payment status does not belong to authozized, invoiced, or
paid.
6,YFS10405,Invalid inventory monitor rule.,Check inventory monitor
rule.
You can periodically monitor the alert queue and remove these
errors after making sure that the root problem has been addressed.
Historical Number
PRI49409
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21539469