Error in the following service com.sap.aii.af.ra.ms.impl.core.archiving.exe

Does anyone know what this error might be?
Details for 'Is the Adapter Engine running?'
==== Events on Server 19010950 ====
Adapter Engine, message: Fatal RecoverJob (Default Recover Job) failed.
(Details: Code: MS.JOB.RECOVER, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.RecoverExecutor, Reason: java.lang.Exception: Failed to restart message ddc46f41-bdad-7cf1-b918-001b7832810c(INBOUND) remotely on cluster node 19011150. Reason: Could not execute cluster event, due to: Service"com.sap.aii.af.ms.svc"on cluster element 19,011,150 thrown an exception in receiveWait(), invoked by a request by cluster element 19,010,950., Time: 07.12.2008 10:00:00)
==== Events on Server 15965050 ====
Adapter Engine, message: Fatal Message listener localejbs/CIDXMessageListener could not be created for connection CIDXAdapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Adapter Engine, message: Fatal Message listener localejbs/RNIFMessageListener could not be created for connection RNIFAdapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Adapter Engine, message: Fatal Message listener localejbs/RNIF11MessageListener could not be created for connection RNIF11Adapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Reset event protocol:http://nytsappip.nyhq.nytint.com:50100/MessagingSystem/performance?resetSystemMatrixInCluster

Resolved in thread: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol ha

Similar Messages

Service com.sap.aii* does not in service list for PI Post installation

Hi Experts,
When I check the PI post installation, in my visual admin Cluster->Server->Service->Delpoy (Application)
the required service "com.sap.aii* and com.sap.xi*" does not exist in the list. How to deploy these mandatory services to my J2EE server, thanks a lot!
Fil

Check this thread..
Re: Web Service call through XI returns SAP error( QName is 'xmlns'.....)
SAP Note: 886888
Regards
Anand

When i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

Hi, Michal
I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
Q1: I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
Q2: The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
1.Builder for Integration Repository
2.Builder for Integration Configuration
3.System Landscape Directory
4.Runtime Workbench
5.Administration System (for Repository, Directory, Runtime)
Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
For more details about my SAP-XI, please access the following Web page:
http://iccxi.sap.com:58000/rep/support/admin/index.html
Q3: The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-19 05:12:16 Success Message successfully put into the queue.
2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
2006-06-19 05:12:16 Success The message status set to DLNG.
2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
2006-06-19 05:12:16 Success SOAP: request message entering the adapter
2006-06-19 05:12:37 Success SOAP: call failed
2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
Thanks
Menghua Li

Unable to start service 'com.sap.aii.adapter.jms.svc'

Hi people,
After I have successfully deployed the external drivers jdbc/jms drivers on a PI 7.1 system trough JSPM using the com.sap.aii.adapter.lib.sda file but now the com.sap.aii.adapter.jms.svc and the com.sap.aii.adapter.jdbc.svc do not want to start up. When checking the log DefaulTrace log file I found the following error Reported reason: Service com.sap.aii.adapter.jms.svc is not loaded Any ideas on what the problem could be?

Hi people,
Thanks for all the ideas. I have followed all the notes and guides to prepare the SDA file ie editing the XML file and adding the JAR files.
The problem was that somewhere along the line the provider.xml file of the old aii_af_jmsproviderlib.sda and the new com.sap.aii.adapter.lib.sda file seeming ot "merged" during my struggles.
The provider.xml file of the SDA which I tried to uploaded had the two reference entries which actually belong to the old aii_af_jmsproviderlib.sda in as well as the correct reference entry. Once I removed these incorrect reference entries the services started up correctly.
I found the error mention above by firstly renaming the DefaultTrace_X.trc file and restarting the JAVA stack. I then stepped through each line of the newly created DefaultTrace_X.trc file from the top down and found the following entries:
1) Cannot resolve component library:sap.com/com.sap.aii.adapter.lib because referenced component Reference strong to library com.sap.aii.messaging.runtime not found#
2) Cannot resolve component service:sap.com/com.sap.aii.adapter.jdbc.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
3) Cannot resolve component service:sap.com/com.sap.aii.adapter.jms.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
In line line 1 I saw that it was referencing the com.sap.aii.messaging.runtime which seemed suspect. Luckily I still had the original SDA file and when comparing it to the uploaded SDA file I found the incorrect entry.
Thanks again for all the help

Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWExc

