cancel
Showing results for 
Search instead for 
Did you mean: 

Messages getting stuck, at Seeburger

Former Member
0 Kudos

I am having standard seeburger as2 solution employed for message exchange. But for a particular partner we are receiving follwing error:

The error has been taken from RWB and it displays follwing in communication channels logs:

"Alert: Maximum number of retries reached. Retry 20. Message initiation failed: Can split neither message of type 'Inhouse VDA' nor 'InhouseVDA' - Both parameters, 'Inhouse VDASplit' and 'InhouseVDASplit', are missing! Please configure either the one or the other! "

Earlier the communication was done in Inhouse format for which there exist no issues. The scenario has stopped working since a few days.

Please let me know, how should I proceed over this, or what values needs to be configured in BIC modules or so.

Regards,

Nipun

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

One more thing:

it's likely that someone checked the split option by mistake, since it is of limited use for Inhouse formats !

Former Member
0 Kudos

Thanks Frederic,

I have checked the spilt option.

In the spilt, I have entries for ANSIX and INHOUSE but no entries for InhouseVDA.

Moreover to make things more different we have found out the files whihc classifier is detecting as Inhouse VDA are not exactly Inhouse VDA file, but are similar to Inhouse VDA structure.

Let me know what settings I can make so that classifier can resume prcessing with Inhouse VDA file.

Former Member
0 Kudos

Hi,

please check the Sender AS2 channel of question. You obviously have the split option checked - in this case you need to define a split type for each message type that is passing through / received by this channel.

See also the AS2 manual and pay attention to chapter "Message Splitting".

Regards,

Frederic