Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ESEUTIL bug with Exchange 2010 RC1

4 views
Skip to first unread message

Plummer@discussions.microsoft.com Alan Plummer

unread,
Sep 23, 2009, 7:07:01 AM9/23/09
to
If you have a Public Folder database on Exchange 2010 RC1 and use ESEUTIL /d
on the EDB, rather than shrink the database it makes it bigger everytime you
run it.

Is this a bug?

Oliver Moazzezi [MVP]

unread,
Sep 23, 2009, 7:57:56 AM9/23/09
to
Just trying this in my lab now...

Oliver


Alan Plummer

unread,
Sep 23, 2009, 8:49:02 AM9/23/09
to
I hope you get the same results as me.....

Oliver Moazzezi [MVP]

unread,
Sep 24, 2009, 7:14:06 AM9/24/09
to
Alan it is not doing it for me.

I've passed on your information though.

thanks,

Oliver

Alan Plummer

unread,
Sep 24, 2009, 10:29:02 AM9/24/09
to
Thanks for trying it Oliver.

FYI, it was a brand new PF database created in 2010. I then rammed in over
1Gb of folders and emails, then tried to compact it.

It increases by around 200Mb everytime I run ESEUTIL /D

Regards

Alan

Alan Plummer

unread,
Oct 28, 2009, 6:21:02 AM10/28/09
to
Oliver,

I have done some more research on this and it's definately a bug.

I've done a clean install of Exchange Server 2010.

I create a new Public Folder Database. The only change I do is allow OAB to
be distributed via this Public Folder.

Stop the Information Store Service.

Run ESEUTIL /d "x:\......\Public Folder Database.edb"

Everytime you run this, even on a NEW database it increases in size by about
10% rather than shrinking.

Regards

Alan

Alan Plummer

unread,
Oct 28, 2009, 6:33:01 AM10/28/09
to
After posting this, I forgot to mention you might have to run ESEUTIL /d more
than once to notice the increase in the file size.

If you run it over and over again without adding anything to PF it gets
bigger and bigger.

I would open a Support Contract with Microsoft but I have to wait till it's
RTM'd

Alan Plummer

unread,
Nov 16, 2009, 10:04:08 AM11/16/09
to
I opened up a Microsoft Support Incident.

This has been CONFIRMED as a bug by Microsoft in Exchange 2010 RTM.

They reckon it'll be fixed in a couple of months.

0 new messages