Error on Adapter Framework with Seeburger component

Hi,
I have the Generic EDI component from Seeburger Adapter, and I have a communication channel using the FTP Adapter from Seeburger with the module localejbs/Seeburger/solution/generic-edi, and when execute the communication channel, I have an error with the solution, the error is:
"Exception caught by adapter framework: Path to object does not exist at solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.".
I see the Seeburger documentation about installation and configuration from FTP Adapter, but I don´t find information about this error, somebody help me please with information about this error, what configuration I need review or where find documentation about this problem?.
We post a note about this problem on the OSS, the content of the note is:
We have installed the Seeburger's FTP adapter in SAP XI.
A communication Channel is calling this adapter nd executing a module called localejbs/Seeburger/solution/generic-edi. When the adapter is called the next error is shown;
Exception caught by adapter framework: Path to object does not exist at
solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.
Delivery of the message to the application using connection
FTP_http://seeburger.com/xi failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not
exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi.:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi..
Also, the host-ftp solution was used instead of the generic-edi with the same result.
The system we have is SAP PI 7.0 SPS09 with Seeburger 1.6.
Thanks and greetings,
Hervey.

Hi,
I have the same problem. What was the solution?
Regards
Kristian

Similar Messages

Error in Control Framework with GUI_DOWNLOAD FM

Dear All,
I am using GUI_DOWNLOAD FM to download a file in PDF format to presentation server.
The code has been written in an enhancement spot in a class "/SCA/CL_SVORDER", method "Print" on an SNC server.
On execution I get the error "Error in Control Framework".
First I tht that this has something to do with the data table. But when I tried to pass a simple table of Integers in ASC format, it gave the same error.
Please assist.
*----Begin of Code Snippet
data: fullpath type STRING value 'D:\temp\PO.pdf',
bin_filesize type I,
filetype type char10 value 'BIN'.
bin_filesize = numbytes.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
   BIN_FILESIZE                    = bin_filesize
    filename                        = fullpath
   FILETYPE                        = filetype
IMPORTING
FILELENGTH                      =
tables
    data_tab                        = t_data
FIELDNAMES                      =
EXCEPTIONS
   FILE_WRITE_ERROR                = 1
   NO_BATCH                        = 2
   GUI_REFUSE_FILETRANSFER         = 3
   INVALID_TYPE                    = 4
   NO_AUTHORITY                    = 5
   UNKNOWN_ERROR                   = 6
   HEADER_NOT_ALLOWED              = 7
   SEPARATOR_NOT_ALLOWED           = 8
   FILESIZE_NOT_ALLOWED            = 9
   HEADER_TOO_LONG                 = 10
   DP_ERROR_CREATE                 = 11
   DP_ERROR_SEND                   = 12
   DP_ERROR_WRITE                  = 13
   UNKNOWN_DP_ERROR                = 14
   ACCESS_DENIED                   = 15
   DP_OUT_OF_MEMORY                = 16
   DISK_FULL                       = 17
   DP_TIMEOUT                      = 18
   FILE_NOT_FOUND                  = 19
   DATAPROVIDER_EXCEPTION          = 20
   CONTROL_FLUSH_ERROR             = 21
   OTHERS                          = 22
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*----End of Code Snippet

Hi!
I have the same error, but i need to use CSV Format.
in another program, i used this with XML format.
lv_xml = lr_element->to_xml( ).
Converts the string to xstring
lv_xxml = wd_this->convert_file( lv_xml ).
Shows it in a new browser window
*cl_wd_runtime_services=>attach_file_to_response(*
    *i_filename      = lco_filename*
    *i_content       = lv_xxml*
    *i_mime_type     = lco_mime_type*
    *i_in_new_window = abap_FALSE*
    *i_inplace       = abap_false ).*
Regards!

Error in Adapter FrameWork

Dear All,
While doinf File to File scenerio, i m getting following error in Mesage Monitoring in Runtime Workbench "Transmitting the message to endpoint http://trexserver:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 403.."
Plz tell me what this error is all about and how this can be solved.
Reg,
nishu

Hi Nishu,
Just check the mentioned possibilities for your error one by one:
1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
4.can you also try the following;
Visual Admin -> start the service,
"com.sap.aii.af.ms.app".
Please go through the followings links also :
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
I hope the info provided help you solve your problem.
Regards,
Abhy

XI ERROR IN ADAPTER FRAMEWORK

