ABAP Cache Refresh: PIAPPLUSER gets locked

Hi,
well we are a little desperate. Concerning ABAP-Cache resfresh we already read in forum and this guide on how to handle XI-Cache (https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290)
But the Cache don't get refreshed at all and the PIAPPLUSER gets locked even though we changed/overwrite all passwords on the needed places.
By the way: the SLDCHECK gives me no Business-Systems via LCR_LIST_BUSINESS_SYSTEMS even though there are some and also the technical and business system for Integration server is maintained correctly. When getting Http-Screen for SLD we get a login mask where i remember that this has not been the case before - right?!
Can somebody help. We have no clue what else to try!
br

Hi Rajeev,
well because we moved through the guide on how to manage caches on XI there were also SLDAPICUST mentioned. This is not the place the error occurs. Actually we still have no f***** clue where this happens.
Because this system is a fresh one we implemented one File2BAPI Scenario.
The File is read but when we want to check data in SXMB_MONI or Message-Monitor of RWB nothing shows up.
I guess this is also a problem concerning the PIAPPLUSER?
We can clearly confirm that no external system/service uses this User to connect but still after 2-3 minutes the user gets locked.
We have no clue what the problem might be...
Any suggestions?!
br

Similar Messages

PIAFUSER and PIAPPLUSER get locked all the time - where are they used?!

Hi guys,
well i am no basis guy but i have to do the following.
We want to use one SLD for PROD & DEV. We chose DEV SLD to be the one!
Therefore i followed Note 720717 in detailed way.
Because there is mentioned i have to change sth. in Service SLD Data Supplier i did so in PROD for giving the SLD-Adress of DEV. This was looking good, i changed, saved and restarted service.
But now the User PIAFUSER and PIAPPLUSER get locked all the time - even without trying to get SLD-Connection.
When i do SLDCHECK we also get error:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server.
Function call returned exception code ....4
=> Check whether the SLD is running!
..and it is running!
Could someone help?! We already read post and blogs the last 4 hours but nothing helped that far!
br
Edited by: Fritz Munster on Jul 21, 2008 4:32 PM
And we get some errors from CC also - e.g. when we want to get a file read:
com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.

Hi,
well i already re-checked all pwds again like given in Note 936093.
Everything runs fine that far but again, the PIAFUSER gets locked, PIAPPLUSER doesn't get locked anymore - finally.
The reason why i was coming to this error is because we need to use one SLD - i described already.
So now we wanted to check our PROD Scenarios, running a test with a FILE-CC and got following error in CC-Monitoring:
ERROR:com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
What could cause this error else than some stuff with pwds?!
Any ideas?! i work 10 hours on this crap now
br

Every time my PILDuser is getting locked

hi,
I have an error mesg when i execute the following command "http://microsoft:50000/exchangeProfile/index.html"
Name or password is incorrect (repeat logon)
Stack Trace class com.sap.rprof.dbprofiles.DBException:
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)
at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101)
at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1288)
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:195)
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:145)
at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:45)
at com.sap.rprof.remoteProfile.webui.ProfileWebTree.(ProfileWebTree.java:24)
at com.sap.rprof.remoteProfile.webui.Edit.getNewWebTree(Edit.java:327)
at com.sap.rprof.remoteProfile.webui.Edit.doGet(Edit.java:139)
at com.sap.rprof.remoteProfile.webui.Edit.doPost(Edit.java:236)
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:160)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
But when i again try with Unlock user from ABAP engine it is getting locked after i press refresh in the browser.And in the "connection tab" in the exchangeProfile page i have user as PILDuser, client 000 and passwd assigned here.

And after resetting the passwords i just moved little bit forward now i can see the following options on the screen
Screen of
Runtime Workbench       Help
Component Monitoring   | Message Monitoring   | End-to-End Monitoring   | Performance Monitoring   | Index Administration   | Configuration   | Alert Configuration   | Alert Inbox   | Cache Monitoring
Component Monitoring
Components with Status: AllRedRed & Yellow Display
But when i click Display on component monitoring and get the following error
"Following error occurred while executing the application:
Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden) "
Detailed Trace:
Stack trace for the above error message is:
com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)
     at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)
     at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)
     at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
     at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
     at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getXIDomain(SLDAgentObjectImpl0.java:375)
     at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
     at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
     at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:137)
     at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:100)
     at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:102)
     at jsp_component_monitoring1192662004031._jspService(jsp_component_monitoring1192662004031.java:209)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
     at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
     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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at jsp_FC_Secure1192662002718._jspService(jsp_FC_Secure1192662002718.java:24)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     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:160)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Error in INTEGRATION_DIRECTORY_HMI and CACHE REFRESH