Hello All,
Does anyone know what this message means? All our programs using RFC to send data to another system is encountering error below. Please help.
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'ZBS_R3BACKEND2'/'CC_MQ_Rfc_Outbound', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QAS#100' returned party/service of ''/'ZBS_R3BACKEND')
Regards,
Alfred

Hi
have u configured the Bussiness System with correct client which u r trying to connect?
check if u have imported RFC from right client.
rgds
srini

File does not Upload ! Error in the listener class com.sap.ip.portal...

Hello.
Recently, I Add a New Server Node on Java Central Instance.
And Java Program Upload on Portal, then following error occured.
Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of
handleTopic
Original server node can upload successfully.
But, An error happens in New Additional node.
Please tell me way to resolve the error.
Regards.
Edited by: Masashi Fujita on Dec 24, 2008 5:29 AM
Edited by: Masashi Fujita on Dec 25, 2008 7:20 AM

Hi Masashi Fujita,
Check this Link for Uploading and Downloading files using Web Dynpro Java.
[Uploading and Downloading Files in Web Dynpro Java|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00062266-3aa9-2910-d485-f1088c3a4d71]
[Upload Files Using Web Service in Web Dynpro Java Application|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0d9336b-b4cf-2910-bdbf-b00d89bd2929]
[Uploading and Downloading Files in Web Dynpro Tables|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0e10426-77ca-2910-7eb5-d7d8982cb83f]
Thanks & Regards,
Sharma Kvbk.

Where is the directory for "com.sap.aii.adapter.lib.sda" - PI 7.1 ?

Hi,
I want to install new JDBC driver in PI 7.1 EHP1, base on notes 1138877 i have to modified file "com.sap.aii.adapter.lib.sda".
please advise in which directory the file is ?
Best Regards
Fernand

Hi
you can go to the drive in which your PI is installed for example if it is E then path will be like
E:/usr/sap/<SID>/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib
copy this file on your local desktop unzip it using winzip and add the driver jar to this
make the entry of your driver jar file in provider.xml file and again zip the folder
then using SDM deploy this file
for complete process search on SDN "how to install and configure external drivers for jDBC and JMS"
Thanks
sandeep

RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication

Have a RFC interface between Sap R/3 and XI. Submit RFC request: call function 'Z_PGM'
 in background task
 destination 'XID'
 tables
 it_zmsfi_labels = t_table.
Getting error in SM58 in R/3 : Commit fault com.sap.aii.af.rfc.afcommunication.Rf cAFWException: alternat
Message no. SR053
Any ideas? If I do test connection on in SM59 on TCP connection it's Ok.

call function 'Z_PGM'
in background task
destination 'XID'
tables
it_zmsfi_labels = t_table.
COMMIT WORK.
This should solve your problem.
regards
SKM

Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

Hello,
In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
com.sap.aii.adapter.lib_api.jar
com.ibm.ws.ejb.thinclient_7.0.0.jar
com.ibm.ws.orb_7.0.0.jar
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
com.ibm.ws.runtime.jar
javax.j2ee.jms.jar
The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
Checking dev_server0 file I found the following error.
==============================================================================================
Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure that any
bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than
an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
on.
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
port=2809 vmcid: 0x4942f000 minor code: 3586 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
... 6 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809 vmcid: 0x4942f0
00 minor code: 3586 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 16 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:522)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:180)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 28 more
Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure t
hat any bootstrap address information in the URL is correct and that the target name server is running. Possible causes othe
r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
iguration.
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor co
de: 775 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
... 7 more
Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor code: 775 completed: No
at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 17 more
==============================================================================================
Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
Thank you in advance.
Roger Allué i Vall

Hi Roger,
we also experience the same issue and would be very keen to understand how you resolved this problem.
Many thanks.
Dieter

What jar for com.sap.aii.mapping is

Dear
i am testing with blow blog.
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
in this blog, java program use the following;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformationConstants;
what .jar file name is?
i could not find com.sap.aii.mapping on eclipse.
thanks
Denis

Denis,
You need the aii_map_api.jar file for this.
You will get this in the following location on your XI server,
j2ee\cluster\server0\apps\sap.com\com.sap.xi.services
Upload the Jar, in your Project Build Path.
Regards,
Bhavesh

