SQL Server não inicia serviço com nenhuma conta

Question

Boa Tarde

Preciso muito da ajuda de vcs. sempre que tenho duvidas, recorro ao fórum e sempre sou ajudado (apenas lendo os comentários).

Mas dessa vez não achei nenhum que solucionasse meu problema.

Instalei o SQL Express 2012 no server 2012. mas o serviço sqlexpress não inicia. já tentei todas as contas possíveis (sistema local, serviço local e serviço de rede). 

Não sei como anexo um log de erro. mas vou tentar postar abaixo.

Me desculpe se não for assim. Segue o log.

2018-11-01 17:25:14.41 Server      Microsoft SQL Server 2012 - 11.0.2100.60 (X64) 
Feb 10 2012 19:39:15 
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2018-11-01 17:25:14.41 Server      (c) Microsoft Corporation.
2018-11-01 17:25:14.41 Server      All rights reserved.
2018-11-01 17:25:14.41 Server      Server process ID is 6848.
2018-11-01 17:25:14.41 Server      System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T430'.
2018-11-01 17:25:14.41 Server      Authentication mode is MIXED.
2018-11-01 17:25:14.41 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2018-11-01 17:25:14.41 Server      The service account is 'GRAFSERVER\SERVIDOR$'. This is an informational message; no user action is required.
2018-11-01 17:25:14.41 Server      Registry startup parameters: 
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2018-11-01 17:25:14.41 Server      Command Line Startup Parameters:
-s "SQLEXPRESS"
2018-11-01 17:25:14.65 Server      SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-11-01 17:25:14.65 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-11-01 17:25:14.65 Server      Detected 16287 MB of RAM. This is an informational message; no user action is required.
2018-11-01 17:25:14.65 Server      Using conventional memory in the memory manager.
2018-11-01 17:25:14.85 Server      This instance of SQL Server last reported using a process ID of 1636 at 01/11/2018 17:24:56 (local) 01/11/2018 20:24:56 (UTC). This is an informational message only; no user action is required.
2018-11-01 17:25:14.85 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-11-01 17:25:14.88 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.
2018-11-01 17:25:14.90 Server      Software Usage Metrics is disabled.
2018-11-01 17:25:14.91 spid5s      Starting up database 'master'.
2018-11-01 17:25:14.94 spid5s      81 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2018-11-01 17:25:14.96 Server      CLR version v4.0.30319 loaded.
2018-11-01 17:25:14.97 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2018-11-01 17:25:15.04 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-11-01 17:25:15.04 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2018-11-01 17:25:15.08 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-11-01 17:25:15.08 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-11-01 17:25:15.15 spid5s      SQL Trace ID 1 was started by login "sa".
2018-11-01 17:25:15.15 spid5s      Server name is 'SERVIDOR\SQLEXPRESS'. This is an informational message only. No user action is required.
2018-11-01 17:25:15.19 spid12s     A self-generated certificate was successfully loaded for encryption.
2018-11-01 17:25:15.20 spid12s     Server is listening on [ 'any' <ipv6> 53742].
2018-11-01 17:25:15.20 spid12s     Server is listening on [ 'any' <ipv4> 53742].
2018-11-01 17:25:15.20 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2018-11-01 17:25:15.20 spid12s     Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2018-11-01 17:25:15.20 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2018-11-01 17:25:15.20 spid12s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-11-01 17:25:15.20 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2018-11-01 17:25:15.22 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDOR.GrafServer.local:SQLEXPRESS ] for the SQL Server service. 
2018-11-01 17:25:15.22 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDOR.GrafServer.local:53742 ] for the SQL Server service. 
2018-11-01 17:25:15.32 spid13s     A new instance of the full-text filter daemon host process has been successfully started.
2018-11-01 17:25:15.33 Logon       Error: 18456, Severity: 14, State: 5.
2018-11-01 17:25:15.33 Logon       Login failed for user 'GRAFSERVER\SERVIDOR$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2018-11-01 17:25:15.35 spid5s      Starting up database 'msdb'.
2018-11-01 17:25:15.35 spid9s      Starting up database 'mssqlsystemresource'.
2018-11-01 17:25:15.35 Logon       Error: 18456, Severity: 14, State: 5.
2018-11-01 17:25:15.35 Logon       Login failed for user 'GRAFSERVER\SERVIDOR$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2018-11-01 17:25:15.35 spid5s      Error: 17204, Severity: 16, State: 1.
2018-11-01 17:25:15.35 spid5s      FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(O sistema não pode encontrar o caminho especificado.).
2018-11-01 17:25:15.36 spid5s      Error: 5120, Severity: 16, State: 101.
2018-11-01 17:25:15.36 spid5s      Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(O sistema não pode encontrar o caminho especificado.)".
2018-11-01 17:25:15.36 spid5s      Error: 17207, Severity: 16, State: 1.
2018-11-01 17:25:15.36 spid5s      FileMgr::StartLogFiles: Operating system error 2(O sistema não pode encontrar o arquivo especificado.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2018-11-01 17:25:15.36 spid5s      File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2018-11-01 17:25:15.36 spid9s      The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2018-11-01 17:25:15.38 spid9s      Starting up database 'model'.
2018-11-01 17:25:15.38 spid9s      Error: 17204, Severity: 16, State: 1.
2018-11-01 17:25:15.38 spid9s      FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(O sistema não pode encontrar o caminho especificado.).
2018-11-01 17:25:15.38 spid9s      Error: 5120, Severity: 16, State: 101.
2018-11-01 17:25:15.38 spid9s      Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(O sistema não pode encontrar o caminho especificado.)".
2018-11-01 17:25:15.38 spid9s      Error: 17207, Severity: 16, State: 1.
2018-11-01 17:25:15.38 spid9s      FileMgr::StartLogFiles: Operating system error 2(O sistema não pode encontrar o arquivo especificado.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2018-11-01 17:25:15.38 spid9s      File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2018-11-01 17:25:15.38 spid9s      Error: 945, Severity: 14, State: 2.
2018-11-01 17:25:15.38 spid9s      Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2018-11-01 17:25:15.38 spid9s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2018-11-01 17:25:15.49 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDOR.GrafServer.local:SQLEXPRESS ] for the SQL Server service. 
2018-11-01 17:25:15.51 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDOR.GrafServer.local:53742 ] for the SQL Server service. 

