Error in Seeburger Adapter

Hi Experts,
We are sending a message to a Partner, and i can see the message processed succesfully in the SXMB_MONI and also in the Runtime Workbench, but when i see in the seeburger adapter monitoring for the MDN's i noticed that the message was in Error MIC not verified # MIC values not verified sha1-null. At first i thought the error was related to certificate, but when the message was retried after some time it was sucessfully processed and we got positive MDN's also. Could you please let me know when exactly the Error comes? and what can be done to solve this issue.
Many Thanks.
Edited by: Ravi Kumar Nakerikanti on Aug 13, 2008 4:51 AM

Hi,
You have used the AS2 Message type MDN (Message Disposition Notification).
An MDN may optionally be signed, in which case the recipient can authenticate the sender of the MDN and check its integrity. A valid, signed MDN together with a valid MIC reported by the MDN can be used by the sender of the payload message
But here this validation is failed ...and have raised the error like
"MIC not verified # MIC algorithms not verified [LOC: com.seeburger.as2.component.MDNHandler.parseMDN]"
refer
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_AS2_Spoke_Unit_for_Trading_Partner_Integration.pdf
Thanks
Swarup

Similar Messages

Seeburger Adapter Module Error

Hi
I have a scenario orders idoc to x12,I have done bic maaping & deployed sda file to SDM.And the paramater i have defined at the adapter module
bic mappingname
bic destTargetMsg
bic destSourceMsg
And the error i am getting is
2007-04-16 16:13:51 Success process()
2007-04-16 16:13:51 Error process()
2007-04-16 16:13:51 Error process()
2007-04-16 16:13:51 Error MP: exception caught with cause java.lang.NullPointerException
2007-04-16 16:13:51 Error Exception caught by adapter framework: null
2007-04-16 16:13:51 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
2007-04-16 16:13:51 Error The message status set to NDLV
Any hep would be highly appreciated
Thanks
sri

Hi Sriram,
Which Seeburger Adapter are you using to transmit your converted X12 message?
Rgds,
Sam Raju
null

Error in Oubound message using Seeburger Adapter

Hi,
I'm getting this error on the Adapter engine when trying to generate an outbound EDI message with Seeburger adapter:
2007-01-24 13:33:29      Error      Unable to forward message to JCA adapter. Reason:
Fatal exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException:
Entry rejected due to error in resource management: null, Entry rejected due to
error in resource management: null
2007-01-24 13:33:29      Error      MP: exception caught with cause
javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null
2007-01-24 13:33:29      Error      Exception caught by adapter framework: Fatal
exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry
rejected due to error in resource management: null, Entry rejected due to error
in resource management: null
2007-01-24 13:33:29      Error      Delivery of the message to the application using
connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null: javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null.
Any ideas?
Rgds,
Yves

Yves,
I think there is some problem in invoking the seeburger adapter. Have you installed the adapter? Also after installing you have to import the metadata. Check this document for further help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
---Satish

Error at AS2 adapter level.. Duplicate will not be sent, SEEBURGER AS2: ..!

Hi All,
Iam sending the Control message through AS2 adapter to partner and i got the below error at the adapter level.
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.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: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> alre.
Any one has any idea what might be wrong?? Did i miss anything??
Waiting for your answers.
Regards
Deepthi.

A patch needs to be updated to solve this issue.

Error in Seeburger Message Monitoring

Hi ,
I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file.
I m getting error in seeburger message monitoring with status as "Could not send ansynchrone MDN to partner - url not set!". can anybody tell me whats the reason behind it,where it went wrong.

Really didn't understand your scenario. That sentence makes no sense:
"I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file."
But what I understand from the error message you have provided...................
if you are using Seeburger AS2 adapter as Receiver Comm Channel..........then there is definitely some cofig error is settings for MDN acknowledgement.
Under Parameters Tab:
You must have set the following parameter
MDN Mode = "ASYNC"
And has not provided the following parameter just below it :
Receipt Delivery Address
This parameter should have value: the URL of your own AS2
server where the asynchronous MDNs are
to be delivered.
Hope this solves your problem.
Regards,
Suddha

Seeburger adapter monitoring

We are running Seeburger AS2 adapter with XI3.0.
All inbound messages that the adapter can handle are passed to XI and we have access to those from XI message monitoring.
From there we have alerting setup.
Whenever an external party presents a message with a bad certificate the AS2 adapter refuses the message.
We can see trace of that in the adapter monitor. But there is no message in error passed to XI. So nothing we could get in message monitoring.
We saw we have a logfile containing those errors on the server. We could setup a logfile monitor on this file and get errors in CCMS. And from there, we could trigger alerts. But that does not look very elegant.
Is there a best way to get Seeburger adapter error generating alerts ?

Hi,
If the check is happening in the Adapter then the Alerts needs to be raised by Adapter framework.
So you have to set up Alert rule for the Adapter framework.
The message goes to message montioring only if the adapter sends the date to the Adapter engine and then you can see the message in the message monitoring.
If the rejection is at AF levelt hen you need to check in the Communication Channel if you are getting the Error?
Regards
Vijaya

Issue in receiver SFTP seeburger adapter