Resource com.sap.aii.af.svc with type service, not active on the server

Hi Forum,
in my X1 server, in rwb, it gave error:
HTTP request failed. Error code: "503". Error message: "Service Unavailable [http://xyz:50000/AdapterFramework/rtc,
on further analysis we find that:
 Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Application sap.com/com.sap.xi.mdt cannot be started. Reason: it has hard reference to resource com.sap.aii.af.svc with type service, which is not active on the server.
and the service/component com.sap.aii.af.svc is not present as the error says,
In visual admin, in the services list i couldnt find this particular resource,
pls instruct me how to deploy/start this service com.sap.aii.af.svc ,

Hi,
Please check out the user authorization and role and also check that you are maintaining the passwords in all places where required.
Regards
Aashish Sinha
PS : reward points if helpful

Error message "com.sap.aii.af.ra.ms.api.DeliveryException: "

Hi Team,
Created a simple file2file scenarion successfully. Unable to pick the file from Sender directory to Receiver Directory.
Checked from monitoring the Communication Channel.
Error message shown for sender communication channel as below:
Communication Channel Status   Short Log                                Control Data   Party Service           Adapter Type Direction
sen_cc                 Red ball Processing Errors In the Last 30 Seconds Manually             kanchuf2f_sen_bs   File         Sender
Line 1 / 1
By selecting the sender communication channel "sen_cc", below is the node details given.
Processing Details for Cluster Node Server 0 1_54295
Type
Time Stamp         Message ID                           Explanation
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Retry interval started. Length: 60.0 seconds
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
By clicking on the first Message ID, The message says successful upto some point and give error says JCO COMMUNICATION FAILURE and RFC issue.
Below is the information provided in detail.
Audit Log for Message: 45f841be-a421-43bd-235a-c7ad19b0aec8
Time Stamp          Status Description
03.12.2008 08:20:00 Success Channel sen_cc: Send binary file "f:\xi_file\sender\f2fmap.xml". Size 210 with QoS BE
03.12.2008 08:20:00 Success Application attempting to send an XI message synchronously using connection AFW.
03.12.2008 08:20:00 Success Trying to put the message into the call queue.
03.12.2008 08:20:00 Success Message successfully put into the queue.
03.12.2008 08:20:00 Success The message was successfully retrieved from the call queue.
03.12.2008 08:20:00 Success The message status set to DLNG.
03.12.2008 08:20:01 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error Transmitting the message using connection http://sitaserv33:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error The message status set to FAIL.
03.12.2008 08:20:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
Page 1 / 2
I think this could be the problem with some basis related settings, I am not sure what exactly the issue with.
Any idea what exactly the error is talking about please do help me in finding the solution to thresolve this error message.
Regards,
Venkat Ramana K

Hi Carlos,
Thank you for the quick information.
Followed all the steps and also basis person from onsite restarted the XI server.
Now, I am able to log onto XI with the login Id but, when I give Tr Code: SXMB_IFR, unable to open the browser that shows Integration Builder.
Getting the error message.
*500   Internal Server Error*
                                                                                *SAP J2EE Engine/7.00*
**Exception**
*An internal error occurred. Contact you XI administrator*
*Unable to read configuration data (ExchangeProfile/aii.properties)*
Error Details, Error History, Build Info, Generic Application Info
Regards,
Venkat Ramana K

Pkg com.sap.aii.proxy.framework.core don't exist even added in the JRE path

Hi All,
I am facing some error while activating the activity. I have checked-in the activity but getting the error while trying to activated the activity. there are two DC's in one of them i am gettign this error. i have not noticed this while check-in.
After checked in - i am not getting the any such option --Revert activitty or delete activity.
This activity is alreday closed.. what i can do with this activity?? After this error i am not able to activate any activity. I am getting the below error in all the activity.
package com.sap.aii.proxy.framework.core does not exist even though i have added this into the JRE path in NWDS. Do i need to import the same version file somewhere into J2ee server or somewhere else??
Regards,
Narpal

