MSSQL Server stopped to Initiate the Service

  • Hello, Please need your help!

    I have SQL Server 2012 and stopped to start the service unexpectedly. I tried a lot to fix the problem by searching from online helps with all related errors I found from the event log with no success.  Below are the errors that I think may have direct or indirect effect to stop the service: 
    1- While trying to start the MSSQL Server instance, the error says :
      << The request failed or the service did not respond in a timely fashion. consult the event log or other applicable error logs for detail>>

    2.  From "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log", I found so many failed logins by hackers using a login names of: sa, Kisadmin, Chred1433, su, mssqla, hbv7,bwsa, 401hk and other names.

    3. From the event log,   I checked
      the application error as :
      <<Event ID 7034: The SQL server (MSSQLSERVER) service terminated unexpectedly. it has done this 1 times>>
     system error:
     <<Event ID: 36888: A fatal alert was generated and set to the remote endpont. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The windows SChannel error.
    System warning:
    <<Event ID: 1085: Windows failed to apply the internet explorer Zonemapping settings. Internet explorer Zonemapping settings might have its own log file. ..>>

    Attached is the screenshots of the errors. 

    Appreciate in advance for your help!!!

  • Have a look at this article http://www.sqlservercentral.com/articles/Disaster+Recovery/176729/
    😎

  • Hi Eirikur,
    Thanks for the reply to my problem! I tried as per the direction but no change. the  "TSSQLELX.bat [Drive letter] [/S] [/P] [/V] [/H] [/O]" on the cmd prompt displays only the information about each severity level of SQL Server.

  • elulu - Friday, November 23, 2018 11:04 PM

    Hi Eirikur,
    Thanks for the reply to my problem! I tried as per the direction but no change. the  "TSSQLELX.bat [Drive letter] [/S] [/P] [/V] [/H] [/O]" on the cmd prompt displays only the information about each severity level of SQL Server.

    You'll have to run the command from it's folder, with the drive parameter pointing to the drive where the log files are.
    😎

    If the the log files are on the C drive the this would be the command
    C:\TSES_V02>TSSQLEX.bat C

  • Hi Eirikur, 
    I did again the same way you said:C:\TSES_V02>TSSQLEX.bat C 
    It lists out the errors but didn't solve the problem. 

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply