Based on the ERROR.LOG located at C:\Program Files\Microsoft SQL Server\MSSQL13.OFFICESCAN\MSSQL\Log\Error.log, the following error lines can be seen:

2019-05-01 05:08:41.61 spid10s     Error: 17182, Severity: 16, State: 1. 
  2019-05-01 05:08:41.61 spid10s     TDSSNIClient initialization failed with error 0xd, 
status code 0x4. Reason: All protocols are disabled. The data is invalid.
  2019-05-01 05:08:41.61 spid10s     Error: 17182, Severity: 16, State: 1.
  2019-05-01 05:08:41.61 spid10s     TDSSNIClient initialization failed with error 0xd, 
status code 0x1. Reason: Initialization failed with an infrastructure error. 
Check for previous errors. The data is invalid.  

The SQL service fails because all protocols are disabled, and it was not able to establish connection to the SQL server.

The issue happens because the connection to the SQL server cannot be established as a result of all protocols being disabled.

To resolve this issue, the required protocols must be enabled. Do the following steps:

1. Open SQL Server Configuration Manager.
2. Expand SQL Server Network Configuration.
3. Highlight Protocols for (INSTANCENAME).
4. At the right side of the screen enable the following:
   • Named Pipes
   • Shared Memory
   • TCP/IP
5. Reboot the server to allow the changes to take effect.
6. Once rebooted check if the SQL service is already started.

If the still happens after performing the recommended solution, collect the following log files below and submit it to Trend Micro Technical Support.

• Error.log file located in C:\Program Files\Microsoft SQL Server\MSSQL13.OFFICESCAN\MSSQL\Log\
• System Event Viewer log

  To collect the System Event Viewer log do the following:

  1. Simultaneously press the Windows key + R on the keyboard to open the Run window.
  2. Type "eventvwr", and click OK.
  3. Expand Windows logs.
  4. Right click on System.
  5. Click Save All Events As..