Lookup of alternativeServiceIdentifier via CPA-cache failed for channel

Hi,
In RFC(ECC) to File(PI) scenaio i am facing the following error in sender CC:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
I have done the following for RFC to File scenario:
ECC side:
1. Created a RFC and tagged it to BAPI
2. In the ABAP program, i am calling the RFC like below:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
EXPORTING
INTERFACE =
IMPORTING
FILENAME = FILENAME
RETURN = RETURN
TABLES
ITAB10 = ITAB10
P_STATUS = P_STATUS
COMMIT WORK.
3. Created a RFC destination using SM59
RFC detination : Z_HR_OUTBOUND_DATA2
Connection type : TCP/IP
Enabled Registered Server Program
Program ID : ECCTOPI_OUTBOUND
Gateway host : ECC's host number
Gateway service : ECC's service number.
In PI side:
I have created :
1 DT for File Rcvr
1 MT for File Rcvr
1 SI for File Rcvr (async)
1 MM (sender RFC and receiver File)
1 OM
1 CC with RFc as sender with the following parameters:
Communication component : ECC's component
application server (gateway) : ecc's gateway
application server service(Gateway) : ecc's service number
Program id : ECCTOPI_OUTBOUND
inital connections 1
max. connections 1
And also gave ecc's details in application server , s/y number, auth. mode, logon user ,
pwd, ecc's client number
1 CC with File adapter and file content conversion
1 receiver determination
1 interface determination
1 sender agreement
1 receiver agreement
When i am executing the ABAP program in R/3 I am getting the following error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
Please let me know if any of my steps are wrong and how to rectify this error and make
the scenario working.
Thanks for your help.

I have mentioned the Adapter specific parameters properly.
It contains :
For ECC s/y(i.e for RFC)
   Logical system : DECCLNT120
   R/3 system ID : DEC
   Client 120
For PI (i.e for File)
   Logical system : DPICLNT100
   R/3 system ID : DPI
   Client 100
Since i am sending the Response of the RFc to the file, i have used a Service interface where i am passing the RFC.Response as Request.
if i am passing the RFC directly as i/p in Source operation of Operation mapping then it doesn't pick up the response in the souce message of the mapping program present in Operation mapping.
So i am passing the same SI_Sender_RFC in the Sender Agreement and it gives the error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'DEC_RFC', toParty '', toService '', interface 'Z_HR_OUTBOUND_DATA2', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (channelId c78f5a88787131a09384c07c2db0e93b)
why is it so?

Similar Messages

RFC Sender - lookup of alternativeServiceIdentifier via CPA-cache failed

Hello,
I am using RFC Sender for a scenario and while sending message I got following error. I found this error while monitoring communication channel. I looked at several posting on this issue and tried with both checking and not checking check box of advanced mode (RFC sender communication channel configuration). I am getting the same "lookup of alternativeServiceIdentifier via CPA-cache failed" error. How did you resolved?, please let meknow.
Did any one come across error
Server 0 0_50478 Sender channel 'CC_GET_CUSTOMER_RFC_SENDER' for party '', service 'SAP_DFR' (internal name 'RfcServer[CC_GET_CUSTOMER_RFC_SENDER]')
Server data: {jco.server.gwhost=XXXXXXXXXX, jco.server.progid=DFX_XI_00, jco.server.gwserv=sapgw00, XI_RFC_USER=*****, jco.server.unicode=0}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=XI_RFC_USER, jco.client.sysnr=00, jco.client.ashost=XXXXXXXXXX}
Current pool size: 1, maximum pool size : 1
Channel History
- Error: 2007-09-20 10:32:14 CDT: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_GET_CUSTOMER_RFC_SENDER' (bee9e190f51f3687b1072bf3f5446a70, party '', schema 'TechnicalSystem', identifier 'DFR#120')
Thank you,
Balaji

run tc SXI_cache on the XI
on that screen press Shift+f6, it will start the refresh....and also do the CPAcahe manually trough the link
http://itmisapxi:50000/CPACache/refresh?mode=full
with PIRDIRUSER and then check the interfce....

"senderAgreement not found: lookup of binding via CPA-cache failed for..."

Hi,
     I have configured asynchronous sender RFC to JDBC scenario and when I execute RFC I get short dump "senderAgreement not found: lookup of binding via CPA-cache failed for..."
     My scenario configurations, RFC destination, are all okey..
A Hint:
     Our XI Server is "LARA"
     Our R/3 4.6C Server is "ZULIA"