Hi guys, well after checking the forum and several blogs i can't get rid of my problem!
I have a problem concerning INTEGRATION_DIRECTORY_HMI and CACHE REFRESH.
i wanted to get a file from a FTP-Server via CC and i got error:
<SAP:AdditionalText>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Because of this i tried to update my cache (SXI_CACHE). When i do a Delta Cache Refresh i get:
Prefix Number: entry missing for system SSID client 100.
When i do a complete Cache Refresh nothing happens at all. I also checked the cache notification in IB - Integration Directory where i fin dout that only the Integration Server (ABAP Cache) won't refresh. Well status is started but nothing else is happening.
Then i checked the RFC INTEGRATION_DIRECTORY_HMI, did a connection test where i get an Internal Server error.
Let me tell u that the systems runs very well in the last days but now i have no clue what might be wrong.
Can somebody please advice me? I already read all blogs concerning this and also did a complete system-restart....
br Jens

when you check INTEGRATION_DIRECTORY_HMI with SM59 it is normal to get
HTTP Response 500 - Internal Server Error. In this case it meens everything OK
see the rediness check, that is attached to SAP note 817920
when you start the complete cache refresh, you can see
the function module SAI_CACHE3_REFRESH_BACKGROUND in SM58. As long as you can see this entry, the cache
refresh is ongoing. If the refresh takes too long and runs on an error, try to specify another timeout in INTEGRATION_DIRECTORY_HMI or in the ICM
Best Regards
Alexander
Message was edited by:
 Alexander Wrobel
Message was edited by:
 Alexander Wrobel
Message was edited by:
 Alexander Wrobel

Cache refresh issue with PI Load Balanced HA setup.

Dear Experts,
Wei have installed a HA Load Balanced PI Production Server with the below specifications. Its a four node cluster. Two nodes for Application Cluster and another two nodes for Database Cluster.
Node1
Physical Hostname : axsappci
Virtual Hostname : axsapp00
Instances         : CI,SCS and ASCS.
Node2
Physical Hostname : axsappdi
Virtual Hostname   : axsapp00
Instances          : Dialog instance installed with physical hostname axsappdi
Node3
Physical Hostname : axsappd1
Virtual Hostname   : axsappdb
Instances : DB Instance.
Node4
Physical Hostname : axsappd2
Virtual Hostname   : axsappdb
Instances : Standby DB Instance (passive).
Web Dispatcher Hostname : h2h
Application Switchover : CI,SCS and ASCS to switchover to Node2 and dialog instance Node2 forcing to go down
Database Switchover : DB Instance switchover to Node2 if Node1 fails.
We have changed all the parameters according to note 951910 -> NW2004s High Availability Usage Type PI
I am facing an issue with the cache Notifications in the Integration Repository and Directory. The cache notifications are not happening properly particularly with the ABAP Cache.
I get the below error in my ID when i try to do the manual cache notification.
Unable to notify integration runtime (ABAP) of data changes
Unable to establish http connection "http://h2h:8002/sap/xi/cache?sap-
client=001"
Kindly assist.
Thanks and Regards
Raghu.

Hi Srikanth,
Thanks for the reply.
I have configured my web disptacher to use default HTTP and HTTPS ports i.e 80 and 443. According to note 951910 i have changed parameters in exchange profile to use these ports.
Regards
Raghu.

Delta and complete cache refresh.

HI,
Difference between Delta and complete cache refresh.
thanks
sunil

Hi,
There are several variants of the cache refresh mechanism depending on the scope of the cache refresh (delta only or entire cache refresh) and on the triggering component (tool or messaging component).
Delta Cache Refresh
Delta Cache Refresh involves the missing activated change lists to be included in the directory cache.
Complete Cache Refresh
To restructure the cache completely, in the menu bar choose XI Runtime Cache à Start Complete Cache Refresh.
Cache refreshing means getting the newly created component in the cache. Usually cache get refreshed automatically by SAP system and user do no thave to refresh it but in some cases the newly created component does not get dispalyed in cache. In that case this cache should be refreshed and it will pull out the new component in it.
Thanks
Swarup

