Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    9
  • Views views
    566
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CICS Screen (TPX) Error - INVALID GROUP (User ID not found in group)

Venkat Samuvel

Hello Everyone,

We have upgraded our TEST server to v5.0 PU24 recently and we are getting the error message “INVALID GROUP” in TPX screen when we tried to login through ID which is defined in Non-default external security (MLDAP ESM).

This issue occurred post upgrade.

Please find the details from console log:

220704 23301820       7368 TST3-ONL ESFEM1045I ESM1: MLDAP: Set number of login attempts for user VSSS54: (0) Success 23:30:18

220704 23301822       7368 TST3-ONL ESFEM1060I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(microfocus-MFDS-Group-Member=VSSS54))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Data,dc=local" succeeded 23:30:18

220704 23301822       7368 TST3-ONL ESFEM1033I ESM1: MLDAP: User VSSS54 is in group SYSADM 23:30:18

220704 23301822       7368 TST3-ONL ESFEM1033I ESM1: MLDAP: User VSSS54 is in group CICSAPPL 23:30:18

220704 23301825       7368 TST3-ONL ESFEM1033I ESM1: MLDAP: User VSSS54 is in group NCIR005G 23:30:18

220704 23301828       7368 TST3-ONL ESFEM1033I ESM1: MLDAP: User VSSS54 is in group NMAPS06G 23:30:18

220704 23301832       7368 TST3-ONL ESFEM1033I ESM1: MLDAP: User VSSS54 is in group NFIN (default group) 23:30:18

220704 23301834       7368 TST3-ONL ESFEM1060I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(|(microfocus-MFDS-Group-Member=group SYSADM)(microfocus-MFDS-Group-Member=SYSADM group)))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Data,d: not found 23:30:18

220704 23301836       7368 TST3-ONL ESFEM1060I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(|(microfocus-MFDS-Group-Member=group CICSAPPL)(microfocus-MFDS-Group-Member=CICSAPPL group)))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Da: not found 23:30:18

220704 23301854       7368 TST3-ONL ESFEM1060I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(|(microfocus-MFDS-Group-Member=group NCIR005G)(microfocus-MFDS-Group-Member=NCIR005G group)))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Da: not found 23:30:18

220704 23301879       7368 TST3-ONL ESFEM1060I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(|(microfocus-MFDS-Group-Member=group NMAPS06G)(microfocus-MFDS-Group-Member=NMAPS06G group)))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Da: not found 23:30:18

220704 23301918       7368 TST3-ONL ESFEM1034I ESM1: LDAP search for "(&(objectclass=microfocus-MFDS-Group)(cn=G_MFC_PR))" in "CN=Enterprise Server User Groups,CN=Micro Focus,CN=Program Data,dc=local": not found 23:30:19

220704 23301918       7368 TST3-ONL CASSE0005W SIGNON fail. Terminal B000, TranId CESX, Program TPXCESNC, User VSSS54. 23:30:19

Any changes required in ESM configuration or some config file in order to fix this issue. Please assist me at the earliest.

Thanks in Advance

Labels:

Enterprise Developer
Parents
  • 0  

    Hi Venkat,

    Which changes have been made, and do they coincide with the start of the errors?

    There are several events in your sample console.log entries, with the "not found" contained. For each of these I recommend you to check and confirm that the groups/users being referenced in those events are setup as you expect. If you require further assistance I strongly recommend you to consider raising a support case to seek further assistance, e.g. where my colleagues can suggest appropriate tracing to investigate further. Please consider to mark this post as answered if it helps you progress to a solution.

Reply
  • 0  

    Hi Venkat,

    Which changes have been made, and do they coincide with the start of the errors?

    There are several events in your sample console.log entries, with the "not found" contained. For each of these I recommend you to check and confirm that the groups/users being referenced in those events are setup as you expect. If you require further assistance I strongly recommend you to consider raising a support case to seek further assistance, e.g. where my colleagues can suggest appropriate tracing to investigate further. Please consider to mark this post as answered if it helps you progress to a solution.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.