пропозиції роботи
Temat: Problem z uruchomieniem servera SQL
W wyniku braku prądu i awarii mam problem z uruchomieniem servera SQL i przez to wfmagaLog błędu poniżej. Proszę o pomoc w rozwiązaniu problemu.
2019-11-08 16:47:38.26 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)
Apr 2 2010 15:53:02
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 5.1 <X86> (Build 2600: Dodatek Service Pack 3)
2019-11-08 16:47:38.26 Server Error: 17054, Severity: 16, State: 1.
2019-11-08 16:47:38.26 Server The current event was not reported to the Windows Events log. Operating system error = 1502(Plik dziennika zdarzeń jest zapełniony.). You may need to clear the Windows Events log if it is full.
2019-11-08 16:47:38.26 Server (c) Microsoft Corporation.
2019-11-08 16:47:38.26 Server All rights reserved.
2019-11-08 16:47:38.26 Server Server process ID is 5488.
2019-11-08 16:47:38.26 Server Authentication mode is MIXED.
2019-11-08 16:47:38.26 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2019-11-08 16:47:38.27 Server This instance of SQL Server last reported using a process ID of 4968 at 2019-11-08 16:36:58 (local) 2019-11-08 15:36:58 (UTC). This is an informational message only; no user action is required.
2019-11-08 16:47:38.27 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-11-08 16:47:38.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-11-08 16:47:38.28 Server Detected 2 CPUs. This is an informational message; no user action is required.
2019-11-08 16:47:38.79 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.
2019-11-08 16:47:38.87 Server Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-11-08 16:47:38.90 spid6s Starting up database 'master'.
2019-11-08 16:47:39.05 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-11-08 16:47:39.08 spid6s SQL Trace ID 1 was started by login "sa".
2019-11-08 16:47:39.08 spid6s Starting up database 'mssqlsystemresource'.
2019-11-08 16:47:39.12 spid6s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2019-11-08 16:47:39.50 spid6s Server name is 'ADMIN-06CBDE5A1'. This is an informational message only. No user action is required.
2019-11-08 16:47:39.51 spid6s Informational: No full-text supported languages found.
2019-11-08 16:47:39.51 spid10s Starting up database 'model'.
2019-11-08 16:47:39.51 spid6s Starting up database 'msdb'.
2019-11-08 16:47:40.07 Server A self-generated certificate was successfully loaded for encryption.
2019-11-08 16:47:40.11 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2019-11-08 16:47:40.11 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2019-11-08 16:47:40.11 Server 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.
2019-11-08 16:47:40.24 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2019-11-08 16:47:40.24 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-11-08 16:47:40.24 spid10s Error: 9003, Severity: 20, State: 1.
2019-11-08 16:47:40.24 spid10s The log scan number (69:144:1) passed to log scan in database 'model' 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.
2019-11-08 16:47:40.24 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