PIAFUSER PIDIRUSER & PIISUSER are getting locked , when cache is refreshed

Hi XI Gurus,
My scenario goes like this.. Sonic MQ <- XI <- SAP CRM.The messages sent from CRM are reaching XI but not are not making to Sonic, and the error message in SXMB_MONI of XI is <SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
I know this problem deals with the aunthentication.The users PIAFUSER PIDIRUSER & PIISUSER are getting locked when ever Iam trying to refresh cache in ID.When I unlock them and again refresh the cache they are again getting locked.when I unlock the users and restart the message it gives me an error of cache probelm .The mesage is stuck at call adapter phase in SXMB_MONI.Iam really confused of what to do.. please help me..

And when the locks are gone it gives me the following error
I have checked my receiver side every thing is fine.
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=CRSCLNT100;TS=Sonic_BusService;AN=EMADispositionIN;ANS=urn:mentorg.com:ema:disposition;</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />

DELTA CACHE REFRESH getting the status red

Hi,
while doing the DELTA CACHE REFRESH getting the status red. There be a traffic light displaying RED on the right part of the screen.
regards,
bobby

I think you are talking about sxi_cache related refresh. If yes, then you may check the following:
1. Service user PIISUSER is not locked.
2. RFC Destination INTEGRATION_DIRECTORY_HMI is working properly.
Regards,
Prateek

ABAP HTTP cache refresh

Hi-
What role is required for an Integration Server (ABAP) HTTP cache refresh?
This is accessible if you go to XI Administration -> Cache Overview and click on Full Cache Refresh for INTEGRATIONSERVER_. It calls this URL.
http://hostname:8000/sap/xi/cache?sap-client=800&mode=F
XISUPER has all SAP_XI* roles. I get a "403 Forbidden" unless I include SAP_ALL.
Thanks,
J Wolff

Hi,
Check this document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
Also verify if the user has such roles:
SAP_XI_ID_SERV_USER
SAP_XI_IS_SERV_USER
SAP_XI_IR_SERV_USER
Regards,
Wojciech

Oracle PW getting Locked + ABAP Kernel Update through the JSPM

Hi Gurus,
#1
After resetting the PW ( ABAP + JAVA System ) at ABAP Side ( SU01 ) and at the Config Tool Secure Store Level + Restart the SDM Server THEN : first time
I am able to connect to DB for ConfigTool and I am also Able to Connect to JSPM, Change the PW and then for the Next Time( even though no changes made to SAPSR3DB ) the Oracle User SAPSR3DB Acc gets locked again - immediately and o repeated bases eventhough it is unlocked at the DB Level !!!
Being ABAP + JAVA Is there anything else I need to do while I reset the PW of J2EE Admin ?
I have referred the notes 701654, 669848 and as it is ABAP+JAVA I don'e need to go for SAP* Emergency User Activation.
#2
Can we update the ABAP Kernel ( CAR Files ) through the JSPM ?
Your inputs are very much appreciated.
Thanks,
Best Regards,
- Rupen

Hello,
I think JSPM can be used to update only the support packs and not SAP Kernel.
Also,
In the Oracle directory, there is a script which changes the database password.
Don't recollect the name though.
Regards,
Siddhesh

ABAP+JAVA System Copy -- Administrator account getting locked

Hi,
I am in the process of doing system copy of my portal to a new server. As per the SAP instructions, I had updated the JDK and SP levels of my EP to the latest supported ones.
Now when i am doing JAVA Add-in Export of my system, SAPinst is throwing error that --
"Error connecting to http://Entportal:50000/sap/monitoring/SystemInfoServlet. The provided user data might be incorrect or user might be locked.:
and when I check the "administrator" user account, it is getting locked. Even though I manually unlock it and update the password is secure storage, still when I run SAPinst, again it is getting locked. I have also chnged the path of my temporary directory to c:\temp which has no spacees in it, according to SAP instructions.
I have raised the issue through OSS, but still, in the mean time can sombody help me?
Regards,
Mandar

