Unable to move messages from inbox to outlook pst

Following a hardware problem on our Windows 2000 Server / Exchange 2000 server box (lost two of five hard drives in Raid 5 config at the same time) and subsequent recovery, we're experiencing the following problem.

1.  Some users are unable to move some messages from the exchange folders (inbox, drafts, etc.) to folders within a PST saved on their hard drives.   I happen to have that problem, and I am running an Outlook 2003 client.   Some messages do move (typically messages from people outside the company) and others don't, always with the error "the item could not be moved.  it was either already moved, deleted, or access is denied."   The messages can be moved around withing the exchange mailbox (from inbox to drafts or deleted items and back) just fine.

2.  Similarly, we cannot export the contents of our exchange folders to a PST.

2.  The same people with Outlook 2003 clients are unable to view any of their mail when Cached exchange mode is enabled.  Not sure if this is a related problem, so I'm throwing this symptom out there.  

3.  We've run the standard Exchange utilities on the database and this hasn't cured the problem.
Who is Participating?
I have never found that I needed to run it more than 3 times.

You may want to try this:
If you have the Enterprise version of Exchange, create another mailbox store.
Then move one of the problem mailboxes over to the new store. See if this corrects the problem.
If so then move the rest of the mailboxes.


Pick one of the problem mailboxes. Try to export the contents to a PST file using EXMERGE. Make sure that you have the proper permissions configured to do this. Add the PST to an Outlook profile to verify what was extracted. If it looks ok then continue on with the next steps. Remove the PST file from the Outlook profile.
Delete the mailbox. Purge the mailbox. Create a new mailbox for the user. Use EXMERGE to import in the contents of the PST file.
Create a new Outlook profile pointing to the mailbox.
Check for problems.
If all seems ok then you can do this for the rest of the mailboxes.
You say you ran utilities against the database. I am assuming that this was ESEUTIL /P.
Did you also run ISINTEG -FIX against the database. This should always be run if ESEUTIL /P is run.

The symptoms you report sounds like this could be the problem. It is advisable to run ISINTEG -FIX until you get 0 warnings, 0 errors, and 0 fixes or until the counts no longer change.
tomgodinAuthor Commented:
ISINTEG -FIX was run, however I don't think our person ran it more than two or three times, and the counts did change every time.  Is this something that could take 10 (50, 100,...) iterations to achieve the desired result?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.