cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Sender File Adapter

Former Member
0 Kudos

Hi,

In Sender File Adapter I have used content convertion. If the content convetion fails or the channel goes to error state, the sender file channel stops polling. The channel is not polling in the next interval once it goes to error state.

Please help.

Thanks

Aravind

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

whcih PI version do you use?

In PI 7.1 you can choose a specific error processing like skip or mote file to error folder and proceed polling.

Maybe you need an upgrade.

Former Member
0 Kudos

Hi,

I am using PI 7.1

"In PI 7.1 you can choose a specific error processing like skip or mote file to error folder and proceed polling."

can you please explain how this error procesing can be done?

Thanks

Aravind

stefan_grube
Active Contributor
0 Kudos

Check SAP Note 1483974 - File and JDBC sender adapter's retry not working after error

Apply the patch, this will help.

In sender channel you can set an archieve folder for files with errors, so they will not reprocess and cause the same issue again after retry.

Former Member
0 Kudos

Hi Stefan,

I tried applying the above note. But it says This note cannot be implemented.

I think This note is not suitable for the PI version I am using.

Thanks

Aravind

former_member200962
Active Contributor
0 Kudos

the note is very much applicabble to your version of PI (PI 7.1)....check the SP Patch Level section in the note.

Former Member
0 Kudos

Hi Abhishek,

In PI 7.1 there is an option known as "ARCHIVE FAULTY SOURCE FILES" option.

What it will do is "whenever a file came on FTP PI will polls and first it genrate a message id and if that message id is in error state untill few minutes it may be any reason like data issue, permission issues any issue it will move it to fault folder which you have specified in channel"

Regars

Amar Srinivas Eli

Answers (3)

Answers (3)

Former Member
0 Kudos

hI,

Yes this is true...in such cases u have to manaully start/stop the channel form RWB (after correcting the error)...

Thanks

Amit

Former Member
0 Kudos

Hi Amit,

yes, the channel starts working if it is stopped and started once.

But if a faulty file is placed, after archiving the faulty file shouldnt the channel start polling in the next intervall automatically?

In RWB after the error message It even shows " Retry interval started. Length: 10.0 seconds ". But it doesnt repoll.

Regards

Aravind

Former Member
0 Kudos

Hi,

when the comm channel fails, you need to sort out the problem with the help of Audit log / Adapter monitoring.

It will not pick the files until the issue is sorted out,& in case after the issue is sorted out and still the comm channel does not pick files then check Queue's using SMQ1/SMQ2 and check with AE cache.

Regards.

Sainath Chutke

Former Member
0 Kudos

Hi,

That's true.

If one file fails to process due error in content coversion or for any other reason, the channel would stop polling for the next time and also would not process the files following it.

Please correct the content conversion and process the file.

Regards,

Subbu