Hi Akshay,
I am not using any ID. SAPInst itself is trying to access systeminformationservlet using administrator account. at this stage it is failing to get the correct password and thats why my administrator account is getting locked.
Regards,
Mandar.

Not getting response in soap ui after cache refresh

Hi Experts,
 I have a scenario SOAP- PI-RFC Synchronous scenario. when we are trying to send message in SOAP UI nothing is coming to PI and its showing blank in soap UI . Before doing cache refresh all interfaces were working fine in QA but after that it s not working.
I have check login credentials and url are fine.
please help me on this?
Thanks,
suma

Hi,
I have created new project again
Some times response is coming as empty(missing raw data) and some times showing as
below
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
 td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
 A:link {color : #0059AA;}
 A:visited {color : #999999;}
 A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
 <tr bgcolor="#FFFFFF">
 <td align="left" colspan="2" height="48"> 401 Unauthorized</td>
 </tr>
 <tr bgcolor="#3F73A3">
 <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
 <td height="23"><img width=1 height=1 border=0 alt=""></td>
 <td align="right" height="23">SAP NetWeaver Application Server </td>
 </tr>
 <tr bgcolor="#9DCDFD">
 <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
 </tr>
</table>
 
 Error: Unauthorized
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
 <tr>
 <td valign="top"> Details:</td>
 <td valign="top"><PRE>No details available.</PRE></td>
 </tr>
</table>
</body>
</html>

PIDIRUSER & PIRWBUSER Keep Getting Locked

After a recent XI system copy my PIDIRUSER and PIRWBUSER keep getting locked by the kernel. I did not change the passwords from the system I copied yet this problem only occurs in the new copy. In SM21 it shows that SAPJSF locks it with repeated invalid login/passwords. It seems to occur every 20 minutes on the nose but I can't find any jobs that correspond to this timeframe.
I have been through the enchange profile a number of times and validated everywhere I can think of but I can't find anywhere in ABAP or JAVA where these users are embeded with the wrong password. I have also restarted multiple times during the system copy process and once just to try to stop this occuring. I've refreshed the caches, I've sync'ed with the SLD, I'm at a loss.
Anyone have any ideas where to procede?
Thanks
Phil

Thanks Moorthy,
I have gone through and changed my passwords for these two users per note 721548. Still the same issue is happening. I am somewhat puzzled since I have no jobs running under either user (at least none that should cause 3 failed logins in 20 minutes). Also, this is a relatively unused system with no developers logging on to use either the directory or the runtime workbench. So I really have no clue what is causing these failures. It is pretty clearly failing from Java trying to connect to ABAP but why?
Thanks for your help, I'll keep this open in case anyone wants a good mystery.
Phil

Int Server (ABAP Cache) - Cache Updated column shows "red"

...long read, appreciate your patience...
In the IB:Config, under Cache Notifications, I'm getting the red square in the Cache Updated column for all "ABAP Cache" entries (green for notification). The "Java Cache" and "Central Adapter Engine" entries are green all the way through.
I've read a bunch of other threads here, and I've read and worked through the entire "How to Handle Caches" document. I ran in to a couple issues, but I don't know how to solve them.....
1) When I run SXI_CACHE, I receive the following messages:
<green> "Cache contents are up to date"
<red> "Error during last attempt to refresh cache"
--->double-clicking shows: Error ID = BUSINESS_SYSTEM, Message = LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM
--->Running the LCR... fxn via SE37 is successful, so I don't understand why SXI_CACHE has a problem running it.
2) When I run the Cache Connectivity Test where the Yellow triangle is displayed for the IS-ABAP with message "Attempt to fetch cache data from Integration Directory not yet started or still in progress".
3) When I try to load http://<host>:<port>/CPACache/refresh?mode=delta or full, I get a "403 Forbidden - You are not authorized to view the requested resource." But I'm never prompted for a user/pw? Since I'm the only user in this XI box, I do have some of my logons saved in Internet Explorer - could it be using one of those without prompting me?
Note:
I have been experiencing on and off network issues, and the machine we have XI installed on is slow. I don't know if that could affect anything or not.
Thanks for taking the time to read this...
Brian
Message was edited by: Brian Vanderwiel

