Skip to Content
author's profile photo Former Member
Former Member

Locked due to incorrect logons ! (Lock 130)

users are being locked due to incorrect logon attempts, but the usual lock type of 128 for this type of error is not happening.

these users are being locked with 130.

when trying to replicate the problem using a test user on the same system, the account is locked with 128.

any thoughts?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 04, 2008 at 01:49 AM
    • upated: when looking in the change documents (su01) history for the account, the new lock value is 130 with text "incorrect logon lock" which i've never seen before. apologies for the confusion. basically 128 is the 'usual' value i'm used to seeing associated with incorrect logon attempts, and i'm curious if anyone has seen 130 before? **

    users are being locked due to incorrect logon attempts, but the usual lock type of 128 for this type of error is not happening.

    these users are being locked with 130.

    when trying to replicate the problem using a test user on the same system, the account is locked with 128.

    any thoughts?

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Julius,

      some insights on the "new package concept" are published in the [1st hand article by Andreas Blumenthal and Horst Keller|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f2dac69e-0e01-0010-e2b6-81c1e8e5ce50]:

      Packages enhance the features of development classes, and allow you to control access to repository objects at design time. SAP plans to enhance the access control into the runtime realm in an upcoming release. Packages can be nested; nesting of packages means layering - an embedded package can't access the contents of its surrounding packages (this limitation will be overcome with the planned new package concept).

      This is a declarative approach; the ABAP runtime provides access control support. In previous releases it was required to evaluate the ABAP callstack programmatically (as practised by some kernel routines ...). Also, ABAP OO provides some access control mechanism using the "friend" concept.

      Cheers, Wolfgang

      Edited by: Wolfgang Janzen on Jan 6, 2008 12:24 PM

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2008 at 08:59 PM

    Hi,

    Where are you seeing this '130'? (SE16? a report output? an external tool?)

    Cheers,

    Julius

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 02:47 PM
    • ANSWER found **

    turns out that the Helpdesk did not unlock all users fully/completely using our custom tool, which puts a value of "2" in the UFLAG field. when users accidentally locked themselves out, this added the normal "128" value to the "2" making it "130"

    thanks to all who helped on this one!

    users are being locked due to incorrect logon attempts, but the usual lock type of 128 for this type of error is not happening.

    these users are being locked with 130.

    when trying to replicate the problem using a test user on the same system, the account is locked with 128.

    any thoughts?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.