cancel
Showing results for 
Search instead for 
Did you mean: 

Seeburger error - No matching inbound binding found

0 Kudos

Hi

I am trying to buld a interface using Seeburger AS2 adapter. I have done all the config in XI and Seeburger level. But when customer sent the message he gets following error.

HTTP/1.1 403 Forbidden^M

server: SAP J2EE Engine/7.00^M

content-type: text/html^M

content-length: 826^M

date: Tue, 18 Nov 2008 23:50:04 GMT^M

^M

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">

<head>

<title>SEEBURGER AS2 Server: Forbidden </title>

</head>

<body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="

#551a8b">

<table cellpadding="0" cellspacing="0" border="0" width="100%" bgcolor="#dc4560">

<tbody>

<tr><td>&nbsp;</td></tr>

<tr>

<td>&nbsp;</td>

<td valign="middle">

<h3>

<font face="sans-serif" color="#ffffff">SEEBURGER AS2 Controller</font>

</h3>

</td>

</tr>

</tbody>

</table>

<br/>

<font face="sans-serif" size="-1">

<b>

403 Forbidden

</b>

</font>

<br/>

</body>

</html>

When I checked the Seebuger log I noticed following

seeburger.as2.AS2Plugin#Plain###Inbound communication from TESTEDI to GFB2BDPI not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No matching inbound binding (message) found for FromParty:PT_TOLL ToParty:PT_GOODMANFIELDER subject:<20081119091602.651278.2248792@> [LOC: com.seeburger.as2.component.AS2Server.checkInboundRelation]#

If someone can help that will be great.

Thanks

Shantha Bandara

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Thanks Every one who tried to help me. I managed to resolve this issue.

Shantha Bandara

danny_deroovere
Participant
0 Kudos

Hello,

I'm having the same error. How did you solve this problem?

S0003485845
Contributor
0 Kudos

Hi,

403 is a standard error if the AS2-IDs are not setup correct. You can also seet his in your log-file:

"Inbound communication from TESTEDI to GFB2BDPI not allowed"

Looks like the SenderAgreement is not referring to the correct parties...

Greetings

Stefan