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

Create a technical support case if you need further support.

NTLMv2 for SQL authentication causes "HTTP Status 412" error in Deep Security Manager

    • Updated:
    • 17 Nov 2015
    • Product/Version:
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • N/A-N/A
Summary

Deep Security Manager (DSM) web page returns the following error message when you try to log in:

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

The server0.log shows the following entries:

Oct 28, 2015 11:29:43 AM com.thirdbrigade.manager.core.Core processInitDatabase
WARNING: ThID:17|TID:0|TNAME:Primary|UID:-1|UNAME:|Unable to connect to the database. Retrying in 10 seconds.
java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
                at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
                at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
                at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
                at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
                at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:352)
                at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
                at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:185)

Unfortunately, the issue still persists after performing the procedures in these articles:

Details
Public

Analyze the SQL Server ERROR.log if it contains the following entries:

2015-11-11 13:20:34.79 Logon Error: 17806, Severity: 20, State: 14. 
2015-11-11 13:20:34.79 Logon SSPI handshake failed with error code 0x80090302, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: IP xxx.xxx.xxx.xxx]. 
2015-11-11 13:20:34.79 Logon Error: 18452, Severity: 14, State: 1. 
2015-11-11 13:20:34.79 Logon Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: IP xxx.xxx.xxx.xxx]

The logs above show because DSM does not use NTLMv2 for SQL authentication by default. If you want to use NTLMv2, do the following:

  1. Open the dsm.properties file.
  2. Add the following line:

    database.SqlServer.useNTLMv2=true

  3. Save and close the dsm.properties file.
  4. Restart the Deep Security Manager service.

If the issue still happens, collect and send the following files to Trend Micro Technical Support:

  • server0.log
  • SQL Server ERROR.log
  • msinfo.nfo of SQL Server and DSM Server
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1112975
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.


Need More Help?

Create a technical support case if you need further support.