Symptom
- Users receive intermittent timeout errors when logging into BI applications via LDAP. The Enterprise users can login successfully without any error. (BI launchpad, BI mobile, CMC, client tools etc)
- Errors are more common after times of inactivity such as early in the morning
- The BOE web application may become completely unavailable at times
- Timeout when logging into BILaunchpad or Mobile App
- After entering in the credentials and clicking logon, the application will sit and eventually display an error stating: timeout.
- CMS logs could show something like this below. Note the username should be visible, and a long timeout in excess of 85 secdonds, then the CMS checks to see if the connection went down.
BIP::CMS:Logon
CSessionMgr::AcceptLogonEx inAuthMethod:secLDAP)
LDAP: LdapQueryForEntries: *QUERY* base: baseDN, scope: 2, filter: (&(objectclass=person)(cn=username)), attribute: dn objectclass
LDAP: LdapQueryForEntries: *QUERY* result: 85 took 85040 ms
LdapQueryForEntries: Last query timed out. Retrying to see if connection went down.
SecLdap Error: an error occurred in LdapGetUserEntry().
LDAP: SecLdap Error: an error occurred in LdapGetUserEntry().
C3rdParty::AcceptLogin() -- 3d-party plugin returned an empty string as the alias.
C3rdParty::AcceptLogin() -- 3d-party login failed, but unable to determine for which user!
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.2 / 4.3)
- Windows
- Linux / Unix
Product
SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 4.3
Keywords
zie lightweight directory access protocol SP fp patch , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.