CNC, DB and Operating System - JDE1 (MOSC)

MOSC Banner

Failed to get extended token

edited Nov 25, 2011 4:58AM in CNC, DB and Operating System - JDE1 (MOSC) 5 comments
Hi,

An user (user1) always runs the R03B50 and this calls the R03B50D.

Now, the R03B50D is not running.

But if other user (user2)  runs, this works fine.

  • jdedebug.log to the user1:
    LANCHUBE--Default queue for R03B50D from parent report: QBATCH
    Entering JDB_AuditingOn
    Exiting JDB_AuditingOn with success
    Try to get an extended token by a regular token
    Failed to get extended token: eSecInvalidToken: The security token is invalid
    Failed to get extended token: eSecInvalidToken: The security token is invalid
    Success get an extended token by using regular token
    KNT0000087 - Could not get extended duration token.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center