DescriptionNo Default Portal Available' Error in Captive Portal
SolutionIssue: End users may receive one of the following messages on the Network Sentry Captive Portal:
“No Default Portal Available. Unable to determine a Portal document to return. Please contact your system administrator so they can resolve the issue.”
OR
HTTP Status 500 Error
java.lang.NullPointerException
com.bsc.bean.PortalContentsBean.escapeName(PortalContentsBean.java:101)
com.bsc.jsp.portal.portalCommon.openView_jsp._jspService(openView_jsp.java:66)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965)
com.bsc.jsp.portal.index_002dhub_jsp._jspService(index_002dhub_jsp.java:112)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
com.bsc.bean.HttpOnlyFilter.doFilter(HttpOnlyFilter.java:64)
com.bsc.bean.EncodingFilter.doFilter(EncodingFilter.java:37)
Workaround: From the Network Sentry Application Server (NS8200/NS9200) or Network Sentry Server (NS500), restart the HTTPD and Tomcat-Portal Services. Type:
service httpd restart
service tomcat-portal restart
Solution: Configure a portal as a default portal to prevent this from occurring in the future.
- Navigate to System -> Portal Configuration -> Content Editor
- Select the portal selection drop-down menu on the bottom left and edit one of the portals.
- Select the Set as Default Portal check box.
As of Network Sentry releases 6.2.6, 7.0.4, and 7.1.1, instead of requiring the administrator to restart the tomcat-portal service in this situation, the service is restarted automatically.
