January 2, 2018 at 3:10 am
Hi all,
I have come across this issue after resetting my Windows 10:
SQL Server detected a logical consistency-based I/O error: invalid encryption key. It occurred during a read of page (2:0) in database ID 1 at offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSSQLSERER\MSSSQL\DATA\mastlog.ldf'.
Before the reset, I was able to install SQL instances smoothly using the same setup. I have read somewhere that it could be hardware issues, so I tried to reformat my PC to (super) clean install SQL but the issue remains. I also cannot execute DBCC CHECKDB as I cannot start sql server.
I am pretty new to SQL Server. How can I fix this?
I am really grateful for any of your help . 😀
Here is the full error log:
2018-01-02 17:04:34.95 Server Server process ID is 6812.
2018-01-02 17:04:34.95 Server System Manufacturer: 'LENOVO', System Model: '20354'.
2018-01-02 17:04:34.95 Server Authentication mode is MIXED.
2018-01-02 17:04:34.95 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-02 17:04:34.95 Server The service account is 'WORKGROUP\WIN-FAN50FHH8UM$'. This is an informational message; no user action is required.
2018-01-02 17:04:34.95 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-02 17:04:34.95 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2018-01-02 17:04:35.17 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.
2018-01-02 17:04:35.17 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-02 17:04:35.17 Server Detected 8084 MB of RAM. This is an informational message; no user action is required.
2018-01-02 17:04:35.17 Server Using locked pages in the memory manager.
2018-01-02 17:04:35.26 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2018-01-02 17:04:35.29 Server Query Store settings initialized with enabled = 1,
2018-01-02 17:04:35.30 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-01-02 17:04:35.30 Server This instance of SQL Server last reported using a process ID of 12144 at 02/01/2018 5:04:13 PM (local) 02/01/2018 9:04:13 AM (UTC). This is an informational message only; no user action is required.
2018-01-02 17:04:35.30 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-01-02 17:04:35.31 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-01-02 17:04:35.33 Server Software Usage Metrics is disabled.
2018-01-02 17:04:35.33 spid8s Starting up database 'master'.
2018-01-02 17:04:35.41 Server CLR version v4.0.30319 loaded.
2018-01-02 17:04:35.50 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-01-02 17:04:36.90 spid8s Error: 824, Severity: 24, State: 2.
2018-01-02 17:04:36.90 spid8s SQL Server detected a logical consistency-based I/O error: invalid encryption key. It occurred during a read of page (2:0) in database ID 1 at offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
January 2, 2018 at 5:46 am
This was removed by the editor as SPAM
January 2, 2018 at 8:51 am
thank you subramaniam
However, I could not perform DBCC CHECKDB. I cannot start the sql server instance as the master database has issues
I tried to rebuild the master db following this , scenario 2 and 3 as I have no backup at all. But it still doesn't work.
January 2, 2018 at 8:55 am
iyarianecy10 - Tuesday, January 2, 2018 8:51 AMI tried to rebuild the master db following this , scenario 2 and 3 as I have no backup at all. But it still doesn't work.
What error do you receive?
Was the rebuild successful?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 2, 2018 at 6:06 pm
I'm not too sure if this is the right error log but this is from the summary.txt in C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2018-01-03 09:00:47
End time: 2018-01-03 09:01:25
Requested action: RebuildDatabase
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: DESKTOP-MAFM0T7
Machine processor count: 4
OS version: Windows 8
OS service pack:
OS region: Philippines
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Database Engine Services 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER SQL Server Replication 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSAS12.MSSQLSERVER Analysis Services 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSRS12.MSSQLSERVER Reporting Services - Native 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Basic 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Complete 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Connectivity 1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 Integration Services 1033 Standard Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation edition:
User Input Settings:
ACTION: RebuildDatabase
CONFIGURATIONFILE:
ENU: false
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: MSSQLSERVER
QUIET: false
QUIETSIMPLE: false
SAPWD: *****
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS: Ariane
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20180103_090045\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Reporting Services - Native
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
January 3, 2018 at 4:24 am
start the instance in single user mode to check master database
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 5, 2018 at 7:37 am
Hi all, I'm sorry for the late response.
I have tried to start instance in single user mode (the -m in configuration manager startup parameters)
But it still yields the same issue
January 10, 2018 at 4:56 am
This was removed by the editor as SPAM
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply