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\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds)

ESENT 327
msiexec (4124) Instance: The database engine detached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (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
Laszlo DenesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Laszlo DenesAuthor Commented:
Still no feedback and this is the first time that I have gotten nothing on experts exchange :-(
0
MaheshArchitectCommented:
Normally this event is logged on exchange servers
Now in your case it's logged because of Windows updates
Can you check if there is memory leakage on physical server?  you can patch / update server firmware
Also check how much page file you kept on server, it should be system managed
How much is memory and page file utilization? Check from perfmon
If your file server data in out is frequent and heavy use (transacting  big files), it might be possible that server is running out of memory and then writing into page file, in that case increase server memory
0
Laszlo DenesAuthor Commented:
Thanks for the insight. Really appreciate it.
Some information.
Attached a quick screen grab from both servers re. memory performance.
Both servers will be file servers eventually. Right now neither one is dong anything except running.
Both have 8 GB of RAM and the page file is set to automatic.
I did do all the available updates and the error has not come up in about 4 days now.
I struggle with the thought that both of these servers (we have another 3 same hardware -  in production doing other things - without that error) have identical memory leaks or such.
Paging file usage and memory available through perfmon was not high.
ScreenShot137.bmp
ScreenShot136.bmp
0
What were the top attacks of Q1 2018?

The Threat Lab team analyzes data from WatchGuard’s Firebox Feed, internal and partner threat intelligence, and a research honeynet, to provide insightful analysis about the top threats on the Internet. Check out our Q1 2018 report for smart, practical security advice today!

MaheshArchitectCommented:
In that case update server firmware to latest *stable* build and then check if it make any difference
If you logged call with microsoft, they will 1st try to patch with Windows latest patches and then run standard internal diagnostics tools and if did not help, then they will ask you to reinstall os
0
Laszlo DenesAuthor Commented:
I am still monitoring (before I patch the firmware) to see if the error comes back after I did all the MS updates. SO far so good. Will keep an eye on it for a few more days
0
Laszlo DenesAuthor Commented:
I updated the firmware (sorry was off due to leg injury) and it made no difference. Still getting the error
0
Laszlo DenesAuthor Commented:
I identified additional messages around ESENT (not errors just informational), specifically (in this sequence and quite often right after the 906 error) 912, 102,105,326,327 and 103 and they all relate to C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb
In Windows desktop system that is the Windows Store. What purpose does C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb serve in Windows server 2012 R2???
0
Laszlo DenesAuthor Commented:
No idea what that was (ESENT error) and ended up rebuilding both servers from ground up... hope it does not come back...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Laszlo DenesAuthor Commented:
Only rebuilds made it go away :-(
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.