Solved: 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.

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi RMS1348,

I don't see the essential role has been added to your PIISUSER so please ensure to add role 'SAP_XI_IS_SERV_USER_MAIN' to your PIISUSER. And also for other left over Service Users ensure you have these below roles assigned.

PILSADMIN - SAP_XI_CMS_SERV_USER

PIREPUSER - SAP_XI_IR_SERV_USER_MAIN

PIDIRUSER - SAP_XI_ID_SERV_USER_MAIN

PILDUSER - SAP_BC_AI_LANDSCAPE_DB_RFC

PIAPPLUSER - SAP_XI_APPL_SERV_USER

PIRWBUSER - SAP_XI_RWB_SERV_USER_MAIN

PIAFUSER - SAP_XI_AF_SERV_USER_MAIN

PIPPUSER - SAP_XI_APPL_SERV_USER

Once after adding these roles to your service users, you are allowed to perform 'delta' cache refresh using PIISUSER id also.

Regards

Sekhar

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sekhar,

Roles for PIISUSER and other service users already had proper authorization as you mentioned. The roles and authorizations I posted in my previous reply was for PISUPER user. However I added role SAP_XI_IS_SERV_USER_MAIN to PISUPER and also double checked all authorizations and roles for all other users both in ABAP and NWA and they are all valid. I am still getting the same login prompt (from client 000) / access denied error. Please advice if any new findings.

Thank you for your valuable input and help in getting this resolved.

Best regards and wishes.

Hi RMS1348,

Please ignore that 000 in the logon prompt that system show when you click on either delta or full refresh.

it's hardcoded and has nothing to do your authorization. B'coz even in a good working system you get to see that 000 client listed in popup window.

It's purely authorization issue and nothing else.

As a next step, Please perform refreshing once again and provide whatever userID & password you are using and then collect 'defaulttrace' information and post in your next reply.

Regards

Sekhar

Hi Sekhar,

Which file output should I post? I found several files for defaultrace from defaultTrace_00.0.trc to defaultTrace_00.14.trc. The latest updated and it is more than 2.5 MB big. Do you have any path to look for this file?

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/tc_wddispwda#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)