HI All,
we are getting the below error message
ERROR:
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE:
Connection pool RfcClient[CC_BS_ECDCLNT130_RFCLookup]174f31f5971337d6af4e1e49826d9077 is exhausted.
The current pool size limit (max connections) is 1 connections.
Please help me in solving this.
Thanks:
Giridhar N

Please check this links:
Re: Connection pool exausted
http://help.sap.com/saphelp_nw04/Helpdata/EN/f6/daea401675752ae10000000a155106/content.htm
Thank you,
Shyam

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.

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

Problems with Seeburger FTP Receiver adapter

Hello,
I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
Hostname <Hostname of our FTP server>
Port <Port # of our FTP server>
Host Path/VAN partner id <some local directory of FTP server>
Payload mode: Maindocument.
At runtime i received following exception
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
Few questions related to this
1] can we use Seeburger adapter to generate EDI files on local FTP server
2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
Any idea how to generate EDI files with Seeburger FTP on test server?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
> 1] can we use Seeburger adapter to generate EDI files on local FTP server
Yes we can use.
> Any idea how to generate EDI files with Seeburger FTP on test server?
It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
BIC
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Regards
Ramesh

Client Auth and SSL with Seeburger AS2 adapter

Hello All,
We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.
and I hope that you will be able to help me out.
1. Server SSL on Receiver AS2 adapter
I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.
This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.
The issue here is :
Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.
Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.
I am using a Decentral Adapter Engine with LoadBalancer.
2. Client Auth on Receiver AS2 Adapter
I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.
XI error's with the error "SSL handshake failed - Bad Certificate" .
I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,
Server Certificate ( Keystore) and Private Key for Client Authentication.
Has anyone tried this? If further details are needed, I will be able to furnish the same.
Regards,
Bhavesh

Hello Jens,
Thanks for your reply.
1. The Encryption and Signature part of the Interface is working absolutely fine and I use the same concept highlighted by you - The Sender always signs the message with his private key and encrypts with message with the partner's public key in the corresponding agreement.
2. Server SSL is also working perfectly fine, i.e, when XI initiates the connection the SSL connection is established to the partner.
3. Mutual Auth was the issue where I was getting the bad certificate issue.
To investigate further I moved the same setup to my Central Adapter Engine and all the issues I had described above seem to have vanished and things work exactly as I was expecting, ie.
The field : Server Certificate (Keystore) is used to provide the Target System's Server SSL's public Certificate.
The field : Private Key for Client Authentication is used where XI provides its own Server SSL's private key for Mutual / Client Authentication.
The problem seems to be with my Decentral Adapter engine and not my central adapter engine and so I guess,
1. I either have the incorrect certificates on my Decentral Adapter Engine.
2. I also have 2 instances of a Decentral Adapter Engine with a Webdispatcher and so maybe the 2 Visual Admin's of the 2 Decentral AE are inconsistent.
3. Maybe it was just a long day and I did something wrong
Will investigate further for the root cause but I am glad that my concepts remain intact and things do work as I expected them to work.
A blog on all this is on the cards sometime soon.
Cheers,
Bhavesh

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Regarding error showing as exception caught by adapter framework

hi all.
here in my scenario iam doing a file to rfc.
but when iam sending a file to rfc and when i see in sxmb_moni its showing as sucess.
bue when i look at runtime workbench under message monitoring (tab) it was showing as
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
SO WHAT COULD BE THE ERROR IS THE EROR THAT WS SHOWING RELATED TO XI R SAP R3(system that was recieving)
waiting for the excellent answer.
cheers.
seeta ram.

HI Matias.
yes i did with the custom Rfc and the result is still the same
and to be more confident i was creates another xi scenario from file to Standerd Bapi BAPI_COMPANYCODE_GETDETAIL by creating a simple file with only one field and mappedwith only the request Message type of this Bapi and tested it.
and even this scenario is also showing the same in reciever rfc and under runtime work ench its showing the same as my old scenario and it is as follows
2007-10-15 10:47:51 Success Message successfully received by messaging system. Profile: XI URL: http://jssxid0:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2007-10-15 10:47:51 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-10-15 10:47:51 Success Message successfully put into the queue.
2007-10-15 10:47:51 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:47:51 Success The message status set to DLNG.
2007-10-15 10:47:51 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:47:51 Success MP: entering
2007-10-15 10:47:51 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:47:51 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
2007-10-15 10:47:51 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
Time Stamp Status Description
2007-10-15 10:47:51 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
2007-10-15 10:47:51 Success The asynchronous message was successfully scheduled to be delivered at Mon Oct 15 10:52:51 SAST 2007.
2007-10-15 10:47:52 Success The message status set to WAIT.
2007-10-15 10:52:52 Success Retrying to deliver message to the application. Retry: 1
2007-10-15 10:52:52 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:52:52 Success The message status set to DLNG.
2007-10-15 10:52:52 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:52:52 Success MP: entering
2007-10-15 10:52:52 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:52:52 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
and the message in sxmb_moni shows as it is processed sucessfully and
at reciever rfc as
Receiver channel 'ReceieverChannel_RFC' for party '', service 'CD103' (internal name 'RfcClient[ReceieverChannel_RFC]')
Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Current pool size: 0, maximum pool size : 1
waiting for your great answer.
cheers.
seeta ram.

