Seeburger AS2: Proxy Error 502

Hi guys,
I'm facing a problem using AS2 Seeburger Adapter.
When sending the message I'm getting the following error:
Could not deliver as2 message to partner: 502 Proxy Error
( The HTTP message includes an unsupported header or an unsupported combination of headers. ) # null
I've checked the AS2 Header message and I've got the following content:
POST /as2/HttpReceiver Connection: Keep-Alive
content-disposition: attachment; filename=1208788092268
Message-ID: <[email protected]1>
Subject: AS2 Message
Disposition-Notification-To: testcompanyAS2
AS2-To: receivertestAS2
Date: Mon, 21 Apr 2008 14:28:12 GMT
AS2-From: testcompanyAS2
AS2-Version: 1.1
content-type: application/octet-stream
begin test
1
end test
One of the things which is odd is why doesn't the AS2 adapter place the http://<server_used>:<port_used> before the "/as2/HttpReceiver".
Another thing is, shouldn't we have a line break after the POST?
It seems to me that this two problems may be raising the 502 exception...
Have you guys faced something similar?

Hi,
no, there shouldn't be any line break and the path is correct too..
First thing I'd check is the proxy settings. Is your partner's AS2 server in the same network? Or are you sending messages outside your network? Ask the network guys for a information about the proxy. Is this configured in your adapter properly (there is a proxy configuration parameter)? Because I think there is network issue now..
Peter

