Question
CPFB
SG
Last activity: 29 Jul 2019 21:34 EDT
File Listener does not process the valid file throws error "Unable to find match for record type"
File Listener does not process the valid file. The file is picked by listener and failed to process by Service file as "Unable to find match for record type". We received the file with correct format and data is starting with the letter which we define in Service file and still the file is not processing.Please let me know a way to solve this. It is working initially, only from few days it is not working. We are receiving file from other sources.
***Edited by Moderator: Lochan to update platform capability tags***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
Have you tried tracing the service? How about the logs then any stack associated?
CPFB
SG
Hi,
Service started and ended, nothing found in the tracer. I am seeing below error message in logs.
"Unable to find match for record type[0]"
Pegasystems Inc.
FR
Can you share the tracer anyway?
CPFB
SG
Please find the logs
Please find the logs
Pegasystems Inc.
FR
System is not able to find the Record Type in use can you trace it and share the XML?
CPFB
SG
Attached the tracer XML, please check. Uploaded as txt as we are not able to upload xml file.
Pegasystems Inc.
FR
Looks like the tracer provided is incomplete. So difficult to say what could go wrong. Could you simplify your File Listener for a quick test and just work with Out-Of-The-Box rules?
Have you tried to ZIP the XML?
CPFB
SG
Placed complete tracer, nothing found. Did not checked with OOTB rules, our requirement is to read only txt which we will receive from Other source. Zipped xml to zip, please check.
Pegasystems Inc.
FR
Hello,
Can I check your FileListener? I don't understand how your rule name could be "INS ID Class Name Service Name". This is really weird.
CPFB
SG
Rule name and security info has been replaced with other name. It is not actual Class name.
Rabobank
NL
Hi,
Would you know what a common rootcause is of: System is not able to find the Record Type?
Thanks,
CPFB
SG
Hi,
One time we identified because of encoding, now there is no issue with encoding, every where it is UTF-8 and still facing this issue.