This are the RFC Sender Communication Channel on LARA:
     RFC Server Parameter
     Application Server (Gateway):           ZULIA
     Application Server Service (Gateway):      sapgw00
     Program ID:                     DEV210
     SNC:                          NOT CHECKED
     UNICODE:                     NOT CHECKED
     Inital Connections:               10
     Maximum Connections:               10
     Advanced Mode:                    NOT CHECKED
     RFC Metada Repository Parameter
     Load Balancing:                NOT CHECKED
     Application Server:               ZULIA
     System Number:                    00
     Authentication Mode:               Use Logon Data for SAP System
     Logon User:                    ldiego
     Logon Password:                    **********
     Logon Language:                    ES
     Logon Client:                    210
     Adapter-Specific Message Attributes
     Set Adapter-Specific Message Attributes: NOT CHECKED
This are the configuration of RFC Destination on ZULIA:
     RFC Destination Name:                XI_RFC
     Connection Type:               T
     ID Program:                    DEV210
     Host Gateway:                    ZULIA
     TCP Service                    sapgw00
Must I create the RFC Destination on the JCo RFC Provider in Visual Administrator?

<i>Is the RFC destination created in the R/3 is pointing correctly to the XI system and vice -versa. Test the connection.</i>
I tested my RFC Destination from R/3 system and the response was successful. What do you mean about vice-versa? How do I test it in the other way?.
I recreate my Sender Agreement. And my Business System is correct.
This are the parameters of my Sender Agreement:
Service:     DES210_DEV
Interface:     Z_DATOS_SAP
Namespace:     urn:sap-com:document:sap:rfc:functions
Sender Communnication Channel: cc_s_rfc_dataCom
When I execute the FM in R/3 the dump now is:
Wrong Sender Agreement:The Sender agreement does not have channel

Error: Sender agreement not found, lookup of binding via CPA-CACHE failed.

Hi,
I am doing an RFC to File Scenario in which RFC has to be triggered from CRM system. The TCP/IP connection and communication Channel are working fine. But when i trigger my RFC using the RFC destination following errors occur:
1. The SYSTEM_FALIURE exception comes on CRM side.
2. In adapter monitoring the following error comes on XI side:
Error: Sender agreement not found, lookup of binding via CPA-CACHE failed for Adapter type RFC.
I have also tried the scenario with RFC request as source message and also after J2EE cache refresh but the problem still persists. And one more thing my file adapter (In receiver communication channel) is not working means it is not started. And no message is coming in SXMB_MONI.
Could anyone please help me to resolve this issue.
Regards,
Vinay Yadav

Hi Aaron,
I had the same error and your feedback solved my problem!
Thank you sooo much!!!!
Luciana

RFC Sender error - lookup of alternativeServiceIdentifier

Hi,
I am trying to configure an R/3-XI-Java proxy scenario using the RFC adapter as sender. When I execute the RFC on the R/3 system using the RFC destination, I get the exception SYSTEM_FAILURE. In the RFC adapter monitor, the error message is "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel". I have verified the settings mentioned in SAP note 730870 (Q. 15), but am still getting the same error. Please let me know how to resolve this error.
Thanks,
Sumanth.

Hi Sumanth,
Check the <i>Adapter Specific Identifiers</i> in the Business sytem which contians RFC adapter.
Make sure that R/3 System ID is equal to the one specified in the SLD.
You can also "compare" the same with that in the SLD.
You should concider clearing the SLD data cache before comparison
Cheers,
Rashmi

CPA Cache Connectivity test fails

Hi All,
We are facing the following issues that have to do with the Adapter Engine:
1) In RWB, the Adapter Engine is in error/red status with the following details: Adapter Engine, message: fatal DeleteJob (Default Delete Job) failed.
2) In RWB, the Cache Connectivity Test fails with the following error: Communication with JMS server failed.
3) The CPA Cache refresh gives erros.
Any ideas? There are no Service users locked, SLDCHECK works fine etc.

Hi,
It seems to like problem with your JMS Connector.
For this, login into Visual admin -->cluster >services>JMS connector-->runtime (tab)->check the factories / destinations. Please contact with your basis team, they will might be helpful to you. After that restart your server, it will solve your issue.
Regards,
P.Rajesh
Edited by: Rajesh_1113 on Jun 5, 2011 9:01 AM

Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

