General discussion

Locked

Exchange 5.5 mailbox problem

By j ·
i have a user that is registering more than 60 MB and 11,000 items in her mailbox that i can see on the server. but we can't find anything to delete, we did a scan on all files in her mailbox greater than 10k and there was only 1 (it was only 23k),the rest are even smaller files. how do i detect corruption? is exmerge the best way? if so, can i do this on one mailbox and keep the services running? if so, how?
thanks,
jeremy

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange 5.5 mailbox problem

by tony.colgrove In reply to Exchange 5.5 mailbox prob ...

Check to see if the user has journaling turned on. By the number of items you see, that is what I expect. Each time a doc, xls, etc is accessed, it makes a small (but they add up) item in the journal. If this is the case, you can change the view to see a list of all items, select them all and delete them.

Collapse -

Exchange 5.5 mailbox problem

by j In reply to Exchange 5.5 mailbox prob ...

Poster rated this answer

Collapse -

Exchange 5.5 mailbox problem

by mebudman In reply to Exchange 5.5 mailbox prob ...

Your problem is in her Journal. Nasty if you don't keep it under control. By default outlook 97 turns this on and the setting is then kept with your profile if you upgrade to 2000.

As for your other question about integrity checking the Information Store.

Depending on the size of your information store and the number of users and the amount of email generated by and for said users, this should dictate when offline database maintenance is performed.

Relatively small IS <700MB should be done at a bare minimum of once a year, quarterly if need be.
Mid size IS <5GB should be done at least quarterly or every other month
Large size IS >5GB should be done monthly.

Stop the IS
Run eseutil /d /ispriv to defrag the store (clean up unused pages and reduce the amount of whitespace in the database, this is the only way to shrink the amount of diskpace used by the IS, the online defragmenter only consolidates free space)

eseutil /g /ispriv checks integrity

before using eseutil /p if you have any questions make sure you have a good backup and all other remedies have been tried. This is sledgehammer approach to fixing IS startup/consistency problems.

Let me know if you have anymore questions.

Collapse -

Exchange 5.5 mailbox problem

by j In reply to Exchange 5.5 mailbox prob ...

Poster rated this answer

Collapse -

Exchange 5.5 mailbox problem

by j In reply to Exchange 5.5 mailbox prob ...

This question was closed by the author

Back to Software Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums