on 11-24-2010 5:31 AM
Good Morning All,
Recently we are done our XI server upgradation from windows to Linux server.
we have only one central SLD for all XI Dev,Qua and production.
We find some issues after upgradation in XI
*****************************************************
1) No message is processed to XI
2) In RWB,Adapter Engine shows under 'Non Central Adapter Engine'
3) cache connectivity shows error
Fetch Data]: com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: sap_businesssystem, [creationclassname, SAP_BusinessSystem, string, name, XD2, string], target element type: SAP_BCSystem)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:490)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: sap_businesssystem, [creationclassname, SAP_BusinessSystem, string, name, XD2, string], target element type: SAP_BCSystem)
at com.sap.aii.ib.server.sldquery.SLDQuery.dammiIlMioCentralAdapterFramework(SLDQuery.java:70)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:191)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
[Data Evaluation]:
Kindly suggest me how I can approach here.
Thank you
Sateesh
Hi Sateesh,
1. Do SLD check, using the transaction SLDCHECK.
2. Check whether Sdapter is registered properly.
3. Perform PI readiness check. Check the below link:
http://help.sap.com/saphelp_nw2004s/helpdata/en/a0/40084136b5f423e10000000a155106/content.htm
If you want to use a central SLD, see SAP Note 939592.
For a general readiness check, see SAP Note 817920.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sateesh,
This issue is generally resolved by applying note #764176.
Also would be good to apply the parameter of note #1278563.
Regards,
Caio Cagnani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1. Check for the Centerlise SLD is proper Connected or Not :- >
These are the following few notes for Centerlise SLD , Check whether each step is ok as suggested in documnet or not:-
These Documents are Used When Moving LOCAL SLD on centerlize SLD.
720717 - Reduce the number of System Landscape in SLD.
768148 - Using a separate SLD for XI.
939592 - PI Usage Configuration versus Central SLD.
764393 - Configuration of the SAP System Landscape Directory.
2. To Remove inconsistencies from RWB Component and SLD : ->
These are Documents Used for doing Changes in SLD When found Error on RWB.
764176 - Error in XI due to inconsistent SLD contents.
1031321 - Self-Registration of Adapter Engine and RWB fails.
I hope this will resolve your issue .
3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check tcode SLDCHECK and SLDAPICUST to check whether SLD is running successfully
--sandeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Looks like the components in SLD are inconsistent.
a. Make sure that the AE is completly registered as described in Note 1031321.
b. Ensure none of the PI Users is locked
c. Perform PI Readiness check, so that you can check whether all RFC Destinations like HMI_DIRECTORY ect and rest other things are fine.
Regards
Monika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.