Error when creating a Report with Form component

I am trying to create a new report with form component but when I try to choose the Table/View name I get a web error "404 web not found". I know for a fact that the list is working because I see the list when I create a "simple form". Is this a bug or i need to do something to get it working? thanks

419008,
It is a bug that has been identified and will be corrected in an HTML DB patch. There is nothing you can do to correct it.
This bug is specific to Internet Explorer and utf-8 encoding. It is not a bug with IE, it is a bug with how we handle this for IE.
Joel

Problem with Adapter Framework

Hello All,
Our env. is XI 3.0 and for our development system all the interfaces which are connecting to R3service are getting failed .
And the audit log for one of the interface is shows
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Can any one help me out to resolve this issue..
Best Regards
Raki

Hello Barry,
Thanks for the update.
The issue has been resolved by applying two more patches of SPS19.
Problem Resolution:
When we apply only one patch Adapter Frame Work Core (SAPXIAFC19P_19-20000272.SCA (Adapter Framework Core 19)), there is chance for some sort of inconsistences in the system and the interfaces relating to Adapter Frame work gets failed from reciever end(R3services).
To avoid such problems (inconsistences) we need to apply the patches which are related to that.And those are .
SAPXIAF19P_9-20000273.SCA Adapter Framework for SP19.
SAPXITOOL19P_10-20000274.SCA) Cumulative Patch tool for SP19
Thanks for all helping me out to resolve the problem earliest.
Best Regards
Raki

Error in JMS receiver adapter: "Error creating initial context with environment"

Hello,
I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
The message in adapter monitoring is:
A channel error occurred. Detailed error (if any) :
com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
(JndiConnectorImpl.java:152)<br> ....
Message processing failed. Cause:
com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
Might there be a problem with the JMS drivers?
Regards,
Marcus

Hi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

Issues with Seeburger FTP adapter

Can one of you with Seeburger FTP adapter experience share some information on these issues I'm facing
1. Do I need to setup resource management in Seeburger workbench. If so, do I need to configure, resource, server and reservations. Do you have more information and what parameters I need here.
2. In the Seebuger FTP adapter, I have
Module Key - exit
Parameter Name - JNDIName
Paramter Valu - deployedAdapters/SeeXIFTP/shareable/SeeXIFTP
JNDIName, should I be replacing this with some other name. I'm trying to get Seeburger FTP to work and in the messaging monitor, I see the message as passed to Module Processor but it does go anywhere from there.
Can one you throw some light on this subject...what to expect from this definition.
Thank you for all your replies,
Parimala

I'm resending this since I did not have any luck with it the first time.
We also have an oss note waiting to be responded on this subject.
When I send messages using Seebuger FTP adapter, I see the following information in the SAP message monitor -
"Message entered module processor exit bean and will be transferred to JCA adapter".
But does not get to IBM VAN mailbox. How do I trace from this point onwards.
Should I use Seeburger monitoring tool for this? If so, I don't see anything in Seeburger monitoring (used all criteria).
Please let me know if you have any information on this subject.
Thanks,
Parimala

Error when make controller with MVC entity framework

error when make MVC with entity framework, WHY??

Hi Arif Kalbu,
It would be better if you could share us the detailed error message, so I could provide useful informaiton or provide the correct forum for this issue, you know that this forum is to discuss the VS IDE.
But if the real issue is related to the MVC project, maybe the ASP.net forum would be better: http://forums.asp.net. If then, you could get an answer more quickly and professional. Thanks for your cooperation.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error on Adapter Framework with Seeburger component

Similar Messages

Maybe you are looking for