none
The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716)?

    Question

  • I installed sql server 2008 in my local machine, when i  try to start the MSSQLSERVER service , it give me the following errors:

    The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    When I try to log in from the management studio it give me the following errors:

    Cannot connect to tom-D.

    ===================================

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

    ------------------------------
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

    ------------------------------
    Error Number: 2
    Severity: 20
    State: 0


    ------------------------------
    Program Location:

       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
    Monday, July 13, 2009 6:57 PM

Answers

  • Looks like your model db has been moved/deleted:

    Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).
    2009-07-13 17:42:00.65 spid10s     Error: 5120, Severity: 16, State: 101.
    2009-07-13 17:42:00.65 spid10s     Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
    2009-07-13 17:42:00.67 spid10s     Error: 17207, Severity: 16, State: 1.
    2009-07-13 17:42:00.67 spid10s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or openi
    ng file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
    2009-07-13 17:42:00.67 spid10s     File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incor
    rect.

    Check the path and restore the files if you can (you can even copy the model db files from another sql instance if you can't restore them, as model is just used as a template db when creating new dbs, although you'll lose anything you had added to your original model db).



    ajmer dhariwal || eraofdata.com
    • Marked as answer by Jake Wardley Wednesday, July 15, 2009 1:08 AM
    Tuesday, July 14, 2009 4:28 PM
    Answerer

All replies

  • Have you checked the error log?

    This should give you some clues as to what the issue is. Default location is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\Errorlog

    Post the contents of the log if nothing stands out as a likely culprit.

    ajmer dhariwal || eraofdata.com
    Monday, July 13, 2009 8:16 PM
    Answerer
  • Hi, thank you for your answer.

    Here is the info from the log file:

    2009-07-13 16:13:25.62 Server      Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
        Feb  9 2007 22:47:07
        Copyright (c) 1988-2005 Microsoft Corporation
        Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

    2009-07-13 16:13:25.62 Server      Error: 17054, Severity: 16, State: 1.
    2009-07-13 16:13:25.62 Server      The current event was not reported to the Windows Events log. Operating system error = 1502(The event log file is full.). You may need to clear the Windows Events log if it is full.
    2009-07-13 16:13:25.62 Server      (c) 2005 Microsoft Corporation.
    2009-07-13 16:13:25.62 Server      All rights reserved.
    2009-07-13 16:13:25.62 Server      Server process ID is 1736.
    2009-07-13 16:13:25.62 Server      Authentication mode is WINDOWS-ONLY.
    2009-07-13 16:13:25.62 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2009-07-13 16:13:25.62 Server      This instance of SQL Server last reported using a process ID of 1924 at 7/13/2009 4:12:15 PM (local) 7/13/2009 8:12:15 PM (UTC). This is an informational message only; no user action is required.
    2009-07-13 16:13:25.62 Server      Registry startup parameters:
    2009-07-13 16:13:25.62 Server           -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2009-07-13 16:13:25.62 Server           -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2009-07-13 16:13:25.62 Server           -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2009-07-13 16:13:25.68 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2009-07-13 16:13:25.68 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2009-07-13 16:13:26.46 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.
    2009-07-13 16:13:26.53 Server      Database mirroring has been enabled on this instance of SQL Server.
    2009-07-13 16:13:26.54 spid3s      Starting up database 'master'.
    2009-07-13 16:13:27.28 spid3s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2009-07-13 16:13:27.62 spid3s      SQL Trace ID 1 was started by login "sa".
    2009-07-13 16:13:28.26 spid3s      Starting up database 'mssqlsystemresource'.
    2009-07-13 16:13:28.57 spid3s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
    2009-07-13 16:13:30.79 spid8s      Starting up database 'model'.
    2009-07-13 16:13:31.03 spid3s      Server name is 'myserver-D\SQLEXPRESS'. This is an informational message only. No user action is required.
    2009-07-13 16:13:31.10 spid3s      Starting up database 'msdb'.
    2009-07-13 16:13:31.93 Server      A self-generated certificate was successfully loaded for encryption.
    2009-07-13 16:13:32.07 Server      Server is listening on [ 'any' <ipv4> 1046].
    2009-07-13 16:13:32.12 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
    2009-07-13 16:13:32.12 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
    2009-07-13 16:13:32.20 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
    2009-07-13 16:13:32.46 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2009-07-13 16:13:32.88 spid8s      Clearing tempdb database.
    2009-07-13 16:13:36.70 spid8s      Starting up database 'tempdb'.
    2009-07-13 16:13:37.98 spid3s      Recovery is complete. This is an informational message only. No user action is required.
    2009-07-13 16:13:38.65 spid11s     The Service Broker protocol transport is disabled or not configured.
    2009-07-13 16:13:38.71 spid11s     The Database Mirroring protocol transport is disabled or not configured.
    2009-07-13 16:13:41.60 spid11s     Service Broker manager has started.
    2009-07-13 16:25:33.87 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.


    Thanks in advance.
    Monday, July 13, 2009 8:50 PM
  • This looks like a normal server startup.
    The server name is myserver-D\SQLEXPRESS. I notice the connection error you printed refers to a server called "tom-D".
    If it's the "tom-D" server you're having problems with, try and dig out the error log for that server.

    ajmer dhariwal || eraofdata.com
    Tuesday, July 14, 2009 5:43 AM
    Answerer
  • Hi, thank you for your answer.

    Here is the error info:

    2009-07-13 17:41:59.28 Server      Error: 17054, Severity: 16, State: 1.
    2009-07-13 17:41:59.28 Server      The current event was not reported to the Win
    dows Events log. Operating system error = 1502(The event log file is full.). You
     may need to clear the Windows Events log if it is full.
    2009-07-13 17:41:59.28 Server      (c) 2005 Microsoft Corporation.
    2009-07-13 17:41:59.28 Server      All rights reserved.
    2009-07-13 17:41:59.28 Server      Server process ID is 5608.
    2009-07-13 17:41:59.28 Server      Authentication mode is MIXED.
    2009-07-13 17:41:59.28 Server      Logging SQL Server messages in file 'C:\Progr
    am Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2009-07-13 17:41:59.28 Server      This instance of SQL Server last reported usi
    ng a process ID of 1712 at 7/13/2009 4:13:41 PM (local) 7/13/2009 8:13:41 PM (UT
    C). This is an informational message only; no user action is required.
    2009-07-13 17:41:59.28 Server      Registry startup parameters:
             -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
    \master.mdf
             -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\
    ERRORLOG
             -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
    \mastlog.ldf
    2009-07-13 17:41:59.29 Server      SQL Server is starting at normal priority bas
    e (=7). This is an informational message only. No user action is required.
    2009-07-13 17:41:59.29 Server      Detected 4 CPUs. This is an informational mes
    sage; no user action is required.
    2009-07-13 17:41:59.31 Server      SQL Server is not configured to use all of th
    e available system memory. To enable SQL Server to use more memory, set the awe
    enabled option to 1 by using the sp_configure stored procedure.
    2009-07-13 17:41:59.97 Server      Using dynamic lock allocation.  Initial alloc
    ation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an infor
    mational message only.  No user action is required.
    2009-07-13 17:42:00.00 Server      Node configuration: node 0: CPU mask: 0x00000
    00f Active CPU mask: 0x0000000f. This message provides a description of the NUMA
     configuration for this computer. This is an informational message only. No user
     action is required.
    2009-07-13 17:42:00.01 spid7s      Starting up database 'master'.
    2009-07-13 17:42:00.14 spid7s      Resource governor reconfiguration succeeded.
    2009-07-13 17:42:00.14 spid7s      SQL Server Audit is starting the audits. This
     is an informational message. No user action is required.
    2009-07-13 17:42:00.14 spid7s      SQL Server Audit has started the audits. This
     is an informational message. No user action is required.
    2009-07-13 17:42:00.15 spid7s      FILESTREAM: effective level = 0, configured l
    evel = 0, file system access share name = 'MSSQLSERVER'.
    2009-07-13 17:42:00.20 spid7s      SQL Trace ID 1 was started by login "sa".
    2009-07-13 17:42:00.20 spid7s      Starting up database 'mssqlsystemresource'.
    2009-07-13 17:42:00.25 spid7s      The resource database build version is 10.00.
    1600. This is an informational message only. No user action is required.
    2009-07-13 17:42:00.65 spid7s      Server name is 'IMEX-JAKEP-D'. This is an inf
    ormational message only. No user action is required.
    2009-07-13 17:42:00.65 spid10s     Starting up database 'model'.
    2009-07-13 17:42:00.65 spid10s     Error: 17204, Severity: 16, State: 1.
    2009-07-13 17:42:00.65 spid10s     FCB::Open failed: Could not open file e:\sql1
    0_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS erro
    r: 3(The system cannot find the path specified.).
    2009-07-13 17:42:00.65 spid10s     Error: 5120, Severity: 16, State: 101.
    2009-07-13 17:42:00.65 spid10s     Unable to open the physical file "e:\sql10_ma
    in_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(
    The system cannot find the path specified.)".
    2009-07-13 17:42:00.67 spid10s     Error: 17207, Severity: 16, State: 1.
    2009-07-13 17:42:00.67 spid10s     FileMgr::StartLogFiles: Operating system erro
    r 2(The system cannot find the file specified.) occurred while creating or openi
    ng file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagno
    se and correct the operating system error, and retry the operation.
    2009-07-13 17:42:00.67 spid10s     File activation failure. The physical file na
    me "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incor
    rect.
    2009-07-13 17:42:00.67 spid10s     Error: 945, Severity: 14, State: 2.
    2009-07-13 17:42:00.67 spid10s     Database 'model' cannot be opened due to inac
    cessible files or insufficient memory or disk space.  See the SQL Server errorlo
    g for details.
    2009-07-13 17:42:00.67 spid10s     Could not create tempdb. You may not have eno
    ugh 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.
    2009-07-13 17:42:00.67 spid10s     SQL Trace was stopped due to server shutdown.
     Trace ID = '1'. This is an informational message only; no user action is requir
    ed.

    C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn>sqlservr.ex
    e
    2009-07-13 17:43:24.23 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.2
    2 (Intel X86)
            Jul  9 2008 14:43:34
            Copyright (c) 1988-2008 Microsoft Corporation
            Enterprise Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)

    2009-07-13 17:43:24.23 Server      (c) 2005 Microsoft Corporation.
    2009-07-13 17:43:24.23 Server      All rights reserved.
    2009-07-13 17:43:24.23 Server      Server process ID is 2740.
    2009-07-13 17:43:24.23 Server      Authentication mode is MIXED.
    2009-07-13 17:43:24.23 Server      Logging SQL Server messages in file 'C:\Progr
    am Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2009-07-13 17:43:24.23 Server      This instance of SQL Server last reported usi
    ng a process ID of 5608 at 7/13/2009 5:42:00 PM (local) 7/13/2009 9:42:00 PM (UT
    C). This is an informational message only; no user action is required.
    2009-07-13 17:43:24.25 Server      Registry startup parameters:
             -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
    \master.mdf
             -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\
    ERRORLOG
             -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
    \mastlog.ldf
    2009-07-13 17:43:24.26 Server      SQL Server is starting at normal priority bas
    e (=7). This is an informational message only. No user action is required.
    2009-07-13 17:43:24.26 Server      Detected 4 CPUs. This is an informational mes
    sage; no user action is required.
    2009-07-13 17:43:24.28 Server      SQL Server is not configured to use all of th
    e available system memory. To enable SQL Server to use more memory, set the awe
    enabled option to 1 by using the sp_configure stored procedure.
    2009-07-13 17:43:24.94 Server      Using dynamic lock allocation.  Initial alloc
    ation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an infor
    mational message only.  No user action is required.
    2009-07-13 17:43:24.95 Server      Node configuration: node 0: CPU mask: 0x00000
    00f Active CPU mask: 0x0000000f. This message provides a description of the NUMA
     configuration for this computer. This is an informational message only. No user
     action is required.
    2009-07-13 17:43:24.98 spid7s      Starting up database 'master'.
    2009-07-13 17:43:25.09 spid7s      1 transactions rolled forward in database 'ma
    ster' (1). This is an informational message only. No user action is required.
    2009-07-13 17:43:25.12 spid7s      0 transactions rolled back in database 'maste
    r' (1). This is an informational message only. No user action is required.
    2009-07-13 17:43:25.12 spid7s      Recovery is writing a checkpoint in database
    'master' (1). This is an informational message only. No user action is required.

    2009-07-13 17:43:25.20 spid7s      Resource governor reconfiguration succeeded.
    2009-07-13 17:43:25.20 spid7s      SQL Server Audit is starting the audits. This
     is an informational message. No user action is required.
    2009-07-13 17:43:25.22 spid7s      SQL Server Audit has started the audits. This
     is an informational message. No user action is required.
    2009-07-13 17:43:25.23 spid7s      FILESTREAM: effective level = 0, configured l
    evel = 0, file system access share name = 'MSSQLSERVER'.
    2009-07-13 17:43:25.26 spid7s      SQL Trace ID 1 was started by login "sa".
    2009-07-13 17:43:25.26 spid7s      Starting up database 'mssqlsystemresource'.
    2009-07-13 17:43:25.29 spid7s      The resource database build version is 10.00.
    1600. This is an informational message only. No user action is required.
    2009-07-13 17:43:25.56 spid7s      Server name is 'IMEX-JAKEP-D'. This is an inf
    ormational message only. No user action is required.
    2009-07-13 17:43:25.56 spid10s     Starting up database 'model'.
    2009-07-13 17:43:25.56 spid10s     Error: 17204, Severity: 16, State: 1.
    2009-07-13 17:43:25.56 spid10s     FCB::Open failed: Could not open file e:\sql1
    0_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS erro
    r: 3(The system cannot find the path specified.).
    2009-07-13 17:43:25.58 spid10s     Error: 5120, Severity: 16, State: 101.
    2009-07-13 17:43:25.58 spid10s     Unable to open the physical file "e:\sql10_ma
    in_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(
    The system cannot find the path specified.)".
    2009-07-13 17:43:25.58 spid10s     Error: 17207, Severity: 16, State: 1.
    2009-07-13 17:43:25.58 spid10s     FileMgr::StartLogFiles: Operating system erro
    r 2(The system cannot find the file specified.) occurred while creating or openi
    ng file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagno
    se and correct the operating system error, and retry the operation.
    2009-07-13 17:43:25.58 spid10s     File activation failure. The physical file na
    me "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incor
    rect.
    2009-07-13 17:43:25.58 spid10s     Error: 945, Severity: 14, State: 2.
    2009-07-13 17:43:25.58 spid10s     Database 'model' cannot be opened due to inac
    cessible files or insufficient memory or disk space.  See the SQL Server errorlo
    g for details.
    2009-07-13 17:43:25.58 spid10s     Could not create tempdb. You may not have eno
    ugh 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.
    2009-07-13 17:43:25.59 spid10s     SQL Trace was stopped due to server shutdown.
     Trace ID = '1'. This is an informational message only; no user action is requir
    ed.


    Thanks in advance.
    Tuesday, July 14, 2009 1:32 PM
  • Looks like your model db has been moved/deleted:

    Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).
    2009-07-13 17:42:00.65 spid10s     Error: 5120, Severity: 16, State: 101.
    2009-07-13 17:42:00.65 spid10s     Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
    2009-07-13 17:42:00.67 spid10s     Error: 17207, Severity: 16, State: 1.
    2009-07-13 17:42:00.67 spid10s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or openi
    ng file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
    2009-07-13 17:42:00.67 spid10s     File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incor
    rect.

    Check the path and restore the files if you can (you can even copy the model db files from another sql instance if you can't restore them, as model is just used as a template db when creating new dbs, although you'll lose anything you had added to your original model db).



    ajmer dhariwal || eraofdata.com
    • Marked as answer by Jake Wardley Wednesday, July 15, 2009 1:08 AM
    Tuesday, July 14, 2009 4:28 PM
    Answerer