Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

"HTTP Status 412" appears when accessing the Deep Security Manager (DSM) console

    • Updated:
    • 23 Aug 2017
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 10.1
    • Deep Security 8.0
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 5 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • VMware ESX 4.0
    • VMware ESX 4.1
    • VMware ESX 5.0
    • VMware ESXi 4.0
    • VMware ESXi 4.1
    • VMware ESXi 5.0
    • VMware ESXi 5.1
    • VMware ESXi 5.5
    • VMware vCenter 5.0
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Server R2 Datacenter
    • Windows 2008 Server R2 with Hyper-V(TM)
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2012 Enterprise
Summary

The browser shows the following error when you open the Deep Security Manager (DSM) console:

HTTP Status 412 - The server failed to start. Please see the server0.log in the installation directory for more information.

HTTP Status 412 - The server failed to start

Details
Public

To resolve the error, identify first the cause of the issue by checking the server0.log. Below are the possible causes of the issue and their respective solutions:

 
Note that this error has many possible causes aside from the two causes listed below. For other possible reasons why the error occurs, check the related server0 logs.

The server0.log shows the following error:

SEVERE: Unable to initialize  java.lang.Exception: Insufficient Disk Space  at com.thirdbrigade.manager.core.Core.checkDiskSpace(Core.java:2033)  at com.thirdbrigade.manager.core.Core.startFull(Core.java:390)  at com.thirdbrigade.manager.core.Core.startFull(Core.java:261)  at com.thirdbrigade.manager.webclient.initialization.InitializeServlet.init(InitializeServlet.java:65)  at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206)  at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026)  at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421)  at org.apache.catalina.core.StandardContext.start(StandardContext.java:4734)  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)  at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)  at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)  at org.apache.catalina.startup.Embedded.start(Embedded.java:825)  at com.thirdbrigade.manager.service.Tomcat.startTomcat(Tomcat.java:134)  at com.thirdbrigade.manager.service.DSMService$WorkerThread.run(DSMService.java:226

As shown by server0.log, the issue occurs because the DSM has insufficient disk space, which makes the Apache Tomcat Web Server unable to start.

To resolve the issue, make sure there is enough available disk space to start the console.

The server0.log shows the following:

INFO: No global web.xml found  Jan 04, 2017 3:35:46 PM com.thirdbrigade.manager.core.Core startFull  INFO: ThID:15Initiating core full startup...  Jan 04, 2017 3:36:11 PM com.thirdbrigade.manager.core.Core processInitDatabase  WARNING: ThID:15|TID:0|TNAME:Primary|UID:-1|UNAME:|Unable to connect to the database. Retrying in 10 seconds  java.sql.SQLException: Network error IOException: Connection timed out: connect  at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:437)

To resolve the issue:

  1. Check the communication between the database and the DSM, and verify if SQL server is available.

  2. Restart the Deep Security Manager service.

  3. Refresh the DSM console. You should now be able to properly access it.

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1103151
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.