Exchange Server Forums

Cannot Open Older Messages?...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Cannot Open Older Messages?...

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Cannot Open Older Messages?... - 23.Feb.2004 10:57:00 AM

Saqib

Posts: 1
Joined: 23.Feb.2004
From: Islamabad, Pakistan
Status: offline

Last Friday I repaired my currupted information store and defraged it and then re-started my exchange server 5.5 (SP4).

Now I can open, read and reply to all the new messages but can't open, read or delete my old messages before this excercise. whenever I try to open any old message it gives me error "Cannot open this item. Operation Faild"

Can anyone help me with this? I've tried soft recovery and checked the integrity and defraged it again but still no success with my old messages. "[Confused]"

Post #: 1

Featured Links*

RE: Cannot Open Older Messages?... - 24.Feb.2004 1:00:00 AM

mtravers

Posts: 31
Joined: 6.Jul.2003
From: charlotte, nc
Status: offline

Was this database ever hard repaired? In other words did you run eseutil /p on this database? If you are not certain, stop the information store and run eseutil /mh <database path> for example eseutil /mh c:\exchsrvr\mdbdata\priv.edb

In this output look for the repair count. If repair count is more than 0, this database has been hard repaired. If the database has been hard repaired and you did follow with a defragmentation, there may be no workaround as this can be the result of a hard repair. This is why this is only recommended in rare circumstances.

Another thing to check is when running isinteg, how many errors do you receive in the summary? If it is more than 0, you will want to run isinteg again until you receive 0 errors.

As a test, for one mailbox, export the contents to a pst file, delete and recreate the mailbox, then import the pst file. Do you still have the same problem? If not, then you can use the exmerge utility to do this for all users, once all mailboxes are exported, create a blank database

To create a blank database, stop the IS, rename all mdbdata folders to mdbdata.old. Create new mdbdata folders and send a piece of mail to all users to populate the mailbox. Now use exmerge to import the pst files.

You may also want to try temporarily disabling your anti-virus. To do this go in the registry to

HKLM\System\CurrentControlSet\Services\MsExchangeIS\VirusScan

Set enabled to equal 0

If the problem is anti-virus, then you will want to call your AV vendor for a resolution

Hope this helps

(in reply to Saqib)

Post #: 2