Adapter Engine af.SID.HOST ERROR

Hi ALL
Facing problem with ADAPTER Engine.....we are using PI 7.0..
here is the desciption of the error:
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.03.server3, string], target element type: SAP_BusinessSystem)
We found some SAP Note 764176 related to this issue...IN second step , as per note we have to delete all the Technical system of type EXCHANGE INFRASTRUCTURE, If we delete that..there is no option for creating Technical sytem os Type EXCHANGE INFRASTRUCTURE...
we have done Template based configuration for Configuring PI Server...
Now when we run this template for second time ,it will struck at 72% ..
Ur suggestion & guidance is necessary to fix this error ASAP
Regds,
vasanth.

Hi Vasanth,
I don't know what to do with the template, but I can tell you how to fix that error you were getting. You need to do the following:
Step 1. Log on to the SLD. Goto Administration->Content Maintenance
Step 2. From the drop boxes, select the following:
Subset: Associations
Class: XI Contained Integration Server
Step 3. You will get a list of the XI servers listed in the SLD. Select your particular server. The next screen will show you details. There will be a link near the top of the box saying something like '1 Associated Instance'. This should actually be '3 Associated Instances'. Click on this link.
If there are less than 3 associated instances, you will need to add associations. I will list all three here, please create the ones that are missing.
Association 1. XI Contained Integration Server
Add XI Domain: Domain <domainname>
Association 2. XI Integration Server Logical Identity
Add Business System: <Business System for the Integration Server>
Association 3. XI Sub-System viewed Application System
Add BC System: <SID> on <Hostname>
(There will be a huge list to select from, make sure that you select from the subgroup 'BC System').
Save this and exit the SLD. This should solve your problem.
If you need, give me your email address and I can send you a screen-shot of what it should look like with the associations properly created.
Do let me know if this helps.
Cheers
Manish

Similar Messages

Adapter Engine XML Schema Validation Error Surpression

We recently developed a number of web services that are called by 3rd parties outside our network. The web service request once made is picked up by a Web Dispatcher which then forwards the request to the de-central adapter. Both of these components reside within within a DMZ.
We have, as an additional security measure made use of the new Adapter Engine XML Schema validation available with PI 7.1, to ensure that the payload of incomming messages is checked to ensure that it is a known structure.
Now here is my problem, we recently had these services penetration tested by a 3rd party to ensure that they were secure and whilst the report was very good showing no major weaknesses they did pickup on a couple of items including that the fact that if the XSD to be used during payload message validation cannot be found an 'ADAPTER.JAVA_EXCEPTION' is returned to the web service consumer that highlights the path details of where the XSD should be (but could not be found).
This was viewed as useful to an attacker for a number of reasons:
1. Feedback in SQL injection attempts via verbatim DB error messages greatly improves attacker efficiency
2. Path information is useful to the attacker for OS fingerprinting, directory traversal attempts
3. Other miscellaneous stack trace information is useful to an attacker to understand how the application works
Is there anyway this can be surpressed so that the adapter does not show this information in the returned error message - see example message below ?
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema MaintenanceOrderByIDQuery_sync.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiSAPGlobal20~Global\MaintenanceOrderByIDQuery_sync.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor497.invoke(Unknown Source)
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiEA-APPLSEGlobal\Schema1.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)

Hi,
We are having the same problem, so you are not alone.
I had an extensive call with Azure premium support and we where able to determine that:
- Nothing is missing or in the wrong place in my exported .xml file.
- Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
- You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's.
I am currently waiting for an solution, i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
he should speak with the previous person helping me. I have not heard from Azure support since.
SR Number:115021812414226
Open on:02/18/2015 09:28
> There are networks with and without gateways created and the issue is happening on all the networks.
> We are unable to add or remove the DNS servers. (by web gui)
> Also not able to add or remove any subnets. (by web gui)
> Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
> Created CRI- 3405931, but they said it will need WATS team.
> Confirmed with WATS engineer as well and moving case to WATS.
> Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
> But they still want to get this resolved soon.
> Agreed and dropped off, reducing severity to B 24/7.
I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
Should anyone have more information on this, please share it here.

Moving the database of SAP J2EE Adapter Engine on another host

