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

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

    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

  • Authorization Required for RFC user  in R/3-APO system.

    Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user  id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and  provide the required the authorization in R/3 and APO system.
    Regard
    Auroshikha

    The RFC authorisation depends completely on what the user is doing (ALEREMOTE?).  We can't tell you what RFC auths your connection requires. 
    There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

  • 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,

  • 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

  • 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

  • Trusted RFC not working for different user , working for same user

    Dear All,
    I have two SAP system - One Solman (7.0) and another ECC 6.0 (SR3) on HPUX box with Oracle DB (Unicode).
    I want to establish Trust relationship between these system.
    I have configured the same, as per the following link:
    http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm
    and note 128447.
    My requirement is one user X in solman client 001,
    will execute some test plan (Tcode stwb_2) which will take the control to ECC 6.0 client 200, execute the tcode as user Y and come back in Solman again.
    The user X (SAP_ALL) exists in Solman - client 001 and user Y (SAP_ALL) exists in ECC 6.0 - client 200.
    In ECC 6.0 client 200, I have created a role ZRFCACL with the following and assigned to the user Y (as per the above help / note):
    Role : ZRFCACL
    Auth. Obj: S_RFCACL
    Value assigned to fields are:
         RFC_SYSID : SOL
         RFC_CLIENT: 001
         RFC_USER  : X
         RFC_EQUSER: N
         RFC_TCODE : *
         RFC_INFO  : *
         ACTVT     : 16
    Whenever the user  X is trying to execute the test from solman, he is getting the error : "No authorization to log on as trusted system (RC = 0)"
    Each time the user is trying the above, in ECC 6.0, the following dump is occuring:
    CALL_FUNCTION_SINGLE_LOGIN_REJ under username SAPSYS
    I have assigned the role ZRFCACL to user X in Solman also.
    Next, I have performed the following check:
    created one user M in both system
    created the role ZRFCACL2 in ECC 6.0 client 200 as follows and assigned the role to user M:
         Role : ZRFCACL2
         Auth. Obj: S_RFCACL
         Value assigned to fields are:
              RFC_SYSID : SOL
              RFC_CLIENT: 001
              RFC_USER  : ''
              RFC_EQUSER: Y
              RFC_TCODE : *
              RFC_INFO  : *
              ACTVT     : 16
    Assigned SAP_ALL to user M in both system (So the user M in Solman does not have ZRFCACL2).
    This time, the trust relationship worked and no dump got generated.
    I have also checked the thread Trusted RFC do not work
    but unable to resolve the issue.
    Any suggestion where the things are going wrong in this / what else I need to check or this is not possible at all?
    Thanks in advance for your help.
    Sudip

    Hi Valdecir,
    Thanks for the reply. I am providing the detail of the generated dump below:
    Please check in case any clue is there.
    Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
    Date and Time          12.08.2008 18:59:32
    Short text
    No authorization to logon as trusted system (Trusted RC=0).
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An RFC call (Remote Function Call) was sent with the invalid user ID "98819 "
    . Or the calling system is not registered as trusted system in the
    target system.
    How to correct the error
    The error code of the trusted system was 0.
    Meaning:
    0    Correct logon as trusted system mode
    1 No trusted system entry for the calling system "SOL " or the
    security key entry for the system "SOL " is invalid
    2 User "98819 " does not have RFC authorization (authorization object
    (S_RFCACL) for user "98819 " witl client 001.
    3    The timestamp of the logon data is invalid
    The error code of the SAP logon procedure was 1.
    Meaning:
    0    Login was correct
    1    Wrong password or invalid user ID
    2    Locked user
    3    Too many attempted logons
    5    Error in the authorization buffer (internal error)
    6    No external user check
    7    Invalid user type
    System environment
    SAP-Release 700
    Application server... "gcbeccd"
    Network address...... "10.10.4.158"
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "gcbeccd"
    Database type..... "ORACLE"
    Database name..... "RD3"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 5 2008 00:55:24"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.1.0) "
    Patch level. 146
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 16192
    EM...... 4189840
    Heap.... 0
    Page.... 0
    MM Used. 1194640
    MM Free. 2992576
    User and Transaction
    Client.............. 000
    User................ "SAPSYS"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "489F2BD6C36D0F12E10000000A0A049E"
    Program............. "SAPMSSY1"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "SOL"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 001
    User................ 98819
    Transaction......... "SMSY"
    Call Program........."SAPLSRTT"
    Function Module..... "SCCR_GET_RELEASE_NR"
    Call Destination.... "SM_RD3CLNT200_TRUSTED"
    Source Server....... "gcbsolm_SOL_00"
    Source IP Address... "10.10.4.206"
    Additional information on RFC logon:
    Trusted Relationship "X"
    Logon Return Code... 1
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPMSSY1" - in
    "REMOTE_FUNCTION_CALL".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 67
    of the (Include) program "SAPMSSY1".
    Source Code Extract
    Line
    SourceCde
    37
    endmodule.
    38
    39
    module %_rfcdia_call output.
    40
    "Do not display screen !
    41
    call 'DY_INVISIBLE_SCREEN'.
    42
    perform remote_function_diacall.
    43
    endmodule.
    44
    45
    module %_cpic_start.
    46
    if sy-xprog(4) = '%RFC'.
    47
    perform remote_function_call using rfctype_external_cpic.
    48
    else.
    49
    call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
    50
    perform cpic_call using convid.
    51
    endif.
    52
    endmodule.
    53
    54
    55
    form cpic_call using convid type c.
    56
    communication send id convid buffer header.
    57
    if sy-subrc eq 0.
    58
    perform (sy-xform) in program (sy-xprog).
    59
    else.
    60
    message a800.
    61
    endif.
    62
    endform.
    63
    64
    form remote_function_call using value(type).
    65
    data rc type i value 0.
    66
    do.
    >>>>>
    call 'RfcImport' id 'Type' field type.
    68
    if sy-xprog = 'JAVA'.
    69
    system-call plugin
    70
    id 'JAVA' value 'FORW_JAVA'
    71
    id 'RC'   value rc.
    72
      if there is no rollout on the JAVA side which
    73
      rolls both, JAVA and ABAP, we return to the
    74
      C-Stack and reach this point
    75
    76
      in case there was an rollout, the ABAP-C stack is lost
    77
      and we jump direkt to this point
    78
    79
      here we trigger the rollout on this Abap side with
    80
      the following statement
    81
    system-call plugin
    82
    id 'JAVA' value 'ROLL_OUT'
    83
    id 'RC'   value rc.
    84
    else.
    85
    perform (sy-xform) in program (sy-xprog).
    86
    rsyn >scont sysc 00011111 0.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080812
    SY-UZEIT
    185932
    SY-XPROG
    SAPRFCSL
    SY-XFORM
    READ_SINGLE_LOGIN_DATA
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    2 FORM         SAPMSSY1                            SAPMSSY1                               67
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       2 Ty.          FORM
    Name  REMOTE_FUNCTION_CALL
    %_DUMMY$$
    0000
    0000
    2222
    0000
    SY-REPID
    SAPMSSY1
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    SYST-REPID
    SAPMSSY1
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    HEADER
    000000000000
    000000000000
    TYPE
    3
    0000
    0003
    SY-XPROG
    SAPRFCSL
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5455445422222222222222222222222222222222
    3102633C00000000000000000000000000000000
    %_ARCHIVE
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RC
    0
    0000
    0000
    SY-XFORM
    READ_SINGLE_LOGIN_DATA
    000000000000000000000000000000
    000000000000000000000000000000
    544455444445444445445422222222
    2514F39E7C5FCF79EF414100000000
    %_SPACE
    0
    0
    2
    0
    No.       1 Ty.          MODULE (PBO)
    Name  %_RFC_START
    %_PRINT
    000                                                                                0###
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RFCTYPE_INTERNAL
    3
    0000
    0003
    Internal notes
    The termination was triggered in function "ab_xsignon"
    of the SAP kernel, in line 2491 of the module
    "//bas/700_REL/src/krn/rfc/absignon.c#9".
    The internal operation just processed is "CALY".
    Internal mode was started at 20080812185932.
    Calling system.....: "SOL "
    Caller.............: "98819 "
    Calling client.....: 001
    RFC user ID........: "98819 "
    RFC client.........: 200
    Trusted return code: 0
    Logon return code..: 1
    Transaction code...: "SMSY "
    Active state.......: "-782823270"
    Note: At releases < 4.0, the information for the caller is not
    available.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (0)  0x4000000003b2b450  CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
    (1)  0x4000000004d2c470  Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
    (2)  0x4000000004d32160  ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
    (3)  0x4000000002b43cb0  SignOnDumpInfo + 0x280 at absignon.c:2491 [dw.sapRD3_DVEBMGS00]
    (4)  0x4000000002b3f2f0  ab_xsignon + 0xb30 at absignon.c:876 [dw.sapRD3_DVEBMGS00]
    (5)  0x4000000002aa4cb0  ab_rfcimport + 0x1ad0 at abrfcfun.c:3599 [dw.sapRD3_DVEBMGS00]
    (6)  0x40000000040f4a80  Z8abjcalyv + 0x500 [dw.sapRD3_DVEBMGS00]
    (7)  0x400000000402f190  Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
    (8)  0x4000000003f538b0  Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRD3_DVEBMGS00]
    (9)  0x4000000003f360a0  ab_dstep + 0x280 [dw.sapRD3_DVEBMGS00]
    (10) 0x4000000001cb4600  dynpmcal + 0x900 at dymainstp.c:2399 [dw.sapRD3_DVEBMGS00]
    (11) 0x4000000001cab0e0  dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRD3_DVEBMGS00]
    (12) 0x4000000001cb1ec0  dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
    (13) 0x4000000001c9dff0  dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
    (14) 0x4000000001fea460  Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
    (15) 0x4000000001fb4de0  TskhLoop + 0x4e20 at thxxhead.c:4518 [dw.sapRD3_DVEBMGS00]
    (16) 0x4000000001faae40  ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
    (17) 0x4000000001569ec0  DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
    (18) 0x4000000002c10630  nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
    (19) 0x4000000002c105c0  main + 0x60 [dw.sapRD3_DVEBMGS00]
    (20) 0xc00000000002be30  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSSY1
    0
    11.04.2005
    09:27:15
    22528
    E
    1
    Prg
    SAPLSCCA
    1
    05.07.2005
    13:10:18
    52224
    E
    2
    Prg
    SAPRFCSL
    0
    13.02.2005
    17:31:45
    17408
    E
    3
    Typ
    RFCSYSACL
    0
    13.02.2005
    17:31:45
    7168
    4
    Typ
    SYST
    0
    09.09.2004
    14:18:12
    31744
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  SAPMSSY1
    SYST                                       .  .       :  :     00004612
    \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
    Program  SAPRFCSL
    RFCSYSACL                                  .  .       :  :     00001760
    SOL                             RD3
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    116
    CLEA
    00
    0035
    SAPMSSY1
    60
    117
    CLEA
    00
    0036
    SAPMSSY1
    60
    118
    CLEA
    00
    0037
    SAPMSSY1
    60
    119
    MESS
    00
    001C
    SAPMSSY1
    60
    120
    ENDF
    00
    0000
    SAPMSSY1
    62
    121
    00
    0000
    SAPMSSY1
    62
    122
    PERP
    00
    0001
    SAPMSSY1
    64
    123
    PERP
    02
    0000
    SAPMSSY1
    64
    124
    WHIL
    00
    0002
    0000
    0000
    0000
    0000
    0000
    0000
    SAPMSSY1
    66
    128
    WHIL
    00
    0003
    0000
    0000
    0000
    0000
    0000
    0000
    SAPMSSY1
    66
    132
    BRAN
    05
    001E
    SAPMSSY1
    66
    133
    CALY
    00
    0003
    0038
    002A
    0005
    002B
    0000
    0000
    SAPMSSY1
    67
    >>>>>
    CALY
    02
    0000
    0039
    8000
    0000
    0000
    0000
    0000
    SAPMSSY1
    67
    141
    COMP
    00
    0002
    0010
    003A
    SAPMSSY1
    68
    143
    BRAF
    02
    000E
    SAPMSSY1
    68
    144
    SRFC
    01
    0000
    003A
    003B
    SAPMSSY1
    69
    146
    SRFC
    01
    0000
    003C
    C000
    SAPMSSY1
    69
    148
    SRFC
    02
    0000
    0000
    0000
    SAPMSSY1
    69
    150
    SRFC
    01
    0000
    003A
    003D
    SAPMSSY1
    81
    152
    SRFC
    01
    0000
    003C
    C000
    SAPMSSY1
    81
    Thanks & Regards
    Sudip

  • EREC : Lock SAP user ID for future date

    Hi ,
    Can anyone  suggest a way to Lock an SAP user id for a Future Date .
    Thanks in advance,
    Tk

    Hi,
    Instead of locking you can better delimit so that you can have a history for audit reasons.
    i dont find business requirement for locking user.
    thanks
    rafi

  • User lock persists for killed process

    Hi,
    We have an app that acquires a user lock (using dbms_lock, release_on_commit FALSE).
    We needed to kill a session but it remained in v$session (KILLED), even after killing the OS process. Fine, I know it will clear up eventually.
    But the user lock (UL) persists. Does anyone know how it can be force-released?
    Calling dbms_lock.release (using handle in v$lock) fails, even as user SYS, the error being that the user does not own the lock. But the owning session is killed so who can release it?
    Eventually the session (and lock) disappers from v$session/v$lock but can the lock be removed before then, to avoid a DB bounce in an urgent case?
    Thanks

    If the process was truely KILLED and not MARKED FOR KILL then I do not know what could of happened. I cannot remember Oracle ever failing to release a user lock when the acquiring session was terminated. We use a fair number of UL; however, few of our processes have concurrent sessions that attempt to use the same UL. Mostly we just ensure that batch processes do not get submitted twice and that some on demand processes run single threaded or do not run if another customer has submitted the task.
    HTH -- Mark D Powell --

  • Password for RFC USer

    Hi experts,
    We need to set the password for RFC User in small letters.But we are not able to do it ,because of our 'login/*' parameter values.
    Is there is any other method to create the password for User ID with small letters(Ex:welcome,hello)?
    Thanks in Advance,
    Karthika

    > > Login rules are not specific to user types. It is same for all type of users.
    > Sorry, this is not correct. The password validity rules are a good example which don't apply to SYSTEM and SERVICE type users. Other examples are the idle time rules and compliance to policy rules and the logon ticket rules and remote login via debugging rules and...
    >
    I tried to talk about is as per the ongoing discussion topic i.e. Case sensitiveness of Passwords and not other attributes. So from this point of view there is no such separate rule applies during admin imposed password or during a change (the cases where system prompts for changing password).
    > > From NAS 7 there is a change in the password rules.
    > There were major changes in 46B, and 6.10 and 6.40 as well, and Karthika still has not told us which release she is on.
    >
    Agreed totally.
    > > [Note 750390 - USR02: various problems with password attributes|https://service.sap.com/sap/support/notes/750390]
    > > [Note 624635 - Error messages with password change using RFC function|https://service.sap.com/sap/support/notes/624635]
    > I cannot see how these notes are related to this silly requirement of setting a lower-case only password.
    >
    I didn't went through in details fully but seen it contains a considerable error details.... may be of any help to OP.
    > I think either Karthika is playing a joke on us, or the person interviewing Karthika is playing a joke on her... These would be the only logical explanations left which I can see for for such a requirement.
    >
    May be.. but of course need more information and purpose of such strictness for setting such password. Also the FM PASSWORD_FORMAL_CHECK can be used with required customizations but you are the best person to tell this properly.
    regards,
    Dipanjan

  • RFC User for Connectivity with ABAP Server Proxy Required?

    Hi people,
    I am just wondering how I set-up my connectivity between XI and my business system B.
    Our basis already set-up the connection to the runtime workbench from B->XI
    For that sake they've added the xirwbuser to B (Xi has it as well, of course).
    Now I am configuring the whole thing in the Directory. There I need an receiver agreement and a channel. For that I take the adapter type "XI". Anyway, I need to give here an RFC destination as well. I've added one of type "H".
    And now the issue: Do I really need a separate user for that rfc connection? I thought with proxies the systems are somewhat like "hard-wired" and do not need special users.
    Anyway, if I need a dedicated RFC user: Is a certain role enough or do I need special roles depending on the stuff I am doing in the business system?
    Thanks in advance!
    Helge

    You can of course use an existing service user.
    But for monitoring purpose it is receommended to use a seperate user. (Think about system log entries).
    The user needs the role SAP_XI_APPL_SERV_USER.
    Regards
    Stefan

  • Not able to use password with characters for RFC User.

    hi All,
    I have installed SAP SCM 5.0 with MaxDB 7.6and liveCache 7.6.
    I created RFC user and RFC destination to administer liveCache globally as per SAP notes 305634 and 452745. I changed the initial passwords and tested Remote login for RFC User.
    But when I try to start liveCache with startrfc following the link below
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/95/379f3cad1e3251e10000000a114084/frameset.htm
    I got the following error
    RFC Call/Exception: SYSTEM_FAILURE
    Group       Error group 104
    Key         RFC_ERROR_SYSTEM_FAILURE
    Message     Name or password is incorrect (repeat logon)
    Then I logged into the CI with RFC user and try to start the liveCache with RSLVCSTART T-Code SE38..I got the following error.
    Error DBMCLI_COMMAND_EXECUTE_ERROR when starting liveCache LCS on server saplcslc
    Message no. LVC007
    I tried by changing the password for RFC user to numeric [0-9] and special characters [$,:] which worked fine.
    Does anyone faced this issue earlier? I searched notes, sdn and finally google ... but no luck to resolve the issue.
    Your help is much appreciated.
    Thanks,
    Venkat

    Yes I used LCA as liveCache connection. I resolved the issue with RSLVCSTART. Thanks for your suggestion to run connection test. I used wrong password for control user in the LCA connection. Now LCA connection shows everything is fine.
    But I am still not able to use alphanumeric password RFC user to start the liveCache from command line. I get the following when run startrfc command...
    bash-3.00$ /usr/sap/CAT/rfcsdk/bin/startrfc -3 -d LCSCLNT001 -h sapcatci -s 51 -c 001 -u LCSRFC -p Mach1cspsap\$ -l EN -F START_LIVECACHE_LVC -E IV_CON_NAME=LCA
    RFC Call/Exception: SYSTEM_FAILURE
    Group       Error group 104
    Key         RFC_ERROR_SYSTEM_FAILURE
    Message     Name or password is incorrect (repeat logon)
    bash-3.00$ echo $?
    1
    But I can start the liveCache from command line with numeric password successfully.
    bash-3.00$ /usr/sap/CAT/rfcsdk/bin/startrfc -3 -d LCSCLNT001 -h sapcatci -s 51 -c 001 -u LCSRFC -p 19811983\$ -l EN -F STOP_LIVECACHE_LVC -E IV_CON_NAME=LCA
    bash-3.00$ echo $?
    0
    Note the difference between the passwords used. Do i need to change any settings to accept alphanumeric passwords for RFC user.
    Note that I am able to start liveCache server in both cases(alphanumeric password and numeric password) by logging into SAP GUI and RSLVCSTART program. The problem is only when i try to start the liveCache from the commandline.
    Any help will be much appreciated.
    Thanks,
    Venkat

  • 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

  • Authorizations needed for MAM 2.5 for RFC user and business users

    Hello all,
    We are using MAM 2.5 application but we are facing authorizations issues.
    It seems we have not enough authorizations on RFC user used between middleware system and back-end system located on the RFC destination MAM on the middleware.
    And we don't find any SAP document related to this customizing.
    Moreover is there any other or same document deals with authorizations needed on the back-end for each user using MAM on its mobile device ?
    Thank in advance,
    Eric GOURDOU

    Hello,
    Can you send me the errors you have?
    If you have a trusted connection, then each users need the authorization S_RFCACL .
    Other than that, I never had to set any authorization for the plant maintenance scenarios of MAM.
    Thank you,
    Julien.
    msc mobile Canada
    http://www.msc-mobile.com

Maybe you are looking for