Similar Messages

  • Seeburger AS2: Proxy Error 407

    Hi All,
    I am facing the following error while sending message to receiver through AS2 
    Could not deliver as2 message to partner: 407 Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. ) # null
    Kindly suggest the solution to resolve the error.
    Hoping for a good reply
    Regards
    Prakash

    May not be an authentication issue. Please go through this link:
    http://www.isaserver.org/tutorials/Troubleshooting_ISA_authentication_issues.html
    Confusing Authentication problems.
    In many instances most people have confused authentication with a service that is explicitly denying them access to the resource.  Please note that if you are denied access to a resource it has nothing to do with authentication but with permissions to the resource.  An authentication issue normally identifies itself with prompt for user credential or with an error message stating that authentication has failed with the server.
    A typical error that you will encounter is error 407 Proxy Authentication Required this means that the authentication has been denied because the user has no valid user account in the domain or that the password has been entered incorrectly.  The 401 error however displays an unauthorized error message this mean the user permissions to that resource are denied.  This error message tells you to look at the ISA server rules not at the way the authentication is handled
    Authenticate: username.passwords should be right
    Authorization: not allowed to access a resource
    "The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied." You might have to look at this authorization issue.

  • Seeburger AS2 Reciever error: 404

    Hi
    Configuring and activating the interface for AS2 receiver channel is loggin error in RWB:
    Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 404 %2Fhttp%3A%2F%2FBlueberry%2ECommu%2Ecom%3A4080%2Fas2NotFound
    Pls can any help be offered to fix this issue?
    Regards
    Prabhu

    Hi Prabhu,
    Check the belowlinks
    403 Forbidden error in a Secured B2B (EDI XI) connection
    Http* Errors in XI
    Make sure that SAP/XI/Engine is active in SICF transaction.
    Regards,
    Venkata Ramesh

  • Seeburger AS2 Adapter error

    Hi,
      I'm trying to test AS2 connection with External system and got some errors.
      I'm able to send message successfully to the external system with MDN Mode Synchronus with out any errors and got the MDN back, I changed the MDN mode to Asynchronus and got the below error. Do we need to do any extra configuration for Asynchronus mode MDN?
    Waiting for your valuble suggestions.
    Error message : Error in unkown channel: (No session available) >> Error type: COMMUNICATION_ERROR >> Error date: 9/23/10 2:19 PM >> Description: 500 - Internal Server Error: Error while handle incoming request: java.lang.NullPointerException: while trying to invoke the method java.lang.String.toUpperCase() of an object returned from com.seeburger.as2.tasks.result.MDNDecomposerResult.getMdnOriginalMessageID() [9/23/10 2:19 PM]
    Thanks,
    Kishore

    Hi,
      Sorry for the late reply.
      Receipt Delivery Address : Enter the URL of yr own AS2.
      Yes, I specified our AS2 address as http://xxxx:50000/SeeburgerAS2/AS2Server
      Time Out: What you have given.
      10 min
      In case of asynchronous MDN mode, an Report channel and Sender agreement always have to be configured also when u201CRefer to XI systemu201D is disabled
    Yes, I have created Sender agreement and Sender communication channel with Message protocol as Reports.
    Thanks,
    Kishore

  • Seeburger As2 adapter error after upgrade

    Hello,
    After an upgrade from PI 7.01 to PI 7.11 we have problems with our AS2 seeburger adapter. We installed the compatible version of seeburger but got stuck on the following error:
    Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm.
    Thanks a lot for any advice,
    Regards,
    Erik

    Hi
    Pls chk the security jar files. you can download the latest version of these from java portal. This might fix the issues related to Key.
    Srikanth Srinivasan

  • Seeburger AS2 Adapter Error :AUTHENTICATION_ERROR

    i am doing the scenario for Purchase Order -> XI ->File
    custumer is posting the purchase order
    and XI Receives the PO using AS2 Adapter (Seeburger) and sends the output as File
    i have done all the AS2 Adapter configurations as mentioned below but still i am getting the error in Seeburger Monitoring, the Error is Authentication_Error
    1. Communication chennel
      Adapter Type : AS2
      Direction : Sender
    Transport protocol : HTTP
    Message Protocol : AS2
    AS2 : Authentication Required is Enabled
    Message Subject : Filled which is in Seeburger Monitor
    2. Sender Agreement
    Sender Communicational chennel which is created above
    Security Setting
    AS2 Sender Config :
    Authentication Certificate : Customer public key
    AS2 Receiver Config :
    Decryption Key : Private key
    3. in Party Identifiers
    Party Name
    AS2 ID
    is there any settings missing to rectify the error "AUTHENTICATION_ERROR"

    Hi
    Check with PIAPPLUSER authentication
    With this Check the following content on AS2 may be you get more clue.
    http://www.customware.net/repository/display/WMFAQ/AS2-authenticationfailureinreceivingEDIINT+MDN
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bpxproj/edi%2bwith%2bpi
    Handling EDI interfaces using Seeburger BIC modules
    Thanks
    Gaurav

  • Seeburger AS2- Authentication Error

    Hi All,
       We are using Seeburger AS2 adapter and we will send and receive EDI documents to two Mail Box.
    We are using certificates for signing and encrypting the message. While sending and receiving EDI documents to Mail Box1, all messages are successfull.
    When we send message to Mail Box 2 . It is successfully delivered to the receiving partner. But when we are receiving message from trading partner we are facing following error in the Seburger Workbench.
    Error while parsing message in AS2 adapter:AUTHENTICATION FAILURE.
    We have restarted the server and tried, still same error we are facing.
    For AS2 Channel Configuration in Integration Directory we followed SAPXI_AS2Adapter_en document.
    Can any one suggest solution to solve the error.
    Regards
    Prakash

    It is certificate issue which was solved

  • Seeburger AS2 403 error

    I've already seen [this posting |SEEBURGER AS2: 403 Forbidden #; and my AS2 scenario is working properly as long as I have a single channel.
    The wrinkle is that I need to add a second AS2 channel for the same trading partner.  The second adapter is needed to allow for message transofmration, this must be done in the sender channel since the receiver channel is an idoc channel, which does not allow for transformation.
    Is it possible, if so how, to set up two unique Seeburger AS2 sender channels to receive messages from a single trading partner, and to apply message transformation in one of those channels and not the other.
    -Gerry

    Hi Gerry,
    It is not possible to have the same channel twice for the same trading partner.
    But you can use the "skipExecution" parameter and an expression, to evaluate if you need to run the conversion or not.
    Do you receive different message types from one partner in the same AS2 channel?
    And some of them need to be converted while others need no conversion?
    regards,
    Daniel
    Edited by: Daniel Rexter on Nov 22, 2010 5:06 PM

  • How do I fix a proxy error 502?

    This is exact of what showed up on my computer.
    "The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request GET /wamvalidate.
    Reason: Error reading from remote server"

    That's an error on the web server, not on your computer.

  • As2 receiver channel, SEEBURGER AS2: 500 Internal Server Error

    Hi,
    There is one scenario in our landscape, its running in production, Proxy to As2. The interface working fine for last 2 weeks, today its showing error in As2 receiver channel saying
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: 500 Internal Server Error # , SEEBURGER AS2: 500 Internal Server Error #
    I have searched in forum, but couldnt get much idea on why this error encounters and how can we resolve it.
    Kindly provide your inputs to help me resolve this.
    Thanks,
    Ruchi

    Hi Ruchi,
    500 means the requested server does not understand the request (the requested service is unknown). The reason is obvisiously outside of PI. You have to contact the 3rd party owner and ask why the system is refusing the request instead of responsing like before.
    Regards,
    Udo

  • Seeburger AS2 HTTPS receiver channel error

    Hi,
    I am getting the following error in the receiver Seeburger AS2 channel with HTPS connection and going through a proxy to the Partner.All the certificates have been installed,proxy server information gives,mentioned the key store values  and encryption certificate values have been mentioned in the receiver agreement that is using the channel.
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection., SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection.
    Can you please give me an idea whether I am missing something or any configuration settings I need to make.
    Thank you,
    Sri

    hi Neetesh,
    Thank you for the link.The first thing I have looked at is the link you gave me.But when I give with * it is complaining that it is not able to retrieve the certificates.
    TRUSTED/AS2CERTS/*,but I have backward slashes..may be  OS is different ,I think the original poste might have Windows servers.
    any other ideas please.
    thank you.

  • Seeburger AS2 Communication Channel Error

    Hello,
    when trying to send a test message to the AS2 receiver communication channel I get the following error in communication channel monitoring:
    javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: ResourceException caused by com.seeburger.xi.api.cci.SeeXIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., ResourceException caused by com.seeburger.xi.api.cci.SeeXIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE..
    Have you ever got a similar error? Seems to be a configuration error of the adapter installation itself rather than a problem with configuration objects or the receiver channel.
    Do you have any idea?

    Hi Florian,
    Please provide info if there is a need for any Sender agreement in case we select "Synchronous" mode for MDN and Handle Received MDn as "NoAction".
    I am also getting the below error for my scenario (IDOC --> XI --> AS2)
    Description: AS2 Adapter failure Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.. com.seeburger.as2.AS2Plugin.execute
    Thanks and regards
    Ajay Garg

  • Error in AS2 RCV adapter.. SEEBURGER AS2: 307 Temporary Redirect #

    Hi all,
    Iam just doing File to File scenario and passing the resultant file to Partner system through AS2 adapter.
    I gave the following details in AS2 RCV adapter..
    SND>XI->Webdispatcher--->Partner.
    My message will be reached to webdispatcher.. from there it will route to Partner Url.
    So i will be giving my webdispatcher URL in my AS2 RCV adapter.
    TP : HTTP
    MP : AS2
    Server : vvvvvv.com.NZ
    Port : 50000
    Url :  /as2gs1/partnera
    Message is processed succesfully but its failing in AS2 RCV adapter with following error.
    Success      SEEBURGER/AS2: Received order from system.
    Error      Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #.
    Error      The message status set to NDLV.
    Kindly let me know if anyone know th solution.
    Regards
    Seema.

    Hi Peter,
    >> a, what do you mean with the Web Dispatcher?
    We are not using the partner URL directly.We will be using Webdispatcher URL .. from there they have written the rule to goto Partner URL.
    >> b, you receive a HTTP code 307, which means that the target AS2 location has been moved. Try to connect the target AS2 server on the URL and check, if it is really there and if it is working.
    Looks like this is working.. its showed success state for a while and after few minutes.. its showing the below error in communication channel monitoring.
    Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address #.
    This is the error it is showing in Seeburger Monitoring.
    State                          : Error on send, will be retried
    Status Description  : Could not deliver as2 message to partner: java.net.SocketException: Connection timed out:could be due to invalid address # null
    What is this error?
    Do u think there is no problem with AS2 adapter.. its the problem wit webdispatcher.??
    Waiting for your reply.
    -Seema.

  • Issue with HTTPS in sender soap channel: HTTP 502 Proxy error

    Hi
    We have a situation where we are providing the target url in SOAP receiver channel dynamically.
    This is a synchronous scenario.
    Whenever we use the url starting with "HTTP" it works but on using "HTTPS" we are getting the following error "HTTP 502 Proxy error"
    Kindly help us resolve this issue.

    Hi Anurag
    Have you tried to open the HTTPS  url in the web browser?
    Please check with 3rd party and find out whether the web service supports the HTTPS url or not.
    Please check the doc below. It may help
    502 Bad Gateway Error (What It Is and How To Fix It)

  • Seeburger AS2 Adapter sending message error

    I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor).  I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
    LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
    MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
    I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
    If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ... 
    Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
    Regards,
    Jason

    Hello ,
    same issue occurred in my system
    Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
    I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
    Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
    Please advise asap.

Maybe you are looking for