Thanks for the replies...
Prashanth,
I think SXI_CACHE is for items in the Java stack only (correct me if I'm wrong). The main problem I have is with items in the ABAP stack not making it in to the cache.
Moorthy,
I walked through the Readiness Check - everything passed except for the items I already mentioned (Cache test shows yellow). The document is a nice gathering of tests, but it doesn't offer any ideas has to how to correct problems encountered.
Integration_directory_hmi tested successfully, and I read through the other OSS Notes, but none solved the issue.

PI 7.1 Java Cache Refresh error

When performing Data Cache Refresh from Data Cache Overview on Java stack, I am getting login prompt for client 000, the Integration Server client is 100. We have maintained the new client as per SAP recommendations, not sure why the Data Cache Overview would prompt for client 000 and would not validate any user at all. There are no locks or discrepancies. Please advice.
Thanks.

Hi,
Here is part of defaulttrace file I got some portion from top of the file since the file is quite large to paste the contents here. Hope it can give some indications...
Thank you.
#1.5 #000C293A0C5D003B0000004B00000EFC00CA8C9112428951#1258497859358#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GUEST#3271####bdec5450d3ca11de9c29000c293a0c5d#HTTP Worker [9]##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The stream has already been taken by method [getWriter()].
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.getOutputStream(HttpServletResponseFacade.java:227)
 at com.sap.tc.webdynpro.serverimpl.core.adapter.AbstractHttpResponseAdapter.finalizeResponse(AbstractHttpResponseAdapter.java:122)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.finalizeRequest(RequestManager.java:657)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:340)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
 at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
 at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
 at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
 at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
#1.5 #000C293A0C5D003B0000004D00000EFC00CA8C9112428951#1258497859530#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#3271####bdec5450d3ca11de9c29000c293a0c5d#HTTP Worker [9]##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The stream has already been taken by method [getWriter()].000C293A0C5D003B0000004B00000EFC00CA8C9112428951#
#1.5 #000C293A0C5D0041000000A100000EFCFFFFFFFFFFFFFFFF#1258498099171#com.sap.conn.jco##com.sap.conn.jco######f1d68eb0d2fe11de8869000c293a0c5d#Thread[R3RoleDataSource_UpdateThread[918637153],5,SystemThreadGroup]##0#0#Error#1#/System/Server/Connector/Rfc#Plain###Context does not exist session id=com.sap.engine.session.exec.UserContextImpl@4c49a32d[ clientId=null, clientSessions=[], persistent Model=null]#
#1.5 #000C293A0C5D0041000000A200000EFCFFFFFFFFFFFFFFFF#1258498099202#com.sap.engine.services.dsr##com.sap.engine.services.dsr######f1d68eb0d2fe11de8869000c293a0c5d#Thread[R3RoleDataSource_UpdateThread[918637153],5,SystemThreadGroup]##0#0#Error##Plain###java.lang.NullPointerException
 at com.sap.jdsr.frame.ComponentStaticDataImpl0.getActionType(ComponentStaticDataImpl0.java:39)
 at com.sap.engine.services.dsr.jco.ClientStatisticsHandlerNew.callStarted(ClientStatisticsHandlerNew.java:59)
 at com.sap.conn.jco.rt.ClientConnection.beginCall(ClientConnection.java:212)
 at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:982)
 at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:987)
 at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:977)
 at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:300)
 at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo700Proxy$Client700.execute(R3JCo700Proxy.java:310)
 at com.sap.security.core.persistence.datasource.imp.R3RoleDataSource.checkBufferRefresh(R3RoleDataSource.java:2032)
 at com.sap.security.core.persistence.datasource.imp.R3RoleDataSource.access$000(R3RoleDataSource.java:57)
 at com.sap.security.core.persistence.datasource.imp.R3RoleDataSource$1.run(R3RoleDataSource.java:593)
 at java.lang.Thread.run(Thread.java:606)
