Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, February 12, 2014 3:18 AM
I have my exchange running on a virtual machine. All roles are running off this vm. After I've installed CU3 and taken it from 10 GB memory to 12 GB and gave it 8 vCPU from 4vCPU, the amount of memory it's paging seems to have gone from around 30% to 60%. The page file size is the memory size + 10 MB. There's about 120 users and 5 databases
I'm also getting this error, which I never got before any upgrades:
Event 906, ESE
Information Store - Mailbox Database 0042403600 (8396) 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: 41% (7145 out of 17019 buffers) (11179 seconds ago)
Current cache residency state: 9% (1681 out of 17019 buffers)
and also this one
The description for Event ID 5 from source MSExchange Workload Management cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
MdbLatency(Global)
11/02/2014 11:17:54 p.m.
00:19:55.2364452
the message resource is present but the message is not found in the string/message table
All replies (4)
Wednesday, February 12, 2014 11:10 AM ✅Answered | 1 vote
Hi
I would increase your memory to at least 16GB or higher. the problem is once you run out it starts using harddrive space for paging and this will significantly slow down things.
I normally seperate my page file from the C:\ drive and put it on its own with enough memory.
Thursday, February 20, 2014 2:55 AM ✅Answered | 1 vote
Hi,
This issue related to the server performance side.
Found some resouce for your reference (even if the mismatched version of Exchange)
Resolution:
*Step 1: Confirmed that all servers within the DAG were consistently and properly configured, specifically network configuration and antivirus exclusions *
Step 2: Installed latest drivers, firmware, and recommended hotfixes
*Step 3: Added additional RAM in the servers (amount may vary on environment/need) *
Step 4: Reboot the server
More details in the following blog:
Exchange Databases Failover Due to Low Memory
Also providing a workaround for solving "Event ID 5" issue.
I SUGGEST MAKING A FULL BACK UP BEFORE PERFORMING FOLLOWING ACTION.
The description for Event ID 5 from source MSExchange Workload Management cannot be found.
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support
Wednesday, February 12, 2014 7:43 PM
I can move it up to 16 GB tonight and report back to see if this makes the events go away, though I find it strange this just started occurring post upgrades. I have the page file on C: but the actual Exchange instance is installed on D:
Wednesday, May 14, 2014 10:51 AM
Hi, i can't get the link for resolution of error 5
Can you help me?
Thanks