Jet error -1811 on eseutil

SBS 2003 new install. Got error database hit 16GB and dismounted. Was able to get it remounted by deleteing some small users and am trying to run eseutil /d and get jet error -1811
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

make sure that permissions set on the bin directory on exchsrvr allow administrators full control.  Make sure that you have plenty of free space on the drive you plan to do the defrag on.  Also post the full command you are tyring.  for example eseutil /d c:\program files\exchsrvr\mdbdata\priv1.edb would need to be enclosed in double quotes like this because of spaces eseutil /d "c:\program files\exchsrvr\mdbdata\priv1.edb".

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
lindemannfoxAuthor Commented:
Thanks. I had the wrong syntax. I am trying the new command now...
lindemannfoxAuthor Commented:
I am running the defrg now but:

Database priv1.edb shows 16GB but if I look at the total of the 12 mailboxes we have there is only 5Gb or so used? How can I figure out what chewed up all the space for my info store?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

If you are already running it, there is no turning back, you have to let it run.  There are events logged look for event 1221 using a filter, it will tell you how much whitespace your database has.
lindemannfoxAuthor Commented:
defrag to 16GB down to 8GB. wheew....
The database does not shrink as things are deleted etc, whitespace is created in the database, so a defrag every now and then is needed after lots of changes.  Check the event and see that you have large amounts of whitespace, if so, a defrag was just needed.
Now thats a nice amount of space savings.  You got a while till you hit the 16GB marker again.  If there becomes a need, you can exceed the 16GB with Exchange 2003 SP2.  There is a registry key change, you can go up to 75GB.
lindemannfoxAuthor Commented:
Will this service pack and registry change work with SBS 2003? If so, can you give me a link that tells how to do this?
Yes.  You can do it with SBS.  Here is a good link I found on the process.
lindemannfoxAuthor Commented:
Thank you very much!
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

From novice to tech pro — start learning today.