SQL server refused to start

V5 Question
1

I have an abrupt issue with SAMBA V5. I opened the software today and it refused to start. i looked into the service and discovered that the issue is with the SQLServer. It has refused to start saying

The dependency service or group failed to start

The error log file shows

    2018-09-12 14:31:22.46 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.

    2018-09-12 14:31:22.46 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.

How do i fix the problem please?

2

I have this in windows 10 every now and then no sql servers start and I need to manual start them

1 Like
3

Just start the service and look into ways to retry auto start if it fails on boot up.

1 Like
4

Yes, usually manually starting it fixes this problem however this time around i am now getting this message

The dependency service or group failed to start

5

I set it to autostart. Didn’t help.

i even changed Log On to " Local system account". It didn’t make any different. This is the first time that manually starting it isnt working

6

2018-09-12 14:31:22.20 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)

Aug 22 2017 17:04:49

Copyright (C) 2017 Microsoft Corporation

Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 10586: )

2018-09-12 14:31:22.20 Server UTC adjustment: 1:00

2018-09-12 14:31:22.20 Server (c) Microsoft Corporation.

2018-09-12 14:31:22.21 Server All rights reserved.

2018-09-12 14:31:22.21 Server Server process ID is 10200.

2018-09-12 14:31:22.21 Server System Manufacturer: ‘LENOVO’, System Model: ‘80M3’.

2018-09-12 14:31:22.21 Server Authentication mode is WINDOWS-ONLY.

2018-09-12 14:31:22.21 Server Logging SQL Server messages in file ‘C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG’.

2018-09-12 14:31:22.21 Server The service account is ‘NT Service\MSSQLSERVER’. This is an informational message; no user action is required.

2018-09-12 14:31:22.21 Server Registry startup parameters:

-d C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\master.mdf

-e C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG

-l C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

2018-09-12 14:31:22.22 Server Command Line Startup Parameters:

-s “MSSQLSERVER”

2018-09-12 14:31:22.25 Server SQL Server detected 1 sockets with 4 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.

2018-09-12 14:31:22.25 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2018-09-12 14:31:22.25 Server Detected 4008 MB of RAM. This is an informational message; no user action is required.

2018-09-12 14:31:22.25 Server Using conventional memory in the memory manager.

2018-09-12 14:31:22.29 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2018-09-12 14:31:22.37 Server Buffer pool extension is already disabled. No action is necessary.

2018-09-12 14:31:22.46 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.

2018-09-12 14:31:22.46 Server Implied authentication manager initialization failed. Implied authentication will be disabled.

2018-09-12 14:31:22.49 Server The maximum number of dedicated administrator connections for this instance is ‘1’

2018-09-12 14:31:22.49 Server This instance of SQL Server last reported using a process ID of 7204 at 9/12/2018 2:29:44 PM (local) 9/12/2018 1:29:44 PM (UTC). This is an informational message only; no user action is required.

2018-09-12 14:31:22.49 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.

2018-09-12 14:31:22.50 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-09-12 14:31:22.52 Server In-Memory OLTP initialized on lowend machine.

2018-09-12 14:31:22.56 Server Database Instant File Initialization: enabled. 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.

2018-09-12 14:31:22.56 Server Query Store settings initialized with enabled = 1,

2018-09-12 14:31:22.57 Server Software Usage Metrics is disabled.

2018-09-12 14:31:22.58 spid6s Starting up database ‘master’.

2018-09-12 14:31:22.61 Server CLR version v4.0.30319 loaded.

2018-09-12 14:31:22.74 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2018-09-12 14:31:22.74 spid6s Error: 9003, Severity: 20, State: 1.

2018-09-12 14:31:22.74 spid6s The log scan number (6640:144:1) passed to log scan in database ‘master’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

2018-09-12 14:31:22.74 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

2018-09-12 14:31:22.74 spid6s SQL Server shutdown has been initiated

2018-09-12 14:31:22.20 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)

Aug 22 2017 17:04:49

Copyright (C) 2017 Microsoft Corporation

Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 10586: )

2018-09-12 14:31:22.20 Server UTC adjustment: 1:00

2018-09-12 14:31:22.20 Server (c) Microsoft Corporation.

2018-09-12 14:31:22.21 Server All rights reserved.

2018-09-12 14:31:22.21 Server Server process ID is 10200.

2018-09-12 14:31:22.21 Server System Manufacturer: ‘LENOVO’, System Model: ‘80M3’.

2018-09-12 14:31:22.21 Server Authentication mode is WINDOWS-ONLY.

2018-09-12 14:31:22.21 Server Logging SQL Server messages in file ‘C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG’.

2018-09-12 14:31:22.21 Server The service account is ‘NT Service\MSSQLSERVER’. This is an informational message; no user action is required.

2018-09-12 14:31:22.21 Server Registry startup parameters:

-d C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\master.mdf

-e C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG

-l C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

2018-09-12 14:31:22.22 Server Command Line Startup Parameters:

-s “MSSQLSERVER”

2018-09-12 14:31:22.25 Server SQL Server detected 1 sockets with 4 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.

2018-09-12 14:31:22.25 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2018-09-12 14:31:22.25 Server Detected 4008 MB of RAM. This is an informational message; no user action is required.

2018-09-12 14:31:22.25 Server Using conventional memory in the memory manager.

2018-09-12 14:31:22.29 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2018-09-12 14:31:22.37 Server Buffer pool extension is already disabled. No action is necessary.

2018-09-12 14:31:22.46 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.

2018-09-12 14:31:22.46 Server Implied authentication manager initialization failed. Implied authentication will be disabled.

2018-09-12 14:31:22.49 Server The maximum number of dedicated administrator connections for this instance is ‘1’

2018-09-12 14:31:22.49 Server This instance of SQL Server last reported using a process ID of 7204 at 9/12/2018 2:29:44 PM (local) 9/12/2018 1:29:44 PM (UTC). This is an informational message only; no user action is required.

2018-09-12 14:31:22.49 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.

2018-09-12 14:31:22.50 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-09-12 14:31:22.52 Server In-Memory OLTP initialized on lowend machine.

2018-09-12 14:31:22.56 Server Database Instant File Initialization: enabled. 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.

2018-09-12 14:31:22.56 Server Query Store settings initialized with enabled = 1,

2018-09-12 14:31:22.57 Server Software Usage Metrics is disabled.

2018-09-12 14:31:22.58 spid6s Starting up database ‘master’.

2018-09-12 14:31:22.61 Server CLR version v4.0.30319 loaded.

2018-09-12 14:31:22.74 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2018-09-12 14:31:22.74 spid6s Error: 9003, Severity: 20, State: 1.

2018-09-12 14:31:22.74 spid6s The log scan number (6640:144:1) passed to log scan in database ‘master’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

2018-09-12 14:31:22.74 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

2018-09-12 14:31:22.74 spid6s SQL Server shutdown has been initiated

This is the entire error log.

7

I understand that your master database is corrupt. So if you have Management Studio please backup your SambaPOS database if you connect.
If you cant please copy your files in ProgramFiles (mdf/ldf both) and reinstall sql server. This is the fastest soluiton

4 Likes