Symptom
- Error "The Web Assistant is not available. BILaunchpad may not have access to the internet or the proxy is not configured."
- In Browser F12 debugger traces, library.js fails with HTTP 500 error.
- Sometimes the Webassistant help button could also be disabled
-
Found the below errors in tomcat stderr logs:
javax.net.ssl|ALL|53|http-nio-8080-exec-6|xxxx|SSLSessionImpl.java:839|Invalidated session: Session(XX|SSL_NULL_WITH_NULL_NULL)
javax.net.ssl|ALL|53|http-nio-8080-exec-6|xxxx|SSLSessionImpl.java:839|Invalidated session: Session(XX|TLS_AES_128_GCM_SHA256)
javax.net.ssl|FINE|53|http-nio-8080-exec-6|xxxx|SSLSocketOutputRecord.java:73|WRITE: TLS13 alert(handshake_failure), length = 2
javax.net.ssl|FINE|53|http-nio-8080-exec-6|xxxx|SSLCipher.java:2013|Plaintext before ENCRYPTION
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform (BI) 4.2 SP05+
- Any supported web application server (Eg. Tomcat)
- Windows
- Linux / Unix
Product
Keywords
The Web Assistant is not available. BILaunchpad may not have access to the internet or the proxy is not configured. , KBA , ============ , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , 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.