RFC user locked

Situation:
Partner can log into VTX, but got a RFC error when doing certain transactions.
Solution:
An locked user account was used in the definition of a RFC destination. Corrected via transaction "SM59".

Hi,
Thiugh am not exposed much to guixt the following document may help you to resolve your prob. Pl have a look.
http://www.synactive.com/download/sap%20gui%20scripting/sap%20gui%20scripting%20security%20settings.pdf
regards

Similar Messages

RFC users locked after system copy in production system

Hi,
BW_User,MDBTC(RFC users) system users were locked in our BI Production system at the same time system copy activity was running in the Quality system(production to quality) so as per our colleagues concern after system copy they started Quality system with out changing background work-process 0 so some jobs were triggered which were copied from production system.
Is there any cause to lock RFC users in production system for system copy? If there is any other reason where we can check logs
Thanks
Jalandhar Reddy

Hi,
Well maybe i am wrong to analyze your problem .
Anyway I faced this issue to in our system before and we found that one background job was running in a system that has basically prompting an RFC connection to another system. In the t.code SM59 and there was wrong password was put in.We just reset the password and it was worked fine.
You can try for this..
Regards
Bhuban
RKFL

RFC user locked for guixt

Hi,
The communication user for guixt keeps getting locked. The RFC username & encrypted password are in the guixtrfc.ini which is distributed to each user PC. I'm thinking that somebody tried to edit the guixtrfc.ini & changed the encrypted password.
I need a method to either find out which front end PC has the bad guixt.ini or prevent the communication user from being locked (not all user accounts).
Thanks.
Stephen S.

Hi,
Thiugh am not exposed much to guixt the following document may help you to resolve your prob. Pl have a look.
http://www.synactive.com/download/sap%20gui%20scripting/sap%20gui%20scripting%20security%20settings.pdf
regards

RFC User in CUA locked

Hello,
when i tried to unlock user both globally and locally (in cua) it failed..saying 'still the user is locked''..why ?
(refering rfc user here)
Thanks
Rajesh

Hi Rajesh,
Check this link:
When unlocking user ALEREMOTE, the user is still locked
Rajeev

RFC user get's locked

Hi experts,
We are using rfc_cua user for RFC communication between R/3 prd server and E-Rec prd server. Here issue is frequesntly rfc_cua user get's locked automatically. if we unlock the id it will work fine for one or two day and again it will get locked, There is no same amount of time gap between locking of this ID every time time. Kindly help me how to trace this issue.
Regards,
Sampath.

Are you using CUA or rfc user has been named just like that & what is E-Rec prd server .. is it SAP or something else ?
Dont u find something in change log of this user ??
thanks
ashish

Use of Adaptive RFC and locking

Hello,
I am using an adaptive RFC model inside a Web Dynpro Application to maintain data residing on a SAP Enterprise system.
This RFC also sets a lock in order to make sure nobody else tries to change the same data.
I use pessimistic locking which means:
1. Web Dynpro calls a RFC
2. The RFC first locks the data then reads the data and returns the result back to Web Dynpro
3. The user changes the data and presses a save button
4. Web Dynpro calls the RFC to write and unlock the data
The problem i have is the fact that after locking and reading of the data the RFC is ended and the data is received by the Web Dynpro App. But at the same moment the lock is automatically unlocked because the RFC has ended succesfully.
How can i achieve that the lock is still there at the moment i want to change the data or is this procedure of pessimistic locking not possible?
Bertil

Hi,
Whether possible or not : Don't know. Probably not with RFCs.
More importantly, shall you do it? If it is transactional data you are updating , you may wish to consider concurrency issues (what if you locked and came to web dynpro, and user is thinking whether he shall take a coffee break first before pressing the 'Save'. Would you like to keep this record(s) locked and unavailable for the entire duration?)
Normally, you would read the data in the first call, let the user update it on the second screen, and then, when the user presses save, execute in sequence :-
- try locking the record,
- if locking is successful, Verify whether the record you read has changed in the meanwhile or not (verify what you have in your workarea(before changes done by user) is the same as in DB, by reading again from the DB)
- If above check is successful, go ahead with the update else throw an error message to the user to redo the txn
- unlock, exit
hope this helps,
cheers,
Ajay

RFC User for satellite systems

Hello Gurus,
I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Many thanks in advance for your help
Miloslav Pudil
IDS Scheer
Prague
Czech Republic

