none
SQL Server Service is stoping with an Error Code : 1814 RRS feed

  • Question

  • Hi,

    I have an SCCM Server in My organization. Where we have installed Microsoft SQL Server 2008 R2 for the database of SCCM Application.

    Now I am not able to Start the SCCM console due to some dependent Services are not starting. 3 services has to be started for the perfect working of SCCM.

    1)SQL Server

    2) SQL Server Agent

    3) SQL Server Reporting Services

    Out of three the first two services are not starting at all. I am getting an error while trying to start SQL Server Services.

    Windows Could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the system event Log, If this is a non-Microsoft Service, contact the service vender , and refer to service-specific error code 1814."

    Please help me to start the services and resolve the SCCM Server issue.

    Thanks,

    Henoy TM

    +918888631370

    Thursday, April 11, 2013 5:10 AM

All replies

  • Hello Henoy,

    Please check also the ERRORLOG file for more details about the reason, why SQL Server service won't start. The ERRORLOG text file is located in

    C:\Program Files\Microsoft SQL Server\MSSQL105.<InstanzName>\MSSQL\Log\

    where <InstanzName> is the name of your instance, e.g. SQLEXPRESS


    Olaf Helper

    Blog Xing

    Thursday, April 11, 2013 5:47 AM
  • Hi Xing,

    I have check the Error Log : Please find the logfile details:

     

    2013-04-11 11:11:57.54 Server      Microsoft SQL Server 2008 R2 (SP1) - 10.50.2811.0 (X64)
     Apr  6 2012 01:59:29
     Copyright (c) Microsoft Corporation
     Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    2013-04-11 11:11:57.54 Server      (c) Microsoft Corporation.
    2013-04-11 11:11:57.54 Server      All rights reserved.
    2013-04-11 11:11:57.54 Server      Server process ID is 10348.
    2013-04-11 11:11:57.54 Server      System Manufacturer: 'HP', System Model: 'ProLiant DL380 G6'.
    2013-04-11 11:11:57.54 Server      Authentication mode is WINDOWS-ONLY.
    2013-04-11 11:11:57.54 Server      Logging SQL Server messages in file 'H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2013-04-11 11:11:57.54 Server      This instance of SQL Server last reported using a process ID of 4428 at 4/11/2013 10:41:54 AM (local) 4/11/2013 5:11:54 AM (UTC). This is an informational message only; no user action is required.
    2013-04-11 11:11:57.54 Server      Registry startup parameters:
      -d H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
      -T 8295
      -T 4199
    2013-04-11 11:11:57.56 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2013-04-11 11:11:57.56 Server      Detected 8 CPUs. This is an informational message; no user action is required.
    2013-04-11 11:11:57.59 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2013-04-11 11:11:57.61 Server      Node configuration: node 0: CPU mask: 0x00000000000000f0:0 Active CPU mask: 0x00000000000000f0:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2013-04-11 11:11:57.61 Server      Node configuration: node 1: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2013-04-11 11:11:57.66 spid9s      Starting up database 'master'.
    2013-04-11 11:11:58.24 spid9s      Resource governor reconfiguration succeeded.
    2013-04-11 11:11:58.24 spid9s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2013-04-11 11:11:58.24 spid9s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2013-04-11 11:11:58.24 spid9s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2013-04-11 11:11:58.27 spid9s      SQL Trace ID 1 was started by login "sa".
    2013-04-11 11:11:58.27 spid9s      Starting up database 'mssqlsystemresource'.
    2013-04-11 11:11:58.29 spid9s      The resource database build version is 10.50.2811. This is an informational message only. No user action is required.
    2013-04-11 11:11:58.38 spid9s      Server name is 'SGL-PANJ-SCCM'. This is an informational message only. No user action is required.
    2013-04-11 11:11:58.39 spid12s     Starting up database 'model'.
    2013-04-11 11:11:58.39 Server      The certificate [Cert Hash(sha1) "6E37DB5BAE65C704EF7C1BA0DE6587F34B5E8A53"] was successfully loaded for encryption.
    2013-04-11 11:11:58.40 Server      Server is listening on [ 'any' <ipv6> 1433].
    2013-04-11 11:11:58.40 Server      Server is listening on [ 'any' <ipv4> 1433].
    2013-04-11 11:11:58.40 Server      Server local connection provider is ready to accept connection on [ \\ . \pipe \SQLLocal \ MSSQLSERVER].
    2013-04-11 11:11:58.40 Server      Server named pipe provider is ready to accept connection on [ \\. \ pipe\ sql \ query].
    2013-04-11 11:11:58.40 Server      Server is listening on [ ::1 <ipv6> 1434].
    2013-04-11 11:11:58.40 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
    2013-04-11 11:11:58.40 Server      Dedicated admin connection support was established for listening locally on port 1434.
    2013-04-11 11:11:58.41 Logon       Error: 17187, Severity: 16, State: 1.
    2013-04-11 11:11:58.41 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 172.17.5.20]
    2013-04-11 11:11:58.42 spid12s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
    2013-04-11 11:11:58.42 spid12s     Error: 927, Severity: 14, State: 2.
    2013-04-11 11:11:58.42 spid12s     Database 'model' cannot be opened. It is in the middle of a restore.
    2013-04-11 11:11:58.42 spid12s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
    2013-04-11 11:11:58.42 spid12s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2013-04-11 11:11:58.43 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2013-04-11 11:11:58.43 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2013-04-11 11:11:58.52 Logon       Error: 17188, Severity: 16, State: 1.
    2013-04-11 11:11:58.52 Logon       SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: ::1]
    2013-04-11 11:11:58.54 Logon       Error: 17188, Severity: 16, State: 1.
    2013-04-11 11:11:58.54 Logon       SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: 192.168.6.2]
    2013-04-11 11:11:58.57 spid15s     A new instance of the full-text filter daemon host process has been successfully started.
    2013-04-11 11:11:58.60 spid16s     Starting up database 'ReportServer'.
    2013-04-11 11:11:58.60 spid17s     Starting up database 'ReportServerTempDB'.
    2013-04-11 11:11:58.60 spid18s     Starting up database 'CM_P01'.
    2013-04-11 11:11:58.60 spid15s     Starting up database 'msdb'.
    Cannot close event log because there are still event handle users active.

     

    Regards,

    Henoy

    Thursday, April 11, 2013 6:13 AM
  • 2013-04-11 11:11:58.42 spid12s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by ...

    Hello Henoy,

    Seems your disk is full, please check this first and free some space.


    Olaf Helper

    Blog Xing

    Thursday, April 11, 2013 6:16 AM
  • Hi Xing,

    I Have plenty of Disk space in all the Drives. That is more than 50% space is free in Each drives.

    Regards,

    Henoy

    Thursday, April 11, 2013 6:17 AM
  • 2013-04-11 11:11:58.42 spid12s     Could not create tempdb. ... Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.


    Can you see further details in Windows EventLog, why the TempDB can't be created?

    Olaf Helper

    Blog Xing

    Thursday, April 11, 2013 6:38 AM
  • Form the event logs I am getting an error code : 7024 which says

    The SQL Server (MSSQLSERVER) service terminated with service-specific error The specified resource name cannot be found in the image file..

    Regards,

    Henoy

    Thursday, April 11, 2013 6:45 AM
  • Please help me on this.
    Thursday, April 11, 2013 8:56 AM
  • I agree with Olaf's observations.  refer to service-specific error code 1814 and Could not create tempdb. You may not have enough disk space available. is a fairly clear indication that SQL Server's not happy with the location of your current TempDB.

    Are you able to start SQL Server in minimal configuration. e.g.

    Stop all the SQL Services

    In a DOS window, type sqlservr.exe -f (if it's not in your path environment variable, you will have to navigate to it)

    Once the SQL service has started, in DOS type "sqlcmd -Sservername\instancename"

    When the 1> comes up, type in 1> "sp_helpdb 'tempdb'"

    2> Go

    You'll get an entry for every TempDB data/log file.  Can you check the paths for each of these and ensure there's enough space to accommodate the current "size" from the result set?



    Thanks, Andrew

    Thursday, April 11, 2013 9:18 AM
  • run commando prompt as administrator then type the following command:

    net start mssql$TYPE_YOUR_SQL_INSTANCE_HERE /T3608

    Wednesday, March 25, 2015 8:04 PM