DatabaseDriveSpaceTrigger (Network Steve Forum)

DatabaseDriveSpaceTrigger

Ever since upgrading to Exchange Server 2013 CU2 I now constantly get these in the Event Viewer...

The performance counter '\\EXCHANGE\LogicalDisk(HarddiskVolume1)\Free Megabytes' sustained a value of '108.00', for the '15' minute(s) interval starting at '16/07/2013 12:07:00'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:harddiskvolume1

Anyone know how to fix this?

July 16th, 2013 12:32pm

Are you low on disk space on that drive?

Free Windows Admin Tool Kit Click here and download it now

July 16th, 2013 2:53pm

How many users in this database

If there are not a lot of users, have a try to recreate outlook profiles of all these users.

Cheers

If you have any feedback on our support, please click here

July 17th, 2013 6:57am

Are you low on disk space on that drive?

Nope. 80Gb free.

How many users in this database

Around 50 mailboxes. Not really got the time to recreate outlook profiles.

As I said, this has ONLY JUST started happening after CU2.

Any other ideas?

Free Windows Admin Tool Kit Click here and download it now

July 17th, 2013 8:11am

This is also occurring on our server since applying CU2.

Proposed as answer by MyKEcz Saturday, July 20, 2013 12:30 PM
Unproposed as answer by MyKEcz Saturday, July 20, 2013 12:30 PM

July 17th, 2013 2:52pm

I also get this with EX2013 and CU. The disk its reffering to it "System Reserve". Anybody now how to disable this trigger?

Free Windows Admin Tool Kit Click here and download it now

July 19th, 2013 9:39am

I have the same issue and i have more than 80Gb free on the disk...

July 20th, 2013 11:17pm

I have the same issue on system reserve and system drive .. my db is on another drive that has plenty of room and no errors. How do you set which drives it looks at?

Free Windows Admin Tool Kit Click here and download it now

July 25th, 2013 1:16am

I'm also getting this on drives that do not hold databases.

One volume being reported is my logs drive which is 64GB and I have over 50GB free.

The performance counter '\\SERVERNAME\LogicalDisk(E:)\Free Megabytes' sustained a value of '53,776.00', for the '15' minute(s) interval starting at '26/07/2013 1:35:00 AM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:e:

I too would also like to know how to configure which drives are being checked as DB drives.

July 26th, 2013 2:00am

Add me to the list of admins experiencing this issue. As soon as I upgraded to CU2, I started getting these errors every 15 minutes. Plenty of free space remains on the drives listed. I haven't come across a fix yet, so I'm hoping this tread eventually leads to one.

Free Windows Admin Tool Kit Click here and download it now

July 26th, 2013 7:37pm

Same error here, 2013 + CU2.

Proposed as answer by Orbdot Wednesday, July 31, 2013 2:19 AM
Unproposed as answer by Orbdot Wednesday, July 31, 2013 2:19 AM

July 28th, 2013 1:47pm

I too am having this issue with 3 users on a test box with CU 2 and it seems
to be causing a back pressure event, stopping mail flow. I was able to resolve
it by doing the following:

Disable the trigger in the Microsoft.Exchange.Diagnostics.Service.exe -

You can find it in the following location:

