Unable to log into the Endpoint Protection Manager (SEPM). with SQL and SEPM services started. Unexpected server error 0x10010000

Products

• Endpoint Protection

Issue/Introduction

• Unable to log into the Endpoint Protection Manager (SEPM). Error: Unexpected server error 0x0000000 
• SQL and SEPM services have all started. 
• No errors appear in the scm-server-x.log, showing successful authentication. 
• reporting.log (located by default here: %Program Files%\Symantec\Symantec Endpoint Protection Manager\Apache\Logs) will show the error: 
  [date:time] ERROR:warning: error at login. will retry once. error message : <b>Source:</b> Microsoft OLE DB Provider for ODBC Drivers<br/><b>Description:</b> [Microsoft][ODBC Driver 11 for SQL Server]Encryption not supported on the client.
  [date:time] ERROR:fatal error at login: \rEXCEPTION block1: Error message: <b>Source:</b> Microsoft OLE DB Provider for ODBC Drivers<br/><b>Description:</b> [Microsoft][ODBC Driver 11 for SQL Server]Encryption not supported on the client.\rError code: -2147352567\rFile and line: D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Php\Include\Common\ado.php(95)\r
  [date:time] ERROR:could not find valid username in session

Environment

• ODBC Driver 14.x or below for SQL server
• Microsoft command line utilities 14.0.x or below for SQL server

Cause

The error indicates that TLS 1.2 started to be enforced on the SQL server, and the SEPM does not have utilities that are compatible. 

Resolution

The SQL ODBC driver, command line utilities, and/or native client will need to be upgraded to one that supports TLS 1.2.

See Microst's documentation here: 
https://support.microsoft.com/en-us/help/3135244/kb3135244-tls-1-2-support-for-microsoft-sql-server

SEPM's requirements and download instructions are found in KB article 178648