Dear all,
We have a proxy to sFTP scenario.
The target message is being delivered to a sFTP system using a receiver sFTP Seeburger adapter.
I have this error being shown in the receiver channel.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true, >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true.
The Seeburger WorkBench monitoring has a 2 error entries which says
1. PUT command for file <TEMP_20110406_115127.TXT> is in progress.
2. "Error on send, will be retried"
Finally, the .txt file is partially written in the receiver system.
If anyone has any inputs/pointers to resolve this issue. Pls share the details.
regards,
Jack.

Hi Jack,
We are also facing the same problem with the seeburger SFTP adapter. If you find the solution , Plz let us know.
Thanks,
Soumya.

SFTP Seeburger adapter - Could not find channel for report handling between

Hello Friends ,
We have R3 -> PI-> SFTP scenario . The messages are transferred successfully and the file is successfully received at the receiving end . But when we do communication channel monitoring , we see errors in Receiver CC . The Reciever CC contains SFTP adapter (Seeburger) . Recently the Seeburger adapter is upgraded and the below error has started occuring then onwards .
Error Message which we see in CC monitoring for Receiver CC (SFTP) is as below .
Initiation of Transmission Report( job id: da405030-30c6-11df-8b6e-797b8921162c milestone: 290) failed! Exception occured: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) - com.seeburger.xi.connector.fw.ConfigurationException: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) [3/16/10 8:40 AM]
Could experts help me ...
Thanks for your time .
Regards,
Laxman Nayak .

Hi,
I also have the error you mentioned but we're implementing the Seeburger SFTP adapter for the first time.
I've requested transport acknowledgements in my ABAP proxy and have checked the 'Deliver transmission report' flag in the adapter but I don't know what else I must do.
Any help would be greatly appreciated.
Thanks,
Alan

Error at AS2 adapter level...There is no certificate with such alias

Hi All,
Iam sending the 856 message through AS2 adapter to partner and i got the below error at the adapter level.
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no certificate with such alias, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Th
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no certificate with such alias, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Th
The certificate has already been uploaded and the AS2ID is defined as one of the identifiers of the party.
Anyone has any idea what might be wrong? Did i miss anything?
Waiting for your answers.
Regards
Lex

I am having the same issue.
I receive the com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException
message plus the "unable to find alias name TRUSTED\".
It appears that after the outbound message is transformed to XML iin XI then sent to Seeburger's BIC for EDI format translation, then sent to AS2 for encryption/transmission, the AS2 adapter cannot find the key store that holds the certificates I am using.
Am I missing some configuration that points the to the keystore I need ?
Thanks for any and all responses.
Andy

Error-Receiver File Adapter using Variable substitution when file is empty

XI Experts,
We are on PI 7.0, SP14.
We are using variable subtitution to get the filename from source message. This works fine as long as we have data in the payload for filename element. But we have a scenario where we don't have to create file when certain condition does not exists in source message so in the message payload filename element will not exists in such condition and file will be empty and we should not create file.
Parameter in the communication channel for Handling empty message is "Ignore".
Does anyone knows how to handle this scneario. We don't want to default any file name in the message mapping if source file name element does not exists.
We are following getting error in the Adapter engine.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file
Thanks
MP

You can implement this by writing the module to throw an exception or whatever method you want to execute.
If you don't want to receive an error message then module is suitable for you.
Gaurav Jain

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

Getting error in the adapter engine when sending a message

Hi,
I'm always getting this error in the adapter engine: Message processing failed. Cause: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme
The comm channel ends up in error because of messages having the above error.
Could someone please help?
Thanks.
Mike

Mike.
Please check this links.
Check your adapter and restarted.
com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
Re: Prerequisites to setup configure mail scenario.
error in communication channel
Error :Receiver File Channel not Initialized

File-IDoc scnario : Error in call adapter

Hi Experts,
I have developed File to IDoc scenario. And getting the following error in "Call Adapter" pipeline step. I have mapped the control record values in IDoc like Sender Partner, no, port and same for receiver.
Have created:
In XI: RFC destination to connect to ECC (sm59)
Port for the above RFC sestination (idx1)
In ECC: New logical system for source file system (BD54)
Partner Profile for Source (we20)
Also in Receiver_IDoc_CC, checked options for 1. Apply control record values from payload 2. Take Sender and Receiver from Payload
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please tell me if i am doing any mistake.
Br,
Nilz

Hi,
Adding to Björn
Check the Port ( Tcode - idx1 ) Port SAPEAQ_100 & Select the Business System where you declared IDOC adapter -go to - Service and check whether you have mentioned the right Logic System,System ID & Client.
Cheers
Agasthuri Doss

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
Scenario: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
SOAP Receiver adaptor.
Target URL http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
SOAP Action http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the sender soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

Error in Call Adapter (IDOC- XI- FILE)

Hello,
i have got the following error message in the integration engine monitoring in the "call adapter" part:
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
What is the AFW application?????

Hi Christian,
Have a look at the following thread, it might be useful
XI Server Malfunction:Error in Receiver Adapter
Regards
Suraj

Error in Seeburger Adapter

Similar Messages

Maybe you are looking for