C:\Program Files\Microsoft\ExchangeServer\V15\Bin\Microsoft.Exchange.Diagnostics.Service.exe (it's a config file)

Change "xchangeJobs.Triggers.DatabaseDriveSpaceTrigger" from "True" to
"False".

Mail seems to be flowing again.

Hope this helps!

Proposed as answer by Orbdot Wednesday, July 31, 2013 2:41 AM
Marked as answer by Zi FengMicrosoft contingent staff, Moderator Wednesday, July 31, 2013 4:19 AM

Free Windows Admin Tool Kit Click here and download it now

July 31st, 2013 2:38am

Ditto. New to CU2 on server with like 10 accounts. Events are pouring in with this trigger from all drives (volumes, really) in the machine, including the 350 MB System Reserved drive (which is of course nearly empty) and my 8GB "just for the page file" drive.

PS - The [MS] in my user name doesn't mean I work for Microsoft and therefore know anything about Exchange. It means I work for Microsoft and ought to know stuff about Exchange but don't and hence acquired the somewhat masochistic hobby of running an Exchange server at home.

Edited by Peter Engrav [MS] Sunday, August 04, 2013 3:03 AM

August 4th, 2013 3:00am

same problem here..
Doesn't disabling this option disable internal DB checking too?

Free Windows Admin Tool Kit Click here and download it now

August 5th, 2013 12:41pm

Changing this seems to stop the error regarding the performance counter '\\EXCHANGE\LogicalDisk(HarddiskVolume1)\Free Megabytes' sustained a value of '108.00', for the '15' minute(s)

But I still get Ping of mdb '27294b65-79bb-4eaa-b90c-944ae9e016c8' timed out after '00:00:00' minutes. Last successful ping was at '8/21/2013 8:02:40 AM' UTC.

And users seem to still see the problem with client trying to update or send emails.

I have tried to create a new DB and move one user to this DB, but the same ping error is displayed for both DB's and the user still have problems with connection.

I am running 2013 Cu2 on server2012 and having no problems with space etc.

Where are Microsoft in all this, can they be contacted in another way?

Edited by Jysk IT Partner Wednesday, August 21, 2013 8:20 AM

August 21st, 2013 8:17am

Hello

I'm experiencing the same. I could disable the check, but what are the implications of doing this ? It's not very clear.

Free Windows Admin Tool Kit Click here and download it now

August 22nd, 2013 9:55am

Did anyone resolve this we have a live exchange with customers running and ever since updating to CU2 we've had these errors. Over the last 24 hours we've also been having to restart the transport service before email comes in.

I'm also getting the error

MSExchange Workload Management cannot be found

Event ID 5

September 25th, 2013 1:00am

Hi,

I got the same error here, 2013 + CU2

Free Windows Admin Tool Kit Click here and download it now

September 26th, 2013 7:09am

Same here, both performance counter and mdb ping errors with users getting disconnected.

September 26th, 2013 7:44am

Hey,

Any updates to his ?

I just freshly installed a new Exchange 2013 CU2 Server and got both errors - 1006 (Drive Space) / 6002 (mdb ping)

Free Windows Admin Tool Kit Click here and download it now

November 12th, 2013 12:07pm

Seeing this in my Exchange 2013 CU2 server as well.

For what it's worth, Tony Redmond posted about this issue in his blog here. It does a good job of summarizing what's going on behind the scenes and how to sidestep the issue, as well as the warnings behind doing so.

He also points out that with CU3 now available, any changes made to circumvent the checks might be overwritten...on the other hand, CU3 might actually fix the problem with the checker.

-Bob

December 6th, 2013 5:33pm

Nope, CU3 does not address the issue. Have a fresh install of EX 2013 with CU3 - the same exact issue. In our case the event is complaining about the free space on the System Reserved partition, which is 70MB in our case and is totally fine. I guess, Microsoft is better to fix it as we definitely don't need to monitor free space on the System Reserved partition and create errors in the Event Log.

SP1 is due soon, hopefully it will address the issue.

Edited by Flegance Friday, February 07, 2014 12:38 AM

Free Windows Admin Tool Kit Click here and download it now

February 7th, 2014 12:23am

It does not. Installed SP1 yesterday:

Error 27-2-2014 21:13:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 21:13:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 21:13:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:58:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:58:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:58:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:43:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:43:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:43:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:28:52 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:28:52 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:28:52 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:13:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:13:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 20:13:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:58:49 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:58:49 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:58:49 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:43:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:43:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:43:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:28:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:28:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:28:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:13:42 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:13:42 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 19:13:42 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:58:40 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:58:40 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:58:40 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:43:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:43:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:43:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:28:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:28:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:28:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:13:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:13:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 18:13:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:58:35 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:58:35 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:58:35 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:43:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:43:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:43:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:28:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:28:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:28:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:13:30 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:13:30 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 17:13:30 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:53:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:53:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:53:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:38:28 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:38:28 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:38:28 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:23:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:23:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:23:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:08:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:08:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 16:08:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:53:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:53:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:53:23 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:38:20 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:38:20 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:38:20 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:23:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:23:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:23:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:08:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:08:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 15:08:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:53:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:53:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:53:17 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:38:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:38:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:38:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:23:14 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:23:14 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:23:14 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:08:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:08:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 14:08:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:53:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:53:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:53:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:43:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:43:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:43:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:28:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:28:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:28:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:13:05 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:13:05 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 13:13:05 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:58:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:58:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:58:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:43:03 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:43:03 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:43:03 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:27:59 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:27:59 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:27:59 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:12:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:12:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 12:12:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:57:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:57:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:57:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:42:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:42:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:42:55 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:27:54 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:27:54 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:27:54 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:12:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:12:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 11:12:53 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:57:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:57:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:57:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:42:48 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:42:48 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:42:48 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:27:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:27:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:27:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:12:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:12:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 10:12:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:57:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:57:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:57:44 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:42:43 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:42:43 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:42:43 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:27:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:27:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:27:39 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:12:37 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:12:37 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 09:12:37 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:57:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:57:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:57:36 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:42:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:42:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:42:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:27:32 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:27:32 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:27:32 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:12:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:12:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 08:12:29 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:57:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:57:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:57:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:42:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:42:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:42:27 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:27:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:27:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:27:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:12:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:12:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 07:12:24 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:57:21 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:57:21 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:57:21 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:42:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:42:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:42:19 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:27:18 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:27:18 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:27:18 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:12:16 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:12:16 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 06:12:16 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:57:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:57:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:57:15 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:42:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:42:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:42:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:27:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:27:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:27:13 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:12:10 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:12:10 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 05:12:10 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:57:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:57:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:57:09 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:42:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:42:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:42:07 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:27:06 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:27:06 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:27:06 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:12:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:12:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 04:12:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:57:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:57:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:57:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:42:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:42:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:42:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:27:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:27:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:27:01 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:11:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:11:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 03:11:58 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:56:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:56:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:56:12 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:41:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:41:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:41:04 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:26:00 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:26:00 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:26:00 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:10:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:10:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 02:10:56 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:55:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:55:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:55:51 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:40:45 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:40:45 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:40:45 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:25:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:25:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:25:46 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:10:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:10:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 01:10:50 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:55:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:55:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:55:38 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:40:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:40:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:40:33 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:25:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:25:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:25:34 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:10:32 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:10:32 MSExchangeDiagnostics 1006 Triggers
Error 27-2-2014 00:10:32 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:55:30 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:55:30 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:55:30 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:40:28 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:40:28 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:40:28 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:25:27 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:25:27 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:25:27 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:10:23 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:10:23 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 23:10:23 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:55:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:55:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:55:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:40:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:40:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:40:21 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:25:18 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:25:18 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:25:18 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:10:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:10:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 22:10:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:55:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:55:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:55:16 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:40:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:40:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:40:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:25:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:25:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:25:12 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:10:10 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:10:10 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 21:10:10 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:55:08 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:55:08 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:55:08 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:40:07 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:40:07 MSExchangeDiagnostics 1006 Triggers
Error 26-2-2014 20:40:07 MSExchangeDiagnostics 1006 Tr

February 27th, 2014 8:31pm

Same here :(

Free Windows Admin Tool Kit Click here and download it now

March 11th, 2014 1:01pm

Same problem. Running Exchange 2013 SP1 on Windows 2012.

What is the solution to this?

March 26th, 2014 2:19am

Same problem here.

Exchange 2013 SP1.

Any Microsoft guy here?

Free Windows Admin Tool Kit Click here and download it now

April 20th, 2014 2:03pm

The same problem.

The performance counter '\\SERVERNAME\LogicalDisk(HarddiskVolume1)\Free Megabytes' sustained a value of '89,00', for the '15' minute(s) interval starting at '16.05.2014 5:46:00'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:harddiskvolume1

May 16th, 2014 6:13am

I've seen it in Exchange 2013 installations as well. My understanding is that it's a bug and can be ignored.

Free Windows Admin Tool Kit Click here and download it now

May 16th, 2014 4:33pm

Same problem with Exchange 2013 CU5.

Any solution?

June 29th, 2014 7:48pm

Have also gone to CU5 and still getting these errors, the performance counter error and the ping error.

Is anybody (at MS) listening?

Free Windows Admin Tool Kit Click here and download it now

July 1st, 2014 3:07pm

According to http://video.ch9.ms/sessions/mec/2014/ARC303_Schnoll.pptx (page 61) you can create a registry key to set your own tresholds:

HKLM\Software\Microsoft\ExchangeServer\v15\Replay\Parameters\SpaceMonitorLowSpaceThresholdInMB
REG_DWORD 186a0 (100000)
In absence of registry value, default is 200 GB
Applies to volumes containing databases or log files

July 18th, 2014 10:41am

Tried this registry key, but it does not make any difference.

Free Windows Admin Tool Kit Click here and download it now

July 19th, 2014 10:33am

Is there real fix for this yet? I am seeing the same thing on a new exchange 2013 server build # 847.32.

April 20th, 2015 10:45am

This topic is archived. No further replies will be accepted.