SAP Knowledge Base Article - Preview

1422510 - Login to BILP / CMC takes a long time due to reverse DNS lookup

Symptom

  • Logging into BILP or CMC takes a long time, sometimes more than 20 sec
  • This happens regardless auditing is enabled or not
  • Once logged in, no network delays and everything works fine
  • For Windows AD SSO workflows, the delay may be noticed in the VintelaServlet HTTP call (Seen in a Browser trace F12)
    Eg:
    https://<HOST>/BOE/portal/2401260053/BIPCoreWeb/VintelaServlet?vint_backURL=%2FFioriBI%2Flogon.jsp&allowLogoff=true&appKind=InfoView&vint_cms=<CMS>%3A6400


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.1 ; SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Enterprise XI 3.0 ; SAP BusinessObjects Enterprise XI 3.1

Keywords

Dynamic DNS, zone, reverse lookup, named.conf, nsswitch.conf, resolv.conf, dig, nslookup, as112, slow, nbt, netbios over tcp/ip, in-addr.arpa, long time, logon, Windows AD logon performance, delay , KBA , logon , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , How To

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.