Hi all,
When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
Environment:
The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
Version: 3.4.1".
i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
The Jars i added in the classpath:
adobe-forms-client.jar
adobe-livecycle-client.jar
adobe-usermanager-client.jar
adobe-utilities.jar
ejb.jar
j2ee.jar
ecutlis.jar
com.ibm.ws.admin.client_6.1.0.jar
com.ibm.ws.webservices.thinclient_6.1.0.jar
server.jar
utlis.jar
wsexception.jar
My code is :
Properties ConnectionProps = new Properties();
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
//Create a ServiceClientFactory object
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
//Create a FormsServiceClient object
FormsServiceClient formsClient = new FormsServiceClient(myFactory);
//Get Form data to pass to the processFormSubmission method
Document formData = new Document(req.getInputStream());
//Set run-time options
RenderOptionsSpec processSpec = new RenderOptionsSpec();
processSpec.setLocale("en_US");
//Invoke the processFormSubmission method
FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
List fileAttachments = formOut.getAttachments();
Iterator iter = fileAttachments.iterator();
int i = 0 ;
while (iter.hasNext()) {
Document file = (Document)iter.next();
file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
short processState = formOut.getAction();
...... (To the end of the sample)
My Error was:
com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
at HandleData.doPost(HandleData.java:62)
at HandleData.doGet(HandleData.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
a

I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
Do the following test:
- Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
- Ping machine1 from machine1 and note the ip address.
The two pings should match.
- Ping machine2 from machine1 and note the ip address.
- Ping machine2 from machine2 and note the ip address.
The two pings should match.
Usually this kind of error would happen if your servers have internal and external ip addresses.

Dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.b

from journalctl -b, I get some warning messages like this.
Oct 26 12:52:48 myhost dbus-daemon[359]: dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 26 12:52:48 myhost dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 26 12:52:48 myhost dbus-daemon[359]: dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.
Oct 26 12:52:48 myhost dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service fail
Oct 26 12:52:48 myhost pulseaudio[1234]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.Lo
Oct 26 12:52:49 myhost rtkit-daemon[1235]: Successfully made thread 1260 of process 1260 (/usr/bin/pulseaudio) owned by '1000' high priority
Oct 26 12:52:49 myhost rtkit-daemon[1235]: Supervising 2 threads of 2 processes of 1 users.
Oct 26 12:52:49 myhost pulseaudio[1260]: [pulseaudio] pid.c: Daemon already running.
I want to disalbe bluez.service,but failed,
#systemctl disable dbus-org.bluez.service
Failed to issue method call: No such file or directory
I have no bluetooth device in my laptop, how to resolve this porblem?
Thanks in advance.
Last edited by eastpeace (2012-10-26 06:12:53)

AND additional information
# systemctl status dbus-org.bluez.service
dbus-org.bluez.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

Authorizations for CPA Cache

Hello Experts,
I am not able to do full CPA Cache and Partial Cache Refresh.
What are the authorization needed for it...it is giving authorization not there
Thanks,
Vishal

Hi,
If someone has the same problem and come to this topic, the necessary role to execute a CPACache Full Refresh and to avoid the error: "403 Forbidden: You are not authorized to view the requested resource" is: SAP_XI_ID_SERV_USER.
Regards.
Rodrigo.

Lookup failed for UserLoginControl

Hi, I am having trouble logging in to my deployed application. In my development
env everything is working fine but in my deployed app I get the following error
when I try to log in:
Context failure: onAcquire[Lookup failed for name:java:comp/env/bfawiWebApp.com.bea.p13n.controls.login.UserLoginControl.jcx.userManager]
I believe the error is occuring when I call the following bit of code:
com.bea.p13n.usermgmt.profile.ProfileWrapper var = myControl.login( aForm.username,
aForm.password, super.getRequest() );
I know I am probably missing something in the configuration of the server I am
deploying to but I am not sure what it might be. Does anyone know what the problem
might be? Thanks, John

Maybe this resoruce will be helpful.

CPA Cache and J2EE server issues

Hi Experts,
I am having a File to File scenario where the sender channel picks up csv files ( around 3MB each). Once I finished the configuration of the scenario, the J2EE server started to restart continuously five times and stops with a out of memory error.
After going through the defaultTrace.trc file in logviewer, this is the first error that I could see after starting the J2EE server.
CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://pi-dev:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pid.pi-dev), due to: HTTP 503: Not Ready
Source Name: com.sap.aii.service.cpa.impl.cache.CacheManager.I checked the RFC destination of INTEGRATION_DIRECTORY_HMI and also checked if PIDIRUSER and PIAFUSER are locked or not. But they are not locked.
After the above error, the errors just build up probably because of the adapter framework not firing up. One of the error is:
Failed to lookup object from JNDI for name localejbs/AFWListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at localejbs, the whole lookup name is localejbs/AFWListener.
Source: com.sap.aii.af.ra.ms.runtime.Resources
I also increased the max thread count in the Application Thread Manager to 250 in the Config tool. I kept the heap sizes as posted above.
Any help will be greatly appreciated.
Regards

Hey,
>the J2EE server started to restart continuously five times and stops with a out of memory error.
Strange, Can you test with less than 1 MB file and let us know the status, Is SAP PI & ECC are installed in the same Server.
Cheers
Agasthuri

Is CPA Cache refresh linked with ftp or file pooling process in XI?

Hi,
I have a file to file scenario using Transport protocol as FTP in XI 3.0 SP 15.
When we try to sends some file using ftp protocol where we are using
FTP connection parameters
Server                          = <CORRECT IP>,
Port                               = 21 ,
User name                <CORRECT NAME>,
Password                  <PASSWORD> ,
Data Connection           = Active
Connection Seq         = None
Connection Mode         = Permanently
Transfer Mode            =   Text
Processing Parameters
Quality of Service    = Exactly Once
Pooling Interval        = 1 sec
Processing Mode    = delete
File Type                   = Text
File encoding           = utf-8
The problem we are facing like some time the ftp is not working even the file is present in the location for pick up. If few files are stacked up to be collected then when we are using CPA Cache refresh in Full mode manually then it fetches all the files from the location but the problem is that ,we have a time constraint for this process to be completed in just 60 seconds if we are not able to pick up a file in 60 Secs then the file will be treated as invalid.
So I just want to know how Manual CPA CACHE refresh in full mode generally solve the problem.
Next if more files will be stacked up then cache refresh also failed to solve the problem and more cache refresh result in NOT pooling any other files in XI including the above discussed flow.
So,in anyway Cache refresh linked with ftp or file pooling process in XI?
Please assist me in correctly understating the whole problem and what solution could be put to solve this.
Thanks,
Satya
Edited by: Satya Jethy on Mar 14, 2008 12:28 PM

Hi Suraj,
If you see my query i have mentioned that the pooling interval is 1 Second.
If we are not able to pick the file with in 60 Secs as this is a real time scenario so the file will be treated as a invalid file.
Moreover this problem is happening some time.
I have also checked the component monitoring it is saying everything is ok as because we are receiving the file with out any error and the file transfer is also success.The only problem is that it is not collecting the files from the given location.
Hope i make you understnad the problem .If not please revert back i will try to explain once again.
Thanks,
Satya

PI 7.1 - CPA Cache not updated with directory data.

Hi Gurus,
I have installed PI 7.1 and recently I refreshed my cache in partial and full mode. when I go to RWB->Cache monitoring -> Show Cache Status Table, I see following error for Central Adaptor engine.
<?xml version="1.0" encoding="ISO-8859-1"?>
<ConfirmationXML>
   <CacheRefreshError>
      <EngineType>
      AE
      </EngineType>
      <EngineName>
      af.sxd.mchir134
      </EngineName>
      <RefreshMode>
      C
      </RefreshMode>
      <GlobalError>
         <Message>
         CPA Cache not updated with directory data.
         </Message>
         <Trace>
         com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Failed to check secure connection configuration. Reason: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:134)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaRefreshURL(DirectoryAccess.java:191)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaCacheUpdateXML(DirectoryAccess.java:440)
     at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:491)
     at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:322)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:471)
     at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getSLDInstanceName(SLDAccessImpl.java:96)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:119)
     ... 7 more
