Windows server 2012 ошибка esent 906 быстродействие

Вопрос

svchost (928) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation.
See help link for complete details of possible causes.
Previous cache residency state: 4608% (100 out of ? buffers) (0 seconds ago)
Current cache residency state: 0% (4611 out of %10 buffers)
Current cache size vs. target: %11% (%12 MBs)
Physical Memory / RAM size: %13 MBs

Is this the cause of my slow performance server?

Ответы

Thanks for your post.

Before we go further, would you please describe your environment briefly? Do you have Exchange Server installed?

If yes, Please run the EXBPA in the Toolbox to do a Health Check.

Please also use Task Manager, review any running processes for unusually high memory consumption.

Below information comes from TechNet article, for your reference:

Determine whether enough memory is installed on the server. Add more memory if it is required.

Verify that the system page file is set correctly. The page file size minimum and maximum must be set to the amount of physical RAM plus 10 MB.

A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation

Windows server 2012 ошибка esent 906 быстродействие

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

All replies

What other roles on the DC? Sounds like memory exhaustion.

Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

File and Storage

32% used physical memory

You might be able to capture the event with process monitor.

Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

You could analyze memory issue by following Dave mentioned.

>> however the server still dies/hangs for a little while and it is when I receive the 906 errors.

For this event ID, please check link below to understand it:

Windows server 2012 ошибка esent 906 быстродействие

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

All replies

What other roles on the DC? Sounds like memory exhaustion.

Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

File and Storage

32% used physical memory

You might be able to capture the event with process monitor.

Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

You could analyze memory issue by following Dave mentioned.

>> however the server still dies/hangs for a little while and it is when I receive the 906 errors.

For this event ID, please check link below to understand it:

ESENT EventID: 906 svchost (1036) A significant portion of the database buffer cache has been written out to the system paging file.

I keep seeing this error message on two 100% identical (same hardware ProLiant DL380p G8, 8 GB RAM on each, same 2012 R2 o/s, same updates) servers that are currently
doing nothing and have nothing else installed in terms of roles and
features except file server. No Exchange, no DC, etc.
Both are physical servers (NO virtualization running on them) on the same network in the same AD domain as all other servers that do not show this error
They both have Shadow Copies enabled and configured for previous versions of files/folders,

Source: ESENT, Type: Warning, EventID: 906
svchost (1036) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation.
Resident cache has fallen by 4749 buffers (or 97) in the last 1 seconds.
Current Total Percent Resident: 2 (111 of 4860 buffers)

always followed by ESENT EventID 912
svchost (1036) A portion of the database buffer cache has been restored from the system paging file and is now resident again in memory. Prior to this, a portion of the database buffer cache had been written out to the system paging file resulting in performance degradation.
Resident cache has restored by -1 buffers (or -100) in the last 589 seconds.
Current Total Percent Resident: 0 (0 of 9 buffers)

and on one server preceeded by these almost always

ESENT 102
msiexec (4124) Instance: The database engine (6.02.9200.0000) is starting a new instance (0).

ESENT 105
msiexec (4124) Instance: The database engine started a new instance (0). (Time=0 seconds)

ESENT 326
msiexec (4124) Instance: The database engine attached a database (1, C:\ProgramData\Microsoft\W indows\App Repository \PackageRe pository.e db). (Time=0 seconds)

ESENT 327
msiexec (4124) Instance: The database engine detached a database (1, C:\ProgramData\Microsoft\W indows\App Repository \PackageRe pository.e db). (Time=0 seconds)

ESENT 103
msiexec (4124) Instance: The database engine stopped the instance (0).
Dirty Shutdown: 0

I have read somewhere that it might refer to windows updates being available and
that it is related to it somehow.
Both servers issue this error (application log) at various times every couple
of days, altough one of them does it a bit more often.

ANyone have any idea what this is? System logs on either server show no errors

Windows server 2012 ошибка esent 906 быстродействие

Hi. Everything passed in the DCDIAG log and I will post it when I find a good site to share it.

The other commands have limited info.

C:\>Repadmin /replsum /errorsonly

Source DSA largest delta fails/total %% error
svr-dc1 09m:41s 0 / 5 0
vm-dc1 03m:51s 0 / 5 0

Destination DSA largest delta fails/total %% error
svr-dc1 03m:51s 0 / 5 0
vm-dc1 09m:41s 0 / 5 0

Repadmin: running command /SHOWREPL against full DC vm-dc1.company.local

Default-First-Site-Name\vm-dc1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
DSA invocationID: aa4ce7d2-41ef-4bdd-abcd-bd696645822a

DC=company,DC=local
Default-First-Site-Name\svr-dc1 via RPC
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
Last attempt @ 2015-11-10 09:59:03 was successful.
CN=Configuration,DC=company,DC=local
Default-First-Site-Name\svr-dc1 via RPC
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
Last attempt @ 2015-11-10 09:49:07 was successful.
CN=Schema,CN=Configuration,DC=company,DC=local
Default-First-Site-Name\svr-dc1 via RPC
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
Last attempt @ 2015-11-10 09:49:07 was successful.
DC=DomainDnsZones,DC=company,DC=local
Default-First-Site-Name\svr-dc1 via RPC
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
Last attempt @ 2015-11-10 09:56:18 was successful.
DC=ForestDnsZones,DC=company,DC=local
Default-First-Site-Name\svr-dc1 via RPC
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
Last attempt @ 2015-11-10 09:49:07 was successful.

Repadmin: running command /SHOWREPL against full DC svr-dc1.company.local

Default-First-Site-Name\svr-dc1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: fb356743-aaf4-44de-8cc2-79fb41bce5f8
DSA invocationID: 7994b09d-7882-4cba-b00e-205b649015c2

DC=company,DC=local
Default-First-Site-Name\vm-dc1 via RPC
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
Last attempt @ 2015-11-10 09:58:58 was successful.
CN=Configuration,DC=company,DC=local
Default-First-Site-Name\vm-dc1 via RPC
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
Last attempt @ 2015-11-10 09:54:57 was successful.
CN=Schema,CN=Configuration,DC=company,DC=local
Default-First-Site-Name\vm-dc1 via RPC
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
Last attempt @ 2015-11-10 09:54:57 was successful.
DC=DomainDnsZones,DC=company,DC=local
Default-First-Site-Name\vm-dc1 via RPC
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
Last attempt @ 2015-11-10 09:56:33 was successful.
DC=ForestDnsZones,DC=company,DC=local
Default-First-Site-Name\vm-dc1 via RPC
DSA object GUID: 2329e1cf-ee8a-4113-acc4-47f6ded37116
Last attempt @ 2015-11-10 09:54:57 was successful.

The current domain functional level is not at least Windows Server 2008.
DFSRMig is only supported on at least Windows Server 2008 level domains.