Luam

GALERA, INSTALEI O SQL SERVER 2017 E O MESMO NÃO INICIA, já FUI NO SERVICES.MSC E DAR ERRO AO TENTAR INICIAR, TENTEI DE TUDO E NÃO CONSEGUI, SERA QUE ALGUÉM PODERIA ME DAR UMA LUZ; SEGUE O ERRO APRESENTADO NO LOG: 2020-07-23 15:11:29.35 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Express Edition (64-bit) on Windows 10 Enterprise LTSC 2019 10.0 <X64> (Build 17763: ) 2020-07-23 15:11:29.37 Server UTC adjustment: -3:00 2020-07-23 15:11:29.37 Server (c) Microsoft Corporation. 2020-07-23 15:11:29.37 Server All rights reserved. 2020-07-23 15:11:29.37 Server Server process ID is 4552. 2020-07-23 15:11:29.37 Server System Manufacturer: 'To be filled by O.E.M.', System Model: 'To be filled by O.E.M.'. 2020-07-23 15:11:29.37 Server Authentication mode is MIXED. 2020-07-23 15:11:29.37 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL14.LUAMDBA\MSSQL\Log\ERRORLOG'. 2020-07-23 15:11:29.37 Server The service account is 'NT Service\MSSQL$LUAMDBA'. This is an informational message; no user action is required. 2020-07-23 15:11:29.37 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL14.LUAMDBA\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL14.LUAMDBA\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL14.LUAMDBA\MSSQL\DATA\mastlog.ldf 2020-07-23 15:11:29.37 Server Command Line Startup Parameters: -s "LUAMDBA" 2020-07-23 15:11:29.54 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2020-07-23 15:11:29.54 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2020-07-23 15:11:29.57 Server Detected 8085 MB of RAM. This is an informational message; no user action is required. 2020-07-23 15:11:29.57 Server Using conventional memory in the memory manager. 2020-07-23 15:11:32.10 Server Default collation: Latin1_General_CI_AS (Português (Brasil) 1046) 2020-07-23 15:11:32.72 Server Buffer pool extension is already disabled. No action is necessary. 2020-07-23 15:11:33.69 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled. 2020-07-23 15:11:33.69 Server Implied authentication manager initialization failed. Implied authentication will be disabled. 2020-07-23 15:11:34.42 Server The maximum number of dedicated administrator connections for this instance is '1' 2020-07-23 15:11:34.99 Server This instance of SQL Server last reported using a process ID of 4476 at 23/07/2020 15:08:22 (local) 23/07/2020 18:08:22 (UTC). This is an informational message only; no user action is required. 2020-07-23 15:11:35.11 Server Node configuration: node 0: 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. 2020-07-23 15:11:35.27 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. 2020-07-23 15:11:35.75 Server In-Memory OLTP initialized on lowend machine. 2020-07-23 15:11:38.30 Server Database Instant File Initialization: desabilitado. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required. 2020-07-23 15:11:38.67 Server CLR version v4.0.30319 loaded. 2020-07-23 15:11:38.89 Server Query Store settings initialized with enabled = 1, 2020-07-23 15:11:39.47 Server Software Usage Metrics is disabled. 2020-07-23 15:11:40.22 spid6s Starting up database 'master'. 2020-07-23 15:11:42.01 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2020-07-23 15:11:43.40 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2020-07-23 15:11:43.49 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2020-07-23 15:11:43.74 spid6s SQL Trace ID 1 was started by login "sa". 2020-07-23 15:11:43.74 spid6s Server name is 'DESKTOP-ALRRQVL\LUAMDBA'. This is an informational message only. No user action is required. 2020-07-23 15:11:44.85 spid16s A self-generated certificate was successfully loaded for encryption. 2020-07-23 15:11:44.85 spid16s Server is listening on [ 'any' <ipv6> 49676]. 2020-07-23 15:11:44.85 spid16s Server is listening on [ 'any' <ipv4> 49676]. 2020-07-23 15:11:44.85 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\LUAMDBA ]. 2020-07-23 15:11:44.85 spid16s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$LUAMDBA\sql\query ]. 2020-07-23 15:11:44.85 spid16s 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. 2020-07-23 15:11:45.12 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2020-07-23 15:11:45.12 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. 2020-07-23 15:11:45.12 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-ALRRQVL:LUAMDBA ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2020-07-23 15:11:45.12 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-ALRRQVL:49676 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2020-07-23 15:11:46.66 spid17s A new instance of the full-text filter daemon host process has been successfully started. 2020-07-23 15:11:47.90 spid6s Starting up database 'msdb'. 2020-07-23 15:11:47.90 spid9s Starting up database 'mssqlsystemresource'. 2020-07-23 15:11:48.03 spid9s The resource database build version is 14.00.1000. This is an informational message only. No user action is required. 2020-07-23 15:11:48.62 spid9s Starting up database 'model'. 2020-07-23 15:11:49.40 spid9s Polybase feature disabled. 2020-07-23 15:11:49.40 spid9s Clearing tempdb database. 2020-07-23 15:11:50.32 spid9s Starting up database 'tempdb'. 2020-07-23 15:11:50.71 spid20s The Service Broker endpoint is in disabled or stopped state. 2020-07-23 15:11:50.71 spid20s The Database Mirroring endpoint is in disabled or stopped state. 2020-07-23 15:11:51.21 spid20s Service Broker manager has started. 2020-07-23 15:11:51.33 spid6s Recovery is complete. This is an informational message only. No user action is required. MUITO OBRIGADO