Caused by: com.sap.aii.utilxi.sld.SldReadFailedException: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:126)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:142)
     at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:458)
     ... 9 more
Caused by: com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.utilxi.sld.SldProxy.getXISubSystem(SldProxy.java:526)
     at com.sap.aii.utilxi.sld.XIEntityInSld.getInstFromSld(XIEntityInSld.java:494)
     at com.sap.aii.utilxi.sld.XIEntityInSld.readFromSld(XIEntityInSld.java:156)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:120)
     ... 11 more
         </Trace>
      </GlobalError>
      <GlobalError>
         <Message>
         Confirmation handling failed.
         </Message>
         <Trace>
         com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Failed to check secure connection configuration. Reason: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:134)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getConfirmationURL(DirectoryAccess.java:162)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.invokeConfirmationURL(DirectoryAccess.java:462)
     at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:603)
     at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:322)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)
Caused by: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:471)
     at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getSLDInstanceName(SLDAccessImpl.java:96)
     at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:119)
     ... 7 more
Caused by: com.sap.aii.utilxi.sld.SldReadFailedException: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:126)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:142)
     at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:458)
     ... 9 more
Caused by: com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable)
     at com.sap.aii.utilxi.sld.SldProxy.getXISubSystem(SldProxy.java:526)
     at com.sap.aii.utilxi.sld.XIEntityInSld.getInstFromSld(XIEntityInSld.java:494)
     at com.sap.aii.utilxi.sld.XIEntityInSld.readFromSld(XIEntityInSld.java:156)
     at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:120)
     ... 11 more
         </Trace>
      </GlobalError>
   </CacheRefreshError>