#1.5 #000C293A0C5D0041000000A300000EFCFFFFFFFFFFFFFFFF#1258498099202#com.sap.conn.jco##com.sap.conn.jco######f1d68eb0d2fe11de8869000c293a0c5d#Thread[R3RoleDataSource_UpdateThread[918637153],5,SystemThreadGroup]##0#0#Warning##Plain###[JCoAPI] com.sap.conn.jco.JCoException: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.#
#1.5 #000C293A0C5D0041000000A400000EFCFFFFFFFFFFFFFFFF#1258498099202#com.sap.conn.jco##com.sap.conn.jco######f1d68eb0d2fe11de8869000c293a0c5d#Thread[R3RoleDataSource_UpdateThread[918637153],5,SystemThreadGroup]##0#0#Warning##Plain###[JCoAPI] JCoClient.beginCall(): cannot get jDSR passport for call 'PRGN_J2EE_GET_ROLES', because of com.sap.conn.jco.JCoException: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.#
#1.5 #000C293A0C5D002B0000010B00000EFC00CA8C91125EB259#1258498492812#com.sap.aii.utilxi.sld.XIIntegrationServer##com.sap.aii.utilxi.sld.XIIntegrationServer#J2EE_GUEST#13##[HostName]_[SID]_5701250#Guest#5b88f4a0d2fb11de881d000c293a0c5d#Application [1]##0#0#Warning##Java###No HTTPS Port for Integration Server is.00.[HostName] defined.
Thrown:
com.sap.aii.utilxi.misc.api.InvalidArgumentException: Parameter httpPort has the invalid value
 at com.sap.aii.utilxi.sld.SldUtil.constructHttpsUrl(SldUtil.java:331)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.setMsgUrlInclSecureUrl(XIIntegrationServer.java:557)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.setMsgUrls(XIIntegrationServer.java:507)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.syncBSInfo(XIIntegrationServer.java:267)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.readFromSld(XIIntegrationServer.java:242)
 at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:120)
 at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:142)
 at com.sap.aii.af.lib.sld.impl.SLDAccessor.getISData(SLDAccessor.java:248)
 at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getISData(SLDAccessImpl.java:47)
 at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:79)
 at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:182)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.NumberFormatException: For input string: ""
 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
 at java.lang.Integer.parseInt(Integer.java:468)
 at java.lang.Integer.<init>(Integer.java:620)
 at com.sap.aii.utilxi.sld.SldUtil.constructHttpsUrl(SldUtil.java:328)
 ... 14 more
#1.5 #000C293A0C5D002B0000010C00000EFC00CA8C91125EB259#1258498492812#com.sap.aii.adapter.xi.ms.SLDReader##com.sap.aii.adapter.xi.ms.SLDReader.fire()#J2EE_GUEST#13##[HostName]_[SID]_5701250#Guest#5b88f4a0d2fb11de881d000c293a0c5d#Application [1]##0#0#Warning##Java###The SLDAccess returned null values for the following fields: #1#SecureURL#
#1.5 #000C293A0C5D002B0000010D00000EFC00CA8C91125EB259#1258499392984#com.sap.aii.utilxi.sld.XIIntegrationServer##com.sap.aii.utilxi.sld.XIIntegrationServer#J2EE_GUEST#13##[HostName]_[SID]_5701250#Guest#5b88f4a0d2fb11de881d000c293a0c5d#Application [1]##0#0#Warning##Java###No HTTPS Port for Integration Server is.00.[HostName] defined.
Thrown:
com.sap.aii.utilxi.misc.api.InvalidArgumentException: Parameter httpPort has the invalid value
 at com.sap.aii.utilxi.sld.SldUtil.constructHttpsUrl(SldUtil.java:331)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.setMsgUrlInclSecureUrl(XIIntegrationServer.java:557)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.setMsgUrls(XIIntegrationServer.java:507)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.syncBSInfo(XIIntegrationServer.java:267)
 at com.sap.aii.utilxi.sld.XIIntegrationServer.readFromSld(XIIntegrationServer.java:242)
 at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:120)
 at com.sap.aii.utilxi.sld.XIEntityInSld.syncFromSld(XIEntityInSld.java:142)
 at com.sap.aii.af.lib.sld.impl.SLDAccessor.getISData(SLDAccessor.java:248)
 at com.sap.aii.af.lib.sld.impl.SLDAccessImpl.getISData(SLDAccessImpl.java:47)
 at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:79)
 at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:182)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.NumberFormatException: For input string: ""
 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
 at java.lang.Integer.parseInt(Integer.java:468)
 at java.lang.Integer.<init>(Integer.java:620)
 at com.sap.aii.utilxi.sld.SldUtil.constructHttpsUrl(SldUtil.java:328)
 ... 14 more

ABAP Cache Refresh: PIAPPLUSER gets locked

Similar Messages

Maybe you are looking for