Automic Workload Automation

Expand all | Collapse all

U00011801 Error in Server routine 'UCGENX_R'… U00020292 RunID 123456789 could not be found.

  • 1.  U00011801 Error in Server routine 'UCGENX_R'… U00020292 RunID 123456789 could not be found.

    Posted 03-19-2018 09:15 AM
    Today we saw the messages U00011801 and U00020292 in one of our AE systems:
    U00011801 Error in Server routine 'UCGENX_R', Server: 'AE_SYS1#WP001' AE system: 'AE_SYS1'.
    U00020292 RunID '123456789' could not be found.
    U00015006 System forced memory trace dump.
    Has anyone seen these messages before?

    Note: 123456789 is not the actual run ID. :smile:


  • 2.  U00011801 Error in Server routine 'UCGENX_R'… U00020292 RunID 123456789 could not be found.

    Posted 03-19-2018 09:25 AM
    Not this particular one, no.

    You encountered a very similar one it appears, so at least we know it's related to scripting going wrong.

    https://community.automic.com/discussion/12033/u00011801-error-in-server-routine-ucgenx-r-u00020292-runid-123456789-could-not-be-found

    https://community.automic.com/discussion/8689/u00003434-server-routine-ucgenx-r-pscript

    That RunID is curious though. Is that an actual RunID on your system, that awesomely sequential 123456789? The message in uc.msl has a variable for the RunID, so this is eother giant coincidence, or ...




  • 3.  U00011801 Error in Server routine 'UCGENX_R'… U00020292 RunID 123456789 could not be found.

    Posted 03-19-2018 09:52 AM
    Run IDs have been changed to protect the innocent.


  • 4.  U00011801 Error in Server routine 'UCGENX_R'… U00020292 RunID 123456789 could not be found.

    Posted 03-19-2018 09:55 AM
    lol, thanks :)

    I actually ran "strings 123456789" on the server binaries expecting to find this ID, thinking they's possibly coded it in as a special test case or something (and found several occurences of it, but as 0123456789 or 0123456789ABCDEF) :D