</ConfirmationXML>
Please suggest the solution.
Thanks,
Surendra

Guys,
I have the same issue. Any help on this is appreciated!
Issue log from CPA cache refresh
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.sxd.pl1vw158</EngineName>
<RefreshMode>C</RefreshMode>
- <GlobalError>
<Message>CPA Cache not updated with directory data.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Failed to check secure connection configuration. Reason: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:134) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaRefreshURL(DirectoryAccess.java:195) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaCacheUpdateXML(DirectoryAccess.java:448) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:457) at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:291) 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: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable) at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:505) at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getSLDInstanceName(SLDAccessImpl.java:96) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:119) ... 7 more Caused by: com.sap.aii.utilxi.sld.SldReadFailedException: HTTP response code: 503 (Service Unavailable) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:133) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:150) at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:492) ... 9 more Caused by: com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable) at com.sap.aii.utilxi.sld.SldProxy.getXISubSystem(SldProxy.java:527) at com.sap.aii.utilxi.sld.XIEntityInSld.getInstFromSld(XIEntityInSld.java:553) at com.sap.aii.utilxi.sld.XIEntityInSld.readFromSld(XIEntityInSld.java:165) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:127) ... 11 more</Trace>
</GlobalError>
- <GlobalError>
<Message>Confirmation handling failed.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Failed to check secure connection configuration. Reason: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:134) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getConfirmationURL(DirectoryAccess.java:166) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.invokeConfirmationURL(DirectoryAccess.java:470) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:576) at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:291) 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: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable) at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:505) at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getSLDInstanceName(SLDAccessImpl.java:96) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:119) ... 7 more Caused by: com.sap.aii.utilxi.sld.SldReadFailedException: HTTP response code: 503 (Service Unavailable) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:133) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:150) at com.sap.aii.af.lib.sld.impl.SLDAccessor.getSLDInstanceName(SLDAccessor.java:492) ... 9 more Caused by: com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable) at com.sap.aii.utilxi.sld.SldProxy.getXISubSystem(SldProxy.java:527) at com.sap.aii.utilxi.sld.XIEntityInSld.getInstFromSld(XIEntityInSld.java:553) at com.sap.aii.utilxi.sld.XIEntityInSld.readFromSld(XIEntityInSld.java:165) at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:127) ... 11 more</Trace>
</GlobalError>
</CacheRefreshError>
Regards

SecureAMF channel failed for first time initialization

Hi all,
I have a Flex application to authenticate with server via RemoteObject.
It is working normally with http (i.e. amf channel)
However when I try to login via https, the first access time, Flex application always return Fault error. Subsequent login is OK.
From server side, I see user has been logged in successfully at first time.
Is it because the certificate is not trusted? Any idea?
Thank you,
Anh
This is the log that I have from client side:
LoginCommand Fault: (mx.rpc.events::FaultEvent)#0
bubbles = false
cancelable = true
currentTarget = (null)
eventPhase = 2
fault = (mx.rpc::Fault)#1
    content = (Object)#2
    errorID = 0
    faultCode = "Client.Error.MessageSend"
    faultDetail = "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure'"
    faultString = "Send failed"
    message = "faultCode:Client.Error.MessageSend faultString:'Send failed' faultDetail:'Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure''"
    name = "Error"
    rootCause = (mx.messaging.events::ChannelFaultEvent)#3
      bubbles = false
      cancelable = false
      channel = (mx.messaging.channels::SecureAMFChannel)#4
        authenticated = false
        channelSets = (Array)#5
        connected = false
        connectTimeout = -1
        enableSmallMessages = true
        endpoint = "https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure"
        failoverURIs = (Array)#6
        id = (null)
        mpiEnabled = false
        netConnection = (flash.net::NetConnection)#7
          client = (mx.messaging.channels::SecureAMFChannel)#4
          connected = false
          objectEncoding = 3
          proxyType = "none"
          uri = "https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure"
        piggybackingEnabled = false
        polling = false
        pollingEnabled = true
        pollingInterval = 3000
        protocol = "https"
        reconnecting = false
        recordMessageSizes = false
        recordMessageTimes = false
        requestTimeout = -1
        uri = "https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure"
        url = "https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure"
        useSmallMessages = false
      channelId = (null)
      connected = false
      currentTarget = (mx.messaging.channels::SecureAMFChannel)#4
      eventPhase = 2
      faultCode = "Channel.Connect.Failed"
      faultDetail = "NetConnection.Call.Failed: HTTP: Failed: url: 'https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure'"
      faultString = "error"
      reconnecting = false
      rejected = false
      rootCause = (Object)#8
        code = "NetConnection.Call.Failed"
        description = "HTTP: Failed"
        details = "https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure"
        level = "error"
      target = (mx.messaging.channels::SecureAMFChannel)#4
      type = "channelFault"
