Seeburger Adapter Error

Hi Everyone,
I am trying to send messages to a VAN using Seeburger. However I am facing the following error
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at solution, the whole lookup name is localejbs/Seeburger/solution/van
I have seen other threads with same error however unfortunately after resolution no has posted the solution. Can I please request some help with this.
regards

Hi,
you are trying to execute a Module in the Module Chain which does not exist ("localejbs/Seeburger/solution/van")
For testing, you can remove this module from the module chain. If there are no other errors in your configuration, you should be able to use this channel now. However, you also should deploy the missing module ("localejbs/Seeburger/solution/van") in order to have a standard configuration, which includes the Solution Module.
regards,
Daniel

Similar Messages

  • 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

  • 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 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

  • 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

  • AS2 adapter error during inbound processing

    Hello,
    We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
    We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
    Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
    In the RWB the communication channel (CC_AS2_Sender) gives the following error:
    "Message inititiation failed: Processing error"
    The message itself gives the following error:
    "Inbound message processing failed! performing rollback
    Can anyone help us with this?
    Thanks in advance.
    Regards,
    Marco

    Hi Marco,
    the message is not forwarded to the intergration egine because there might be an error in your communication channel.
    Are there any other modules in the module chain of this communication channel?
    Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
    Did you also restart the Java Stack after the Upgrade?
    regards,
    Daniel
    Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

  • 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

  • Unable to create database due to ORA-12560, TNS protocol adapter error

    Hello,
    I'm trying to create an 8.1.7.0 database on a W2k server, but it is failing because as soon as svrmgrl is launched, I get an ORA-12560, TNS: protocol adapter error:
    D:\oracle\db_creation_scripts>D:\oracle\ora81\bin\svrmgrl @D:\oracle\db_creation_scripts\mterm62run.sql
    Oracle Server Manager Release 3.1.7.0.0 - Production
    Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
    ORA-12560: TNS:protocol adapter errorEcho ON
    SVRMGR> connect INTERNAL/manager
    ORA-12560: TNS:protocol adapter error
    SVRMGR> startup nomount pfile="D:\oracle\admin\mterm62\pfile\initmterm62.ora"
    LCC-00161: Message 161 not found; product=RDBMS; facility=MGR
    My ORACLE_HOME, ORACLE_SID, and TNS_ADMIN environmental variables are correctly set, and I'm able to tnsping the listener.
    I've enabled tracing, and my client trace file is:
    --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
    New trace stream is d:\trace\client_trace.log_2084_9.trc
    New trace level is 6
    --- TRACE CONFIGURATION INFORMATION ENDS ---
    --- PARAMETER SOURCE INFORMATION FOLLOWS ---
    Attempted load of system pfile source d:\oracle\ora81\network\admin\sqlnet.ora
    Parameter source loaded successfully
    Attempted load of local pfile source D:\oracle\db_creation_scripts\sqlnet.ora
    Parameter source was not loaded
    -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
    Successful parameter table load
    -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
    TRACE_DIRECTORY_SERVER = d:\trace
    TRACE_DIRECTORY_CLIENT = d:\trace
    NAMES.DIRECTORY_PATH = (TNSNAMES, HOSTNAME)
    SQLNET.CRYPTO_SEED = 4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf
    TRACE_FILE_CLIENT = client_trace.log
    TRACE_FILE_SERVER = server_trace.log
    SQLNET.AUTHENTICATION_SERVICES = (NTS)
    TRACE_UNIQUE_CLIENT = on
    TRACE_LEVEL_CLIENT = ADMIN
    TRACE_LEVEL_SERVER = ADMIN
    --- PARAMETER SOURCE INFORMATION ENDS ---
    --- LOG CONFIGURATION INFORMATION FOLLOWS ---
    Log stream will be "D:\oracle\db_creation_scripts\sqlnet.log"
    Log stream validation not requested
    --- LOG CONFIGURATION INFORMATION ENDS ---
    nigini: entry
    nigini: Count in NI global area now: 1
    nigini: Count in NI global area now: 1
    nrigbi: entry
    nrigbni: entry
    nrigbni: Unable to get data from navigation file tnsnav.ora
    nrigbni: exit
    nrigbi: exit
    nigini: exit
    niqname: Hst is already an NVstring.
    niqname: Inserting CID.
    niotns: entry
    niotns: niotns: setting up interrupt handler...
    niotns: Not trying to enable dead connection detection.
    niotns: Calling address: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleMTERM62)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=MTERM62)(CID=(PROGRAM=D:\oracle\ora81\bin\SVRMGRL.EXE)(HOST=SERV0354)(USER=tarisa))))
    nsmal: 140 bytes at 0x12493f0
    nscall: connecting...
    nladini: entry
    nladini: exit
    nladget: entry
    nladget: exit
    nlpcaini: entry
    nlpcaini: prg =
    nlpcaini: arg[0] =
    nlpcaini: arg[1] =
    nlpcaini: exit
    nsmal: 420 bytes at 0x12542f0
    nsmal: 1712 bytes at 0x12572f0
    nsopen: opening transport...
    ntpcon: entry
    ntpcon: toc = 1
    sntpcall: entry
    snlpcss: entry
    ntpcon: exit
    nserror: nsres: id=0, op=65, ns=12560, ns2=0; nt[0]=530, nt[1]=2, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
    nsopen: unable to open transport
    nsmfr: 1712 bytes at 0x12572f0
    nsmfr: 420 bytes at 0x12542f0
    nladget: entry
    nladget: exit
    nsmfr: 140 bytes at 0x12493f0
    nladtrm: entry
    nladtrm: exit
    nioqper: error from nscall
    nioqper: nr err code: 0
    nioqper: ns main err code: 12560
    nioqper: ns (2) err code: 0
    nioqper: nt main err code: 530
    nioqper: nt (2) err code: 2
    nioqper: nt OS err code: 0
    niomapnserror: entry
    niqme: entry
    niqme: reporting NS-12560 error as ORA-12560
    niqme: exit
    niomapnserror: returning error 12560
    niomapnserror: exit
    niotns: Couldn't connect, returning 12560
    niotns: exit
    nigtrm: Count in the NI global area is now 0
    nnfgdei: entry
    nrigbd: entry
    nrigbd: exit
    nigtrm: Count in the NL global area is now 0
    My tnsnames, listener and sqlnet.ora files are very simple:
    ## BEGIN TNSNAMES.ORA
    # TNSNAMES.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\tnsnames.ora
    # Generated by Oracle configuration tools.
    MTERM62 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.3.1.75)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = mterm62)
    (INSTANCE_NAME = mterm62)
    INST1_HTTP =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.3.1.75)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = SHARED)
    (SERVICE_NAME = mterm62)
    (PRESENTATION = http://admin)
    # LISTENER.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = serv0354)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_DESC =
    (ORACLE_HOME = D:\oracle\ora81)
    (SID_NAME = mterm62)
    TRACE_LEVEL_LISTENER = ADMIN
    # SQLNET.ORA Network Configuration File: D:\oracle\ora81\NETWORK\ADMIN\sqlnet.ora
    # Generated by Oracle configuration tools.
    TRACE_DIRECTORY_CLIENT = d:\trace
    TRACE_UNIQUE_CLIENT = on
    TRACE_DIRECTORY_SERVER = d:\trace
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    TRACE_FILE_CLIENT = client_trace.log
    TRACE_FILE_SERVER = server_trace.log
    TRACE_LEVEL_CLIENT = ADMIN
    TRACE_LEVEL_SERVER = ADMIN
    NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME)
    SQLNET.CRYPTO_SEED = 4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf
    Does anyone have any ideas what else I can check. I'm a Unix person, not a Windows person, which is making it even more complicated. If I was on Unix, I'd just blow everything away and start again from scratch, but since I'm not sure how to remove all traces from the registry, etc., I don't want to try that on this machine. There was already one other database created, but it's not goign to be used.
    Any help would be greatly appreciated.
    regards,
    Tarisa.

    hi,
    thanks for the info. the problem, as it turns out, was that I was connected to the db server via a terminal service (Microsoft Management Console), which for some reason caused probelms with TNS. After I connected directly to the machine using VNC, I was able to create the database with no problems. strange but true.
    regards,
    Tarisa.

  • "TNS: Protocol adapter error" while creating a database

    Hi All,
    I´m new to Oracle and trying to create a database.
    We use Oracle 8.1.7
    I´m using the Database Configuration Assistant. The problem is when creating the database I get the error:
    TNS-12560 TNS: Protocol adapter error
    Any help will be really appreciated.
    Thanks in advance,
    Carlos.

    Do you have ORACLE_HOME and/or ORACLE_SID defined in the environment which are different than the settings for the new database that you are trying to create?

  • TNS-12560: TNS:protocol adapter error, ORA-12535: TNS:operation timed out

    I installed Oracle 9i (9.2.0.1.0) on a Windows XP machine (the machine is in a domain). There were no errors during the instalation, but I have problems connecting from the same machine using the sid. Here are some examples from a command promt:
    D:\>tnsping orcl9i
    TNS Ping Utility for 32-bit Windows: Version 9.2.0.1.0 - Production on 31-OCT-20
    08 17:43:22
    Copyright (c) 1997 Oracle Corporation.  All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = timisoara01)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = orcl9i)))
    TNS-12560: TNS:protocol adapter error
    D:\>sqlplus "sys/pass@orcl9i as sysdba"
    SQL*Plus: Release 9.2.0.1.0 - Production on Fri Oct 31 17:54:54 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    ERROR:
    ORA-12535: TNS:operation timed out
    Enter user-name:If I don't use the sid I can connect:
    D:\>sqlplus "sys/pass as sysdba"
    SQL*Plus: Release 9.2.0.1.0 - Production on Fri Oct 31 18:05:46 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    SQL>If I go to services I see that the service is running: OracleServiceORCL9I Started.
    Thx.

    Yes, the XP firewall is running. During the Oracle instalation it poped up twice, but I selected 'Unblock'. I can't turn it off because it is running using the domain settings, but I can add exceptions (programs or ports). Port 1521, tnsping or sqlplus are not blocked and there is an option 'Display a notification when Windows Firewall blocks a program' witch is checked.

  • File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)

    File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)
    Hi all,
      im having some troubles after the installation of SP19 (from SP16 in NW04) with File Adapter (File->Idoc scenario).
    In message monitoring (Adapter Engine), I have several messages with status "System Error". The error text is :
    <i>Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR
    ErrorText:   ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace 'http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,</i>
    Im sure that the Integration Directory settings have not been changed. So I tried the following, but the problem persists:
    - Deactivation/Activation of File Adapter channel
    - check that user XIISUSER is not locked
    - checked SXI_CACHE (it seems ok)
    - Many CPA full refresh
    - Dummy modifications of File Adapter channels (a dummy modification of the description)
    - Reboot J2EE
    I've seen that someone else had problems after upgrading to SP19. I'd really appreciate any suggestion of how to solve my issue.
    Thank you
    Manuel

    Hi Prabhu,
      I've already tried to restart server, but nothing happened. (Before update to SP19, the interface worked well).
    This is the error log from message monitoring:
    <i> 2007-01-16 16:37:34 Success Channel cc_File_Snd_Bolle: Entire file content converted to XML format
    2007-01-16 16:37:34 Success Send binary file  "BOLLE_20061229142059.CSV" from FTP server "AS810T:/sapinbound", size 8733 bytes with QoS EOIO
    2007-01-16 16:37:34 Success Application attempting to send an XI message asynchronously using connection AFW.
    2007-01-16 16:37:34 Success Trying to put the message into the send queue.
    2007-01-16 16:37:35 Success Message successfully put into the queue.
    2007-01-16 16:37:35 Success The application sent the message asynchronously using connection AFW. Returning to application.
    2007-01-16 16:37:35 Success The message was successfully retrieved from the send queue.
    2007-01-16 16:37:35 Success File "BOLLE_20061229142059.CSV" successfully archived on FTP server "AS810T" as "/sapinbound/bolle/20070116-163735-245_BOLLE_20061229142059.CSV"
    2007-01-16 16:37:35 Success The message status set to DLNG.
    <b>2007-01-16 16:37:35 Error Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText:   ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,
    2007-01-16 16:37:35 Error Transmitting the message to endpoint http://SERVERNAME:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: INBOUND_BINDING_ERROR:. </b>
    2007-01-16 16:37:35 Success The asynchronous message was successfully scheduled to be delivered at Tue Jan 16 16:42:35 CET 2007.
    2007-01-16 16:37:35 Success The message status set to WAIT.
    2007-01-16 16:42:35 Success Retrying to send message. Retry: 1</i>
    After this, the system try to resend the message, and the same error appears several times.
    Ty,
    Manuel

  • Receiver  Mail adapter Error

    HI  All
       i    am doing   a   scenario     SFTP    to mail adapter,   i  am sending  a    file    to    SFTP ADAPTER  and   Mail adapter   send  the   mail  to    clint,   i am   using  java  mapping ,   i  have  checked  the message in    RWB  mesage  is    fail   in mail adapte,
       ERROR  :   Message processing failed. Cause: java.lang.Exception: java.io.IOException: server does not support PLAIN or LOGIN authentication
      anyone  suggest  me     soloution?

    Hi Pankaj,
    Remove your mail server user id and password and keep authentication mode as Plain and try in mail adapter configuration.
    You can try accessing ID from within IR via menu options or via a direct URL.
    Thanks,

  • TNS-12560: TNSrotocol adapter error

    Iu2019m installing SAP ERP 6.0 on a Windows server 2008 with Oracle 10.2.0.4.0.
    First of all I installed the Oracle software by means of Oracle Universal Installer.Then I used the Sapinst tool. At the step u201CConfigure Oracle server Networku201D I get an error. In the lsnrctl.log file I can read:
    TNS-12560: TNSrotocol adapter error
    TNS-00530: Protocol adapter error
    These are my .ora files in the path <oracle-home>\NETWORK\ADMIN::
    1 )LISTENER.ORA
    ADMIN_RESTRICTIONS_LISTENER = on
    LISTENER =
    (ADDRESS_LIST =
    (ADDRESS =
    (PROTOCOL = IPC)
    (KEY = DEV.WORLD)
    (ADDRESS=
    (PROTOCOL = IPC)
    (KEY = DEV)
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = SAP-BTdemo)
    (PORT = 1527)
    STARTUP_WAIT_TIME_LISTENER = 0
    CONNECT_TIMEOUT_LISTENER = 10
    TRACE_LEVEL_LISTENER = OFF
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = DEV)
    (ORACLE_HOME = F:\oracle\DEV\102)
    2) SQLnet.ora:
    AUTOMATIC_IPC = ON
    TRACE_LEVEL_CLIENT = OFF
    NAMES.DEFAULT_DOMAIN = WORLD
    05.01.06 unsorported parameter now
    #NAME.DEFAULT_ZONE = WORLD
    05.01.06 set the default to 10
    SQLNET.EXPIRE_TIME = 10
    SQLNET.AUTHENTICATION_SERVICES = (NTS)
    05.01.06 set to default
    #TCP.NODELAY=YES
    05.01.06 set to 32768
    DEFAULT_SDU_SIZE=32768
    3) tnsname.ora:
    DEV.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = SAP-BTdemo)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = DEV)
    (GLOBAL_NAME = DEV.WORLD)
    I have set the following Environment Variables:
    u2022 ORACLE_HOME = F:\oracle\DEV\102
    u2022 ORACLE _SID= DEV
    u2022 TNS_ADMIN= F:\oracle\DEV\102\NETWORK\ADMIN
    I have installed Oracle by Universal Installer and, in the Server Manager, I got only the following Oracle Service:
    OracleDEV102iSQL*Plus
    If I use the command lsnrctl start from Windows prompt I get the same error.
    Can anyone help me?

    Ok, I made all the things that you say: installed Oracle sw, installed the Opatch end started SAPinst.
    But SAPinst stops when configuring oracle server network. I really don't understand what to do. If i write the command of LSNRCTL and tnsping the DEV (my DBsid) i have the following error:
    LSNRCTL> services
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 2: No such file or directory
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 2: No such file or directory
    Connecting to (ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=10.32.33.4)(PORT
    =1527))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 61: Unknown error
    LSNRCTL> status
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 2: No such file or directory
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 2: No such file or directory
    Connecting to (ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=10.32.33.4)(PORT
    =1527))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       64-bit Windows Error: 61: Unknown error
    C:\SAPinst>tnsping DEV
    TNS Ping Utility for 64-bit Windows: Version 10.2.0.4.0 - Production on 27-OCT-2
    010 14:11:45
    Copyright (c) 1997,  2007, Oracle.  All rights reserved.
    Used parameter files:
    F:\oracle\DEV\102\NETWORK\ADMIN\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP
    .WORLD) (PROTOCOL = TCP) (HOST = 10.32.33.4) (PORT = 1527))) (CONNECT_DATA = (SI
    D = DEV) (GLOBAL_NAME = DEV.WORLD)))
    TNS-12541: TNS:no listener
    Why isn't SAPINST able to use the listener??
    Edited by: Paolo Rubino on Oct 27, 2010 3:16 PM

Maybe you are looking for