Hi,
javac ERROR: class file has wrong version 49.0, should be 48.0
This error means that the class file in question is being built with JDK1.5 (49), however it should be built with JDK1.4.2 (48).
In other words, as per the class the build expects a class file built with 1.4.2, but in your track JDK1.5 is configured for the build tool.
You need to therefore :
A.) review the CBS service settings, as most likely the parameters BUILDT_TOOL_JDK_HOME and JDK_HOME_PATHS are set up improperly.
B.) plus the build variant is incorrect in the track in question.
I'll refer below to the corresponding points with the letters A and B.
Some more explanation on the error:
If you check any class file with a hex editor, you'll see at the beginning of it this:
example: CA FE BA BE | 00 00 |00 31 ...
JDK 1.6 = 50 (0x32 hex)
JDK 1.5 = 49 (0x31 hex = (161)*3 + (160)*1 = 49)
JDK 1.4 = 48 (0x30 hex)
JDK 1.3 = 47 (0x2F hex)
JDK 1.2 = 46 (0x2E hex)
JDK 1.1 = 45 (0x2D hex)
On the first 4 bytes there's a magic number (CAFEBABE) which ensures this is a java class file, then on 2-2 bytes you'll see the minor and the major version (in this order). In the above example 00 00 | 00 31. This is what displayed as major.minor i.e. 49.0 what you can see in error messages. See also the attachment I've put to this thread minormajor.JPG.
More information on the class file structure:
http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html
For point A)
See the guide for doublechecking the CBS parameters
help.sap.com u2013 CBS Service Properties
http://help.sap.com/saphelp_nw70/helpdata/EN/53/75b3407e73c57fe10000000a1550b0/frameset.htm
Further explanation to the paramters
BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS
BUILD_TOOL_JDK_HOME = <path to highest JDK>
JDK_HOME_PATHS = JDK1.3.1_HOME=<path of jdk131>;JDK1.4.2_HOME=<path of jdk142>;JDK1.5.0_HOME=<path of jdk150>JDK1.6.0_HOME=<path of jdk160>;default=<path of the JDK as default>
Some simple rules with examples:
- for BUILD_TOOL_JDK_HOME you simply enter the path to your JDK, e.g.: /opt/IBMJava2-amd64-142
- for JDK_HOME_PATHS you have to follow the scheme "key=value" e.g.: JDK_1.4.2_HOME=/opt/IBMJava2-amd64-142
- for BUILD_TOOL_JDK_HOME you always specify the highest JDK,
- for JDK_HOME_PATHS you list the available JDKs.
- JRE is not allowed, specify always JDK!
For point B)
Regarding the build variant in your track: check the page 13 for the paramter com.sap.jdk.home_path_key as per the guide :
How To... Setup an NWDI Track for Composition Environment Developments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f
Summary:
A. The first part of the solution is then to doublecheck the CBS service parameters. CBS service must be restarted after changes.
B. The second part is to doublecheck the build variant in the track (see the Build Variants tab on the Track Data tab on the CMS webui - Landscape Configurator).
I recommend you to have
A) BUILD_TOOL_JDK_HOME = <highest available JDK, I recommend here to set the path to JDK1.5>
JDK_HOME_PATHS = JDK1.4.2_HOME=<path of jdk142>;JDK1.5.0_HOME=<path of jdk150>;default=<path of the JDK as default, set it to the same path as you did for 1.4.2_HOME>
B) set the com.sap.jdk.home_path_key in the build variant to 1.4.2_HOME, or leave it for the default. Do not forget to set this build variant explicitly for >= 7.1 tracks to JDK1.5.0_HOME
I hope this helps.
Best Regards,
Ervin

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

RFC Error : Commit fault: com.sap.aii.af.rfc.afcommunication

Hi ,
I am having a problem in a RFC to File scenario. My Sender RFC is working fine and is showing the status green in the CC Monitoring in AdapterEngine under Component Monitoring. But we are trying to trigger the data to the RFC we are getting the following error "Commit fault: com.sap.aii.af.rfc.afcommunication.R
fcAFWException: alterna "
The RFC connection when tested it is ok .. the connection is established.
Please suggest.
Regards,
Hemanthika

Hi,
1. Refer to the following notes
SAP Note 730870
SAP Note 775765
Also check
RFC Error in SM58 Commit fault
RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication
2. have a look to R/3 transaction SM58 to find your message
Thanks
swarup

Error in the following service com.sap.aii.af.ra.ms.impl.core.archiving.exe

Similar Messages

Maybe you are looking for