headers = (null)
message = (mx.messaging.messages::ErrorMessage)#9
    body = (Object)#2
    clientId = (null)
    correlationId = "F4E42A7F-5E56-B704-CDB6-87826108D443"
    destination = ""
    extendedData = (null)
    faultCode = "Client.Error.MessageSend"
    faultDetail = "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'https://172.52.22.218:9443/MyApplication/messagebroker/amfsecure'"
    faultString = "Send failed"
    headers = (Object)#10
    messageId = "B549C02F-9EDF-7C6E-C89F-878261572A73"
    rootCause = (mx.messaging.events::ChannelFaultEvent)#3
    timestamp = 0
    timeToLive = 0
messageId = "B549C02F-9EDF-7C6E-C89F-878261572A73"
statusCode = 0
target = (null)
token = (mx.rpc::AsyncToken)#11
    message = (mx.messaging.messages::RemotingMessage)#12
      body = (Array)#13
        [0] (com.mydomain.model.dto::LoginDTO)#14
          statuscode = "0"
          userName = "myusername"
      clientId = (null)
      destination = ""
      headers = (Object)#15
      messageId = "F4E42A7F-5E56-B704-CDB6-87826108D443"
      operation = "authenticate"
      source = (null)
      timestamp = 0
      timeToLive = 0
    responders = (Array)#16
      [0] (com.mydomain.controller::LoginCommand)#17
    result = (null)
type = "fault"

Hi Alex,
Thank you for your reply. It is true that I failed in IE 6, 7, 8 with amf-secure channel. Firefox and Google Chrome is working.
I have checked the services-config.xml (should be the default) and see the <add-no-cache-headers>false</add-no-cache-headers> in channel definition my-secure-amf:

        <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel">
            <endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
            <properties>
                
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
        </channel-definition>
For my-amf, it is set to true

        <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
            <properties>
                <polling-enabled>false</polling-enabled>
                <add-no-cache-headers>true</add-no-cache-headers>
                <invalidate-session-on-disconnect>true</invalidate-session-on-disconnect>
            </properties>
        </channel-definition>
Is there any other place I need to add the add-no-cache-headers?
I'm using Websphere application, do I need to set any properties in Websphere?
Thank you and look forward to your reply,
Anh

Database cache failed during installation !!!!

Hello Guys,
Database cache has failed during my installation !!!
I have re-started it using wtacca -create -custom, but after 23% it gives
a error
connecting to the cache failed
reason ORA -01034: ORACLE NOT AVAILABLE
ORA -27101 - SHARED REALM DOES NOT EXISTS
SVR 4 ERROR 2: NO SUCH FILE OR DIRECTORY
My client is behind me for this issue, if anybody has come across
this problem let me know, I did'nt do any changes to tnsnames.ora or listener.ora
in 9IAS machine !!
In one machine 8.1.7 is running and 9ias is running on another machine and this
on Sun Solaris 7 environment !!!
Any suggestions are greatly appreciated !!!
A.Kishore
null

Hi Oliver,
normally the listener is installed by SAPINST during installation of the database instance. On which stage of the installation are you ? What is already installed ? What is your installation order of central instance, database instance, system central service instance(s) ?
Additionally you can try to start the listener via command line with user <sid>adm "lsnrctl start" (if the listener name is "LISTENER". At least on UX this works, hopefully on Windows as well ;-).
Regards,
Juergen

Lookup of alternativeServiceIdentifier via CPA-cache failed for channel

Similar Messages

Maybe you are looking for