(**UPDATE, CU6 Fixes this bug**)
Since upgrading to CU1, CU2 and now CU2v2 for Exchange 2013, event ID 1006 keeps getting logged with performance counter errors. My server has 600GB free space yet it complains of this. Seems like yet another bug in Exchange 2013.
I turned off these notifications, you can do so at your own will if you want. This is the error logged:
The performance counter ‘\SERVERLogicalDisk(HarddiskVolume1)Free Megabytes’ sustained a value of ‘45,297.00’, for the ’15’ minute(s) interval starting at ‘7/21/2013 5:41:00 AM’. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:harddiskvolume4
Here is the location of the config file where you can set the value from “True” to “False”
Disable the trigger in the Microsoft.Exchange.Diagnostics.Service.exe
Change “ExchangeJobs.Triggers.DatabaseDriveSpaceTrigger” from “True” to “False”.
After making the change I restarted the MS Exchange Diagnostics Service and no more errors logged. This should be fixed in CU3
Hope it helps.
10 thought on “Exchange 2013 MSDiagnostics Event Error 1006”
[…] From: http://edwardvbs.wordpress.com/2013/08/22/207/ […]
Couple of corrections.
The file is: “Microsoft.Exchange.Diagnostics.Service.exe.config”
Value is ExchangeJobs.Triggers.DatabaseDriveSpaceTrigger (missing the E)
[…] From <http://edwardvbs.wordpress.com/2013/08/22/207/> […]
Thanks for the tip. I have 3TB free and keep getting the message, what a pain.
just applied CU3 and the issue is not fixed. I’m still getting these errors.
Correct, i added in a message on the top of the post regarding this.
Just did a fresh install Exchange 2013 SP1.
Same issue. Can’t move mailboxes. DAG not replicating.
Thanks for the tip.
Again, great post. I am actually on a fresh SP1 install and this post did resolve this event. However, what are the downsides of changing this to false? Does this mean now if my database actually gets filled I will not be alerted?
setting the value to false stops the alerts in the event log that there is an issue. the problem has persisted from RTM to SP1 now. I have had a chat to the MS team and presented my findings, hopefully in the future it will be rectified or they will shed some more light on this.
The error is probably not about your main hard drive. Exchange is looking at all drive volumes, which includes the little 100MB boot volume that Windows creates. If you look, you will most likely see the free space on that volume, not your main volume.
Comments are closed.