Hello all,
I'd like to ask SAP/Oracle experts if there is any obstacle, why would not be able to move Oracle database of SAP J2EE Adapter Engine on other/different host after the installation.
As I describe int he thread [Installation of J2EE Adapter Engine with DB on different host|Installation of J2EE Adapter Engine with DB on different host;, the SAPINST program doesn't offer the possibility to install J2EE Adapter Engine with DB on other host than the central instance.
Only thing I'm not sure about is if this is done by any purpose for some database requirement, or it's simply not there.
SAP J2EE AE is normal JAVA AS with some more functionalities and is also installed within SAP PI/XI installation, which can run in "distributed model" system.
What do you think ?
Thank you for your opinion in advance.
Regards
Tomas

No opinion anyone ?
Tom

Unable to determine the adapter engine or sld connection error

1. Check wether the SLD is up or not
2. Note 764176 - Error in XI due to inconsistent SLD contents --> Follow this note.

Aswin..
Is that a question or answer or information to others?
VJ

J2SE Adapter Engine Error

Hi everyone,
I am facing couple of issues with J2SE adapter engine.
1. First Issue
Config in SLDaccessor -
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
SLD.host=<HOST>
SLD.port=50xxx
SLD.user=user
SLD.password=pass
SLD.adapterEngineName=AdapterEngine
Config in Sender File Channel
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
XI.SLDConfiguration=SLDaccessor
#XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
XI.TargetURL=<fromSLD>
XI.QualityOfService=EO
XI.Client=001
<Other parameters like InterfaceName / FCC>
If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
If I ignore the SLDaccessor, the message is processed successfully.
Am I missing anything in the above configuration?
The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
2. Second Issue
In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
The port is wrong ... it should be 8200. My question is, from where to fix this?
Any help will be highly appreciated.
Thanks,
Neetesh

Hi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh

Error : Unable to find URL for Adapter Engine

Hi Experts,
I have searched several forums , but i am not clear on how to resolve this error.
I am using XI 3.0, my scenario is File->XI->File
I am getting this error in SXMB_MONI.
*Can any body suggest me a clear step-by-step procedure to solve it.*
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.xd2.host-dev</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.xd2.host-dev</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.xd2.hydrus-dev</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
sai

Hi Debashish,
Thanks for ur reply,
I have executed
--->Execute SAI_AE_DETAILS_GET from se37
>Enter AE name:<host>.<systemid>
After executing, i got these param
Exception NO_ADAPTER_ENGINE_FOUND
Message ID: SAI_GLOBAL Message number: 016
Message:
no_adapter_engine_found: Unable to find Adapter Engine host-DEV.XD2
Exchange profile parameters are like this
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call terminated sucessfully
Retrieved value of
section = Connections
parameter = com.sap.aii.ib.server.connect.webas.r3.ashost
-> value =
and i dont have authorizations for SU01 fro lock/unlock.
Any suggestions how to proceed.
Thanks
Sai

Reg Unable to find URL for Adapter Engine Error

Hello,
During execution of a scenario, i am getting these errors in sxmb_moni:
AE_DETAILS_GET_ERROR
3: Unable to find URL for Adapter Engine af.xip.poecspxioo4
Error when reading the access data (URL, user, password) for the Adapter Engine.
Seems like it is a problem of XI Server unable to locate the Central adapter engine due to some parameter not set properly.
So, what are the points we can check while installation of XI so as to rectify this problem.

Hi all,
I got the similar error in my scenario and i solved the same.Actually i ma not pretty surte this will solve your problem.
In my case proxy generation settings was mis configured in the sender system. so its caused the reason.
I made an entry in the SPROXSET table and i did other activities like RFC and application system also.
Then its worked for me. Its not matching with your case please do ignore this one
Regards
Vijay

Schema Validation using Adapter Engine : Error

Hello Guys,
For SOAP message coming into PI, I am doing schema validation by adapter engine but getting below error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in /usr/sap/PID/<Server>/j2ee/cluster/server1/validation/schema/af7c332075ce11e08e23ddce0a512253/urncompany.comcrmexternald2c/ServiceRequest_Out/urncompany.comcrm~enhancements/Schema1.xsd (validation/schema)
* at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)*
* at sun.reflect.GeneratedMethodAccessor336.invoke(Unknown Source)*
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)*
* at java.lang.reflect.Method.invoke(Method.java:585).........................*
Here are some details
- Using standard SAP Message Type
- Enhance data type
- while exporting schema, there are 3 files in zip file
1) mainschema (renamed it to MessageType name)
2) Schema1.xsd
3) Schema2.xsd
I have followed the step according to below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?QuickLink=index&overridelayout=true
I have also checked schema1.xsd on PI server and File is there but still getting error.
Any suggestions ?
Thanks
Edited by: chetan patel on Jan 31, 2012 10:50 PM

Please make sure that main xsd uses import or include tag to reference both schema1.xsd and schema2.xsd. If the main xsd does not do it, Pi cannot verify it. Since you package all the files as zip file, also make sure the path for the secondary files are in proper location.
In short, the import element allows you to use schema components from any schema; the include element allows you to add all the components of an included schema to the containing schema. If the target namespace is same for both then include tag should be good enough. If you don't find one, you might have to use include tag element in the main or parent xsd file.
Edited by: Baskar Gopal on Jan 31, 2012 5:18 PM

Abap tables for adapter engine errors

Hello,
Which ABAP tables in PI will have the data relating to adapter engine errors (like the communication channel errors). Is there any way I can get the adapter engine errors from abap tables?
Any help is very much appreciated.
Thanks
MLS

Hello,
What I am trying to do is write a report in ABAP, which will read the table for errors (for messages which are not processed successfully in Integration engine or adapter engine) and email those errors to users. If there is communication channel error in RWB, the message in sxmb_moni is still shown as success and is not being updated in table SXMSPERROR.
We cannot use PI Alerts here since the email list is dynamic for the same PI interface.
Any ideas on how to accomplish this?
Thanks
MLS

