on 06-25-2009 2:01 PM
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 Jens,
is the PIAPPLUSER defind in tcode SU01 as a
PI 7.0 - service user
PI 7.10 system user
Regards
Kenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jens,
if the PIAPPLUSER is not being used from connected Business systems, e.g., ABAP Proxy connections and it is consistent in all the PI components then perhaps you are connected to a shared SLD. If so then the PIAPPLUSER should have the same password there in the SLD (and also other PI SLD client system.
Regards
Kenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
in XI run transaction SLDAPICUST, change the password of PIAPPLUSER here also.........moreover in all connected SAP systems accessing XI SLD, run this transaction there also and change the password of PIAPPLUSER..........then unlock PIAPPLUSER and run SLDCHECK and now i think your PIAPPLUSER should not be locked........Moreover in exchange profile, check where you have used PIAPPLUSER and change its password there also........
Regards,
Rajeev Gupta
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
Hi,
Ask your basis guys to change the service user passwords as said in a SAP Note.........i dont remember the SAP note number but your basis guys can search it by giving change service user passwords.................
Only change the service user passwords as said in this SAP Note.....then in SLDAPICUST give your new password for PIAPPLUSER....also change your service user passwords in exchange profile...then restart your XI system and then run SLDCHECK to see if your SLDCHECK is running fine............
Regards,
Rajeev Gupta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
can you please check THIS ENTRY IN VA .
alos check given link may be helfull for you .
http://help.sap.com/saphelp_nw70/helpdata/EN/8f/67d27676ace84080964d4c4223bb3c/frameset.htm
Regards,
Amit
Edited by: Amit Shivhare on Jun 25, 2009 6:39 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
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.