Windows system32 logfiles sum current mdb

← Вернуться в раздел «Microsoft Windows»

Автор: ipmanyak
Дата сообщения: 22.04.2015 11:14

Страницы: 1

Предыдущая тема: 0x000007b при установке Windows XP SP3 With ACHI

---

Форум Ru-Board.club — поднят 15-09-2016 числа. Цель — сохранить наследие старого Ru-Board, истории становления российского интернета. Сделано для людей.

Авг 18, 2016 23:01

Hi.

We have a SQL Server cluster A/B/C

A and B has 4 SQL Server 2014 instances, 1 SQL Server 2012 instance.

C has 2 SQL Server 2014 instances(a sync replica)

Everything runs well until I installed new SQL Server 2016 instance, it was fine at the beginning, but Server B crashed on that night.

The second day I disabled SQL Server 2016, and rebooted the B node for 4 times, and it crashed 4 times when available memory drops to roughly 40GB, as long as I limit the total max sql server memory setting to total ram — 50GB, it runs well.

Also we found the error «

Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 410**.

» in SQL Server log which is quite similar to this case:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/05d4f0b0-c0a2-45bb-b9cd-5a24b746c92c/failed-to-update-replica-status-within-the-local-windows-server-failover-clustering-wsfc-due-to?forum=sqldisasterrecovery

So we think it might be a ram problem, we replaced the ram, however it does not help, still crashes when avail memory drops to 40GB.

Does anyone has the similar issue before

The symptom  is when the available memory drops to 40GB, all connection to that server dropped, and can only login from DRAC console:

Event Log:

1.

svchost (3048) An attempt to write to the file «C:Windowssystem32LogFilesSumSvc.log» at offset 1773568 (0x00000000001b1000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad): «Insufficient quota
to complete the requested service. «.  The write operation will fail with error -1011 (0xfffffc0d).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

2.

svchost (3048) Unable to write to section 2 while flushing logfile C:Windowssystem32LogFilesSumSvc.log. Error -1011 (0xfffffc0d).

3.

svchost (3048) The logfile sequence in «C:Windowssystem32LogFilesSum» has been halted due to a fatal error.  No further updates are possible for the databases that use this logfile sequence.  Please correct the problem and restart
or restore from backup.

4.

svchost (3048) Unable to rollback operation #28998049 on database C:Windowssystem32LogFilesSumCurrent.mdb. Error: -510. All future database updates will be rejected.

SQL Server starts to crash.

5.

The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.

6.

The local availability replica of availability group ‘SQL**AG’ is in a failed state.  The replica failed to read or update the persisted configuration data (SQL Server error: 41029).  To recover from this failure, either restart the local Windows
Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.

In SQL Server log:

1.

AlwaysOn: The local replica of availability group ‘**AG’ is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.

2.

The availability group ‘**AG’ is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required.

3.

The state of the local availability replica in availability group ‘**AG’ has changed from ‘PRIMARY_NORMAL’ to ‘RESOLVING_NORMAL’.  The state changed because the availability group is going offline.  The replica is going offline because the associated
availability group has been deleted, or the user has taken the associated availability group offline in Windows Server Failover Clustering (WSFC) management console, or the availability group is failing over to another SQL Server instance.  For more information,
see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.

4.

DbMgrPartnerCommitPolicy::SetSyncState: 00000014ACDBD360:4

5.

AlwaysOn Availability Groups connection with secondary database terminated for primary database ‘db***’ on the availability replica ‘**Server-1CINSTANCE2’ with Replica ID: {52bbb123-6d62-4e35-b364-371c2c79fc74}. This is an informational message only. No
user action is required.

…

All AGs’ role change to «Resolving» on that box.

As «Insufficient quota to complete the requested service» is the first error appear in the log when the issue occurs, it makes sense if a stick of ram failed when available memory drops to 40GB, but we have replaced the ram, does anyone has the
similar issue? can you please share your experience?

Thanks,

Albert

On every restart of a new Windows Server 2012 R2 Essentials machine, I get several instances of the following errors in the Application event log:

Log Name:      Application
Source:        ESENT
Event ID:      490
Level:         Error
Description:
svchost (3536) An attempt to open the file «C:Windowssystem32LogFilesSumApi.chk» for read / write access failed with system error 5 (0x00000005): «Access is denied. «.  The open file operation will fail with error -1032 (0xfffffbf8).

Log Name:      Application
Source:        ESENT
Event ID:      490
Level:         Error
Description:
svchost (3536) An attempt to open the file «C:Windowssystem32LogFilesSumSystemIdentity.mdb» for read / write access failed with system error 5 (0x00000005): «Access is denied. «.  The open file operation will fail with error -1032 (0xfffffbf8).

MSKB 2811566 and this Connect bug discuss SQL Server causing this issue. But the error says it’s coming from svchost (3536). Using Sysinternals Process Explorer, I learned that this PID is actually hosting the Remote Desktop Gateway service. I confirmed this by stopping and starting that service; the errors repeated.

Workaround

The Remote Desktop Gateway service runs using the Network Service account. Once I gave that account Modify permissions on

C:Windowssystem32LogFilesSum

the ESENT 490 errors stopped. Instead, I get these messages when starting the Remote Desktop Gateway service:

Log Name:      Application
Source:        ESENT
Event ID:      326
Level:         Information
Description:
svchost (7704) The database engine attached a database (1, C:Windowssystem32LogFilesSumSystemIdentity.mdb). (Time=0 seconds)

Log Name:      Application
Source:        ESENT
Event ID:      327
Level:         Information
Description:
svchost (7704) The database engine detached a database (1, C:Windowssystem32LogFilesSumSystemIdentity.mdb). (Time=0 seconds)