Answer 1

Jeff.

Parece que há mais de um problema neste log, conforme abaixo:

A mensagem a seguir parece indicar que o serviço subiu : 2018-11-01 17:25:15.20 spid12s     SQL Server is now ready for client connections. This is an informational message; no user action is required.

Apesar da mensagem acima, ainda há estes problema para resolver:

1 - falhar de login :

2018-11-01 17:25:15.35 Logon       Error: 18456, Severity: 14, State: 5 

2018-11-01 17:25:15.33 Logon       Login failed for user 'GRAFSERVER\SERVIDOR$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

2 - vários erros de arquivos não encontrados da base model

2018-11-01 17:25:15.35 spid5s      Error: 17204, Severity: 16, State: 1.
2018-11-01 17:25:15.35 spid5s      FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(O sistema não pode encontrar o caminho especificado.).

Sobre o 1 , verifique as contas que são criadas pelo setup do SQL Express na documentação e sobre o 2, você precisa verificar se estes arquivos estão nos locais indicados.

Espero ter ajudado

Atte.

Alex M. Bastos

Answer 2

Alex

Em primeiro lugar, muito obrigado pela sua atenção em dedicar um pouco do seu tempo a ajudar o próximo.

Foi verificando o que vc me passou que consegui solucionar. 

O arquivo MSDBData.mdf não estava na pasta. então percebi que o erro não estava apenas no serviço que não iniciava e sim na instalação que já tinha dado falha e não me atentei.

Caso ajude alguém, vou passar o que resolveu aqui pra mim.

Aqui na empresa tenho o mesmo servidor para controlador de domínio e para banco do sistema.

Então desinstalei toda a aplicação SQL, e com a ajuda desse tópico (https://blog.sqlauthority.com/2017/01/27/sql-server-sql-installation-fails-error-code-0x851a001a-wait-database-engine-recovery-handle-failed/), durante a nova instalação mudei o usuário do SQL Server Database manager para NT AUTHORITY\NETWORK SERVICE (por padrão vem com a conta do próprio SQL).

Depois disso finalizou a instalação sem erros e todos os serviços iniciaram perfeitamente.

Então fica a dica pra quem usa o servidor como controlador de domínio também ou caso na instalação do SQL de o erro 0x851A001A.

Mais uma vez obrigado Alex.