Can we have all the list of Error from Sametime?

HCL Sametime Sametime Forum
,
1

During the installation of Sametime, we found various error in the log.

We need the list of ErrorCode.

For example:

[34;1mcommunity_1 |[0m stserver 2025-03-25 09:27:14.513 FINEST 98 --- 140025626453824 : Authentication for db723f44 0ac140013 returned <0, CN=CISGUG,OU=Sistemas,OU=PRODUCCION,OU=MyDomain,OU=OU Entidades,DC=DomainX,DC=ORG, CISGUG, , CN=CISGUG,OU=Sistemas,OU=PRODUCCION,OU=MyDomain,OU=OU Entidades,DC=DomainX,DC=ORG, cn=domino/o=test>
[34;1mcommunity_1 |[0m stserver 2025-03-25 09:27:14.513 FINEST 98 --- 140025626453824 : SelectiveStatus for <CN=CISGUG,OU=Sistemas,OU=PRODUCCION,OU=MyDomain,OU=OU Entidades,DC=DONOSTIA,DC=ORG, db723f44 0ac140013> returned, rc = -2147483116
[34;1mcommunity_1 |[0m stserver 2025-03-25 09:27:14.513 FINEST 98 --- 140025626453824 : Element login failed: eType=14e0, eId=db723f44 0ac140013, uId=CN=CISGUG,OU=Sistemas,OU=PRODUCCION,OU=MyDomain,OU=OU Entidades,DC=DomainX,DC=ORG, reason=80000214

2

Hi,

Most of the error code details are listed here -> https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0037378

Thanks

3

From what you have pasted above it looks like a user (or the bind account) could not login, we tried to look up this account in LDAP and could not. 80000214 means Sametime could not verify the login.

Check these things:

  • Check the beginning of the log from when Sametime was starting and make sure that the LDAP related services started up without errors (stusers, stresolve, stdirectory, userinfo).
  • Adding LDAP debug will improve the error messages. Click here for Docker. Click here for Kubernetes. The parameter you need is STI__DEBUG__VP_LDAP_TRACE, and use the value =1 for Docker, or : "1" for Kubernetes.
  • LDAP hostname is resolvable in DNS
  • LDAP port is reachable from the Sametime environment. If you have k8s, the traffic may come from the pod's IP range depending on your cluster set up.
  • If using the secure port, you MUST use a fully qualified domain name (FQDN) to reach LDAP and the FQDN that you use must match the LDAP server's certificate subject. (for ST 12.0.2). You can use openssl and connect to the secure port on your LDAP server to examine the subject of the certificate.
  • Check the LDAP bind credentials (name/password). You can test the credentials using ldapsearch (see KB0024811) or a client like "LDAP Browser".
  • If you are on Kubernetes, check this article for more troubleshooting.

Open a case with HCL Support if you need assistance.