Question:
Can somebody provide a quickfix?
This is happening in our QA box.
Whenever I click 'Schedule' from the context menu of an InfoPackage, the login dialog for the source system (R/3) pops up.
This also happens when I click on the 'Details' tab of the monitor.
And in SM59, when I do a remote login from BW, the login window pops up again, when it is not supposed to.
Our basis team is on it for the last 2 hours and not been ablr to come up with anything. It was working well till yesterday.
Our security team is also looking into the profiles.
I've got a host of user-acceptance tests lined up for today and next week in the QA system, before transporting stuff to the production system during labor day weekend.
PS: From the status->detailed analysis, the 'RFC to source system successful?' is grey and the monitor remains yellow
_________________
Keep smiling
Answer:
Did someone change the logon password of the RFC user?
Answer:
Did someone change password parameters (restricting with numbers, length of password, etc...)
Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Everbody (basis & security) claim that they have changed nothing. Since I am the "system owner", I can see everything, and nothing is changed.
They now say that the problem has been escalated to the third level.
_________________
Keep smiling
Answer:
It is probably easier to re-create the source system.
Answer:
It turns out that the Basis/Security manager who sits right next to me, did a change for initial password reset parameters, to comply with an audit finding in R/3! It seems that it blew all CPIC users!!
It was reset to what it was, and all's well folks!
Thanks for all your responses!
(Since the parameter was changed, I couldn't see any changes in SM59).
Lessons learnt: Tell the auditor that initial password resets/vaildity limit does not apply to ALEREMOTE (or BWREMOTE or APOREMOTE) or all system users in general. Else the RFC links do not work!
_________________
Keep smiling
Answer:
It turns out that the Basis/Security manager who sits right next to me, did a change for initial password reset parameters, to comply with an audit finding in R/3! It seems that it blew all CPIC users!!
told ya! I had a very similar issue last weekwhen use TMSADM (use for tranposrt) could not be created because it did not follow Security guidelines following an audit.
Glad you resolved this.
Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759