Resend Message that fails in adapter engine but shows success in sxmb_moni

Hello SDN!!
We are testing sending soap requests out via SSL. We are using a BEA as a pass through server for SSL encryption only.
The scenerio is to send a message from SAP to PI 7.1 to BEA (SSL enc) to Receiving System. We successfully connect to BEA (only used as a pass-through) but the connection to Receiving System does not work. This returns an error to our adapter engine.
My question is this, Since SXMB_MONI shows the message as successful, but the adapter engine is showing an error. What is the best way for
1. Monitor the errors, (I only see where you can monitor the type of adapter only)
2. Resend the message, since it shows valid in SXMB_MONI, it won't let me resend.
Any help will be greatly appreciated and awarded
Cheers
Devlin

1. Once the message is in successful status in moni, the best way to monitor becomes RWB -> Message Monitoring.
2. For adapter engine related errors, you may resend the data manually using the resend option in the Message Monitoring. Otherwise, for automatic retry of messages, you may change the default settings.
Regards,
Prateek

Local Adapter Engine

Hi All,
Here we installed Local AE on both Sender and Receiver Systems but stuckup with configuring these Adapters.
Step1:How to configure the SLD part if am working with Local AE's?
Step2:How can XI recognize these Local AE's?
Step3:In the Communication channels while defining the File Adapters,At the Adapter Engines option i have to choose Local AE instead of Integration Server.To get(display) this option (Local adapters) what all the connections are configurations need to be done at XI and Sender/Receiver?
Any suggestions??
Thanks,
Kalyan.

HI Kalyan,
The Plain J2SE Adapter Engine is one of the PI messaging components responsible for message processing and protocol handling. This type of adapter engine was already available with XI 2.0 and merely requires a Java Virtual Machine to run. It can be used as a non-central adapter engine, but it hosts only a subset of the adapter functions and does not support standard security features such as security logs or integrated user management
The Plain J2SE Adapter Engine does not access the exchange profile, because the connection data is kept locally. It does, however, register itself in the System Landscape Directory (SLD).
for
Technical Communication
http://help.sap.com/saphelp_nw04s/helpdata/en/5e/f85141196ff423e10000000a155106/frameset.htm
Adapters Running in the Plain J2SE Adapter Engine
http://help.sap.com/saphelp_nw04s/helpdata/en/43/a745d8823017b5e10000000a1553f6/frameset.htm
<removed by moderator>
regards
kummari
Edited by: Mike Pokraka on Jul 24, 2008 1:00 PM

Where to set up connection to Adapter Engine (central)?

Hi guys!
I need to change connection (server:port) settings to central adapter engine, because I get error (in RWB->Component monitoring->AdapterEngine):
Unable to establish connection to "http://<servername>:<port>/AdapterFramework/rtc"
Thank you!
Olian

> Hi Barry,
>
> I checked it - I didn't find anything...
>
> Olian
Define - "didn't find anything?"
There were no associations for the XI Adapter Framework?

Multiple Adapter engines

Can anyone confirm if XI 2.0 supports multiple Adapter Engines on different hosts?
Thanks

Yes, the XI 2.0 supports multiple adapter engines.
Only the RFCAdapter should be installed on the XI 2.0 Integration Server engine, but all other adapters can run locally on the business systems for example.
Best regards, Silvia

Non Central adapter engine error

Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani

Error in RWB - Component Monitoring - Adapter Engine

Hi,
After we install an Additional Application Server Instance, we are facing an issue with the Runtime Workbench, specifically with the Adapter Engine status.
On the RWB we're have this error:
Ping Status: Unable to establish connection to
"http://<Additional AS Host>:<Central Instance JAVA Port>/AdapterFramework/rtc"
All the time it's pointing to the Additional AS with the Primary AS Java Port.
We are using a central SLD in PIP system.
We already reviewed, the point 8.12 of the "SAP NetWeaver PI 7.1 Including SAP EHP 1 - Troubleshooting Guide"
Any idea to solve this?
Regards,
GCC PI

Hi GCC,
Please change in the http://<host>:<j2ee_port>/exchangeProfile this settings:
Exchange Profile
Connections:
- com.sap.aii.connect.directory.name
- com.sap.aii.connect.landscape.name
- com.sap.aii.connect.repository.name
RuntimeWorkbench:
- com.sap.aii.rwb.server.centralmonitoring.r3.ashost
Please change the value in the:
Config Tool -> cluster-data -> Global Server -> Configuration ->
Services -> com.sap.aii.af.cpa.svc ->
 SLD.selfregistration.hostName
 SLD.selfregistration.httpPort
 SLD.selfregistration.httspPort
Also see notes: #1113161 - Links in Component Monitoring not working
and #764176 - Error in XI due to inconsistent SLD contents
After that, please restart the j2ee engine.
Regards,
Luis Diego

Adapter Engine af.SID.HOST ERROR

Similar Messages

Maybe you are looking for