>
Miloslav Pudil wrote:
> I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
> Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Hi Miloslav,
Technically, it will work that you define one common RFC user in your SolMan for communication (RFC BACK destination) from all connected managed systems.
BUT, I would never recommend it.
Once a managed system cause issues in your SolMan, you are not able (or at least it's much more difficult) to identify the managed system. Same happens, if a invalid password in the BACK destination leads to a locked user.
My recommendation: Spend the extra effort in creating a user per managed system. Operation will be much easier later.
See also this guide:
[Activating EarlyWatch Alert [EWA] in End Customeru2019s System |http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000567342009E]
Best regards,
Ruediger

PM Order is getting blocked by RFC user

Hi all, i'm facing the following problem. We've an FM that is invoked externally using an RFC user, that is used to change the status of an specific order. This FM first makes the ENQUEUE of the given object, with the following data:
    CALL FUNCTION 'ENQUEUE_ESORDER'
      EXPORTING
        mode_aufk            = 'S'
        aufnr                     = number
        _wait                     = 'X'
      EXCEPTIONS
        foreign_lock           = 1
        system_failure       = 2
        OTHERS               = 3 .
Then calls the standard FM STATUS_CHANGE_FOR_ACTIVITY and after that executes the
    CALL FUNCTION 'DEQUEUE_ESORDER'
         EXPORTING
              aufnr = number.
After that we have a COMMIT WORK.
Somehow and with no explicit reason, the given order remains locked by RFC user, sometimes for several hours.
This happen in Production System. We'd never get this kind of situation on pre-production.
Does anyone have any clue about this ???
Thanks for your kind attention.
Regards,

Hi Rahul,
Thanks for your answer. But it seems to me that the problem is not a question of authorization, because this same user is used in the same system for another processes.
For example, today we have an Order that is blocked in SM12 since 12:47:12 and the processes for closing it still remains active and waiting, but in another way for Orders of the same type during today, this situation doesn't occur and the respective processes were finished sucessfully.
Thanks anyway.
Regards,

User locked every two minutes

Hello,
my user is locked within two minutes after unlocking it.
Its Netweaver PI System.
What can I do, to find out what program my user locks?
If already checked following:
- all connections in SM59
- JAVA Default Trace
- Exchange profile
Please advice
Regards Christian

It is in the FAQ at the top of the page, in the main security page --> wikis -> best practices --> how to secure and analyze RFC connections.
Or via the [search|https://wiki.sdn.sap.com/wiki/dosearchsite.action?queryString=cardinalityANDRFC&where=conf_all&type=&lastModified=&contributor=&contributorUsername=] ...
Some (standard) scenarios do not by default support this cardinality requirement.
Cheers,
Julius

Reg:who is self, ALEREMOTE and BW RFC Users,

Hi All
While Loading any data Ensure all other users except self and ALEREMOTE or BW RFC users are locked out
My Question is who is self, ALEREMOTE and BW RFC Users, Iam also used to see these users names list in Process Overview(SM50)
plz clarify my dought
Regards
raamu
Please search the forum before posting a thread
Edited by: Pravender on May 6, 2011 11:14 AM

Good morning
I need to have visibility of what users are online (Excel) for audit/monitoring purposes.
We are having severe performance issues and want to understand how many users are online concurrently.
In other SAP systems one can audit who is online SM04. In SM04 all BPC users logged in through Excel show up as BPCADMIN. So there is no way to tell how many users are online.
BPC for Microsoft offers a feature to find who is online. There must be a way to do the same in Netweaver?
Thank you,
Catherine

PIRWBUSER user locked daily

Hi All,
daily i found this user PIRWBUSER is locked
i unlocked it manual but it is not a solution, i want to know why it is daily locked.
i checked tcode sm37 no scheduale jobs under this user.
i checked the exchangeProfile for the value of com.sap.aii.rwb.serviceuser.pwd and i put the actual value for the password of that user
but the problem still i found this user locked
so could you please help?
Thanks
Sherif

Hi,
Check the passwords everywhere n follow the steps.
First of all, compile a list of the names of the relevant users.
If you also want to change the user for the sending business systems (PIRWBUSER or a copy of this user) you have to be aware that you will have to change the password in all sending systems/adapters.
The passwords must be changed at the following places:
1. Transaction SU01 in the R/3 system
              Here, you must change the passwords on the R/3 ABAP side.
2. Exchange Profile - Server Settings
              Call the PI exchange profile using:
              http://<xi-host>:<j2ee-port> /dir/start/index.jsp
              --> Administration --> Exchange Profile
              Press the 'Connection' button and adjust the password accordingly for the user used here.
              Important: If the system issues the error message 'Password logon no longer possible - too many failed attempts', check in transaction SU01 whether the user used under 'Connection' has already been locked, and unlock that user if necessary.
3. Exchange Profile
              You must now change the passwords in all parameters of the exchange profile to make them available for the PI Java applications.
              To do this, start the exchange profile as described in section 2, and adjust the changed passwords in all parameters.
4. SLDAPICUST
              If a PI* user is set in transaction SLDAPICUST adjust the password for this user.
5. SM59 Destination INTEGRATION_DIRECTORY_HMI
              In transaction SM59, adjust the password of the user used in HTTP destination to an ABAP system INTEGRATION_DIRECTORY_HMI.
6. SM59 Destination SAPXIPP*
              In transaction SM59, adjust the passwords of the users used in the ABAP connections SAPXIPP*.
7. SLD Data Supplier in the J2EE
              Log on to the SAP NetWeaver Administrator (http://<server>:<port>/nwa). Under "Configuration Management --> Infrastructure --> Destinations", check the user in destinations SLD_Client and SLD_DataSupplier. Only if a PI* user is set here change the password for the relevant user.
8. PMI store destination in the J2EE
              Log on to the SAP NetWeaver Administrator (http://<server>:<port>/nwa). Under "Configuration Management --> Infrastructure --> Destinations", change the relevant user password in HTTP destination pmistore.
9. RFC destinations in J2EE
              Log on to the SAP NetWeaver Administrator (http://<server>:<port>/nwa). Under "Configuration Management --> Infrastructure --> JCo RFC Provider" change the password in the RFC destinations AII_RUNTIME, LCRSAPRFC and SAPSLDAPI* if a PI* user is set there. Choose 'Save' to transfer the changes.
              Important: If user SAPJSF is used here, do not change the password of this user, because it is also used in several J2EE applications. In this case, create a copy of user SAPJSF in transaction SU01 and use this copy in the JCo RFC Provider.
10. SM59 connections for end-to-end monitoring
              In transaction SM59, adjust the user password in all connections that start with PMI*. You have to adjust the connections both under 'ABAP Connections' and 'HTTP Connections to External Server'.
              In addition, adjust the passwords in the systems where the destinations are pointing to, if this is not the PI itself.
11. SM59 connections for GRMG monitoring
              In SM59, change the user password in all connections that start with XI_GRMG*. You have to adjust the connections under 'HTTP Connections to ABAP Systems' and under 'HTTP Connections to External Server'.
              In addition, adjust the passwords in the systems where the destinations are pointing to, if this is not the PI itself.
12. Now restart the J2EE Engine.
13. Connections from sending business systems
              In all sending systems, you must check whether you are using one of the service users to log on to the PI system, and change the passwords if necessary (PIAPPLUSER).
              For this purpose, check the relevant SM59 destinations and logon data in the sending adapters.
              If the sending system is a system with a release version < 7.00, note that you need to set the password in the XI system in accordance with the instructions in Note 807895 so that it is downward compatible. Alternatively, you can create a copy of the relevant service user for this special connection, assign the downward-compatible password to this user, and use this user for the connection.
Then check in transaction SU01 whether any users were locked during the changes as a result of failed logon attempts, and unlock these users if necessary.
Note:
Check all these things for user PIRWBUSER. It may be possible that some of the steps will not fit for you. i recommend to follow the same password everywhere.
regards
Aashish Sinha
PS : reward points if helpful

Invalid_jobdata when submitting job with rfc user

Hi,
I've created a function module in the erp system to remotly trigger a report program by a bw prossess chain.
When running in the forground it works fine, but the runtime is so long that I want it as a background job.
So I call job_open, job_submit, job_close in the function module. When I test the function module in the erp system with my dev user it opens a new job, adds a step and release correctly. It also runs fine if I intercept it in the debugger and change sy-uname to aleremote (the standard rfc user).
It does not work when it's acctually called rfc from the bw system. The job is opened, but job_submit throws invalid_jobdata.
Could this have anything to do with rfc or the executing user (which is of type SYSTEM)?

I've caught the execption so there is no dump, but I'm unable to determine why the function module job_submit gives invalid_jobdata only when the executing user is the aleremote user and only when the call originated (the call to my module) from a remote system (the module job_submit is called locally thru my module). Authorization for the user is sap_all, but I was woundering maybe the user type system could be a problem?

LOCKS checking user locked and SQL that he is executing

Hello all,
I have this script that inserts into a table the user causing the lock and the users waiting for the lock to be released.
What I would like to add into this the script is the SQL string that the user causing the lock and the users waiting for the the lock to be released are executing.
Can you help me on this?
Script that I have now:
insert into dba.sessions_bloq
select sysdate "Data", w.sid "SID E", s1.username "User E", s1.osuser "OS User E", s1.machine "Maquina E", s1.program "Programa E", s1.logon_time "Logon E",
s.ksusenum "SID B", s2.username "User B", s2.osuser "OS User B", s2.machine "Maquina B", s2.program "Programa B", s2.logon_time "Logon B"
,decode(r.ksqrsidt,
''MR'', ''Media Recovery'',
''RT'', ''Redo Thread'',
''UN'', ''User Name'',
''TX'', ''Transaction'',
''TM'', ''DML'',
''UL'', ''PL/SQL User Lock'',
''DX'', ''Distributed Xaction'',
''CF'', ''Control File'',
''IS'', ''Instance State'',
''FS'', ''File Set'',
''IR'', ''Instance Recovery'',
''ST'', ''Disk Space Transaction'',
''TS'', ''Temp Segment'',
''IV'', ''Library Cache Invalidation'',
''LS'', ''Log Start or Switch'',
''RW'', ''Row Wait'',
''SQ'', ''Sequence Number'',
''TE'', ''Extend Table'',
''TT'', ''Temp Table'',
r.ksqrsidt) "Tipo Lock"
from gv$session_wait w, x$ksqrs r, gv$_lock l, x$ksuse s, gv$session s1, gv$session s2
where w.wait_Time = 0
and w.event = ''enqueue''
and r.ksqrsid1 = w.p2
and r.ksqrsid2 = w.p3
and r.ksqrsidt = chr(bitand(p1,-16777216)/16777215)||
chr(bitand(p1,16711680)/65535)
and l.block = 1
and l.saddr = s.addr
and l.raddr = r.addr
and s.inst_id = userenv(''Instance'')
and w.sid = s1.sid
and w.inst_id = s1.inst_id
and s.ksusenum = s2.sid
and s.inst_id = s2.inst_id;
Thanks in advance

You can link to:
gv$sql
gv$sqltext_with_newlines
but, if doing this in a trigger, also look at these:
http://www.psoug.org/reference/system_events.html

Password inconsistancy issue with RFC users in ECC 6.0 System after upgrade

Hi,
We have upgraded the system from 4.7 to ECC 6.0, but facing the password inconsistancy problem for RFC users. We have set the parameters like "login/min_password_lng" as "8" and "login/password_downwards_compatibility" as "3" & RFC user Type is "system". Could you please suggest how to resolve the password inconsistancy issue.

Hi Chandan,
you need to run the txn. SECSTORE and there it will shows you all the RFCs that have inconsistent passwords. Please maintain the correct passwords there.
In case the existing passwords are no longer acceptable due to new security policies as per the new SAP version, you will have to change the password from SU01.
Regards,
Shitij

RFC function module always creating BPs with the same user name (RFC user )

Hi All
I posted the below question in a different area before. But thought it would be more suitable here.
Moderators - Please let me know if am doing any mistake.
Question:
I have a RFC function module in CRM that creates Business Partners in ECC (XD01 tcode).
I am using a dialog RFC destination configured in SM59 in CRM.
But my RFC function module in CRM is always creating the Business Partners in ECC with the RFC user id (the user that we maintain for the RFC destination in SM59).
This is a problem for the users because they are not able to track the actual person responsible for creating these Business Partners.
Can somebody please let me know how to solve this problem?
Thanks
Raj

Hi.
You may use the trust relationship between CRM and R/3 and in SM59 instead of set a specific username, you set the flag "current user".
With this flag, the system will access R/3 system with the user logged in CRM system. The Trust relationship must be created between CRM and R/3 in order to the system doesn't ask for a password to login in R/3.
If you need more details please reply.
Kind regards,
Susana Messias

RFC user locked

Similar Messages

Maybe you are looking for