XIC: User Id Aggregation failing because a NonStop User Id has a LAST-UNSUCCESSFUL-ATTEMPT Status of "* UNKNOWN *"

XIC: User Id Aggregation failing because a NonStop User Id has a LAST-UNSUCCESSFUL-ATTEMPT Status of "* UNKNOWN *"

Note:  This applies to XIC 1.31 and earlier releases.  The issue will be fixed in a future XIC release.  The solution provided is only a workaround until the release containing the fix is available

User id aggregation fails with the following error:

\XXXXXXX XYPRO Product:XYGATEIC Msg#2: Level:Fatal Msg:XIC java error:

This error occurs because during aggregation, a user id or multiple user ids on the NonStop have been determined to have a value of * UNKNOWN * in the LAST-UNSUCCESSFUL-ATTEMPT  field of the Safeguard user id or alias record.

1.  Check the XIC http.log file for confirmation. This log file is found in the OSS space on the NonStop at /users/<user id>/XYPRO/webservices/XYGATEIC/logs:

      Where <user id> is the user id that performed/owns the XIC installation.

       Note: there may be slight variances on the directory names.  This is dependent on the path names provided when XIC was installed.

      The HTTP log file will be named similar to the following:

      xic_<instance>_http.log

      Where <instance> is the name of the XIC instance, usually the NonStop node name.  This would have been determined when XIC was installed.

      Sample log file name:

      xic_chicago_http.log

   2. Confirm that the error is related to * UNKNOWN * being the value in the LAST-UNSUCCESSFUL-ATTEMPT field for the Safeguard user record.   The http.log file  should
       contain error information similar to the following:

      -------------------------------------------------
2023-10-13 17:49:02 INFO  - Request started from 172.25.10.201 for GET - 10.56.1
7.22:3609/NonStop/v2/Users?startIndex=1&count=50
2023-10-13 17:49:02 INFO  - Current Memory usage: 13500960 ,total memory: 648806
40 ,free memory: 51379680
2023-10-13 17:49:02 INFO  - XTR Connection. Session ID: 208230KL8JTS
2023-10-13 17:49:02 INFO  - Successful authentication by SECURITY.ADMIN.
2023-10-13 17:49:02 INFO  - Attempting to get all users
2023-10-13 17:49:02 INFO  - XTR Session ID:208230KL8JTS
2023-10-13 17:49:02 INFO  - Sending request to XTR...
2023-10-13 17:49:13 INFO  - XTR request complete.
2023-10-13 17:49:14 ERROR - Unable to parse dateTime for attribute: LAST-UNSUCCE
SSFUL-ATTEMPT
2023-10-13 17:49:14 ERROR - Unable to parse dateTime for attribute: LAST-UNSUCCE
SSFUL-ATTEMPT
2023-10-13 17:49:14 ERROR - Unable to parse dateTime for attribute: LAST-UNSUCCE
SSFUL-ATTEMPT
2023-10-13 17:49:16 INFO  - Successfully retrieved all users

------------------------------------------------------

3.  Step #2 can also be confirmed by doing a "SAFECOM INFO USER *.*, DETAIL" and a "SAFECOM INFO ALIAS *, DETAIL" on the NonStop.   The output should be checked for
     all user ids containing "* UNKNOWN * " in the LAST-UNSUCCESSFUL-ATTEMPT field.


4. Once the user id(s) or aliases containing "* UNKNOWN *" in the LAST-UNSUCCESSFUL-ATTEMPT field have been determined, a deliberate failed logon should be performed for
    each user id at issue.   This can be done by making a logon attempt using an incorrect password, as this will change the value of the LAST-UNSUCCESSFUL-ATTEMPT field for
    the given user to the date and time of the failed logon.

     Example:
  
     a. LOGON <user id>    (Where <user id> is a valid NonStop user id)

     b. Enter a bad password

     c. Check the value of the LAST-UNSUCCESSFUL-ATTEMPT field for <user id> by doing a "SAFECOM INFO USER <user id>,DETAIL"  or if it was an alias, a "SAFECOM INFO
        ALIAS  <alias>, DETAIL"


5.  After executing failed logons for all user ids/aliases with * UNKNOWN * in the LAST-UNSUCCESSFUL-ATTEMPT field, attempt aggregation again.  


If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.

    • Related Articles

    • XIC: Where can the XIC log files be found?

      There are three XIC log files: access.log error.log http.log The full log name will be in the following format: xic_<instance>_xxxx.log Where: <instance> is the name of the XIC instance provided at the time of installation. Usually, this is the name ...

    • XUA: RSA Authenticated user and SFTP

      Add the below setting to UAACL using XAC_EDIT_ACL. UAGROUP SN-RSA-MAP-TEST DESCRIPTION "RSA Logon with Mapping" FROM_USER $EVERYONE TO_USER support.sam MAP re:"GRP80.TST010" REPLACE "scottfob" EXIT MAP re:"SUPPORT.SAM" REPLACE "scottfob" EXIT MAP ...

    • A Reconcile Account on CyberArc should be a member of ACLGROUP $XIC_OWNER

      For changing and/or reconciling PASSWORD requests from CyberArk, XTR will perform the actual password change actions in Safeguard as a privileged user account such as 255,255. So, a service account, which is a 'Reconcile Account' on CyberArk, can be ...

    • XYPRO GUIs can't connect to the NonStop host after the host ip address is changed

      If the user cannot connect to the NonStop host after the host ip address has been changed, then both XYGATETR (XTR) on the NonStop host and the GUI must be modified to reflect the new ip address 1. If XYGATE/TR (XTR) is configured on multiple NonStop ...

    • XS1: "License status cannot be determine" error at logon prompt

      This may happen if there is a password mismatch. A logon is required to verify the license is valid. If that logon fails, a message will be displayed indicating the license status cannot be determined. To resolve this, the XTR user and password can ...