Obserwuj Odpowiedz nie mozna uruchomic serwisu sprawdz wpisy w pliku error log wf kaper


(kafar610) #1

Witam
Przy próbie odpalenia wf-kaper’a wyskakuje taki oto błąd “nie mozna uruchomic serwisu sprawdz wpisy w pliku error log”

plik errorlog

	2017-06-23 10:15:57.52 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64) 
Dec 28 2012 20:23:12 
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2017-06-23 10:15:57.52 Server      (c) Microsoft Corporation.
2017-06-23 10:15:57.52 Server      All rights reserved.
2017-06-23 10:15:57.52 Server      Server process ID is 6104.
2017-06-23 10:15:57.52 Server      System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'B85M-D3H'.
2017-06-23 10:15:57.52 Server      Authentication mode is MIXED.
2017-06-23 10:15:57.52 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2017-06-23 10:15:57.53 Server      The service account is 'WORKGROUP\TAX-HAVEN2$'. This is an informational message; no user action is required.
2017-06-23 10:15:57.53 Server      Registry startup parameters: 
	-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
	-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
	-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2017-06-23 10:15:57.53 Server      Command Line Startup Parameters:
	-s "MSSQLSERVER"
2017-06-23 10:15:57.65 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.
2017-06-23 10:15:57.65 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-06-23 10:15:57.65 Server      Detected 3992 MB of RAM. This is an informational message; no user action is required.
2017-06-23 10:15:57.65 Server      Using conventional memory in the memory manager.
2017-06-23 10:15:57.71 Server      This instance of SQL Server last reported using a process ID of 5336 at 2017-06-23 10:10:53 (local) 2017-06-23 08:10:53 (UTC). This is an informational message only; no user action is required.
2017-06-23 10:15:57.72 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.
2017-06-23 10:15:57.72 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.
2017-06-23 10:15:57.73 Server      Software Usage Metrics is disabled.
2017-06-23 10:15:57.73 spid7s      Starting up database 'master'.
2017-06-23 10:15:57.77 spid7s      Error: 9003, Severity: 20, State: 1.
2017-06-23 10:15:57.77 spid7s      The log scan number (465:128: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.
2017-06-23 10:15:57.77 spid7s      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.