Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1868
  • Last Modified:

Cannot delete or move emails from the inbox folder

Hi All,

I have a Exchange server 2007 SP1 x64 installed on a Windows Server 2008 R2 x64 Enterprise edition. We transitioned from Ex2003 to 2007 in November this year and since then everything is running quiet well and am very happy.

Yesterday I update the Server 2008 to SP1, also had issues with space running out on the c: drive, so I had to delete transaction logs manually until we could start receiving emails. After deleting the transaction logs the Mailbox databases wont mount so I had to do eseutil /p and move all the transaction logs etc, that worked perfectly well. I have also moved the exchange que to a different drive to avoid back pressure in the future.

Now the problem is when I log onto outlook 2007, 2010, Active Sync, I can delete emails and everything. But when I logon to OWA (either light or normal) I cannot move or delete emails. On the light version as soon as I click delete it does nothing and just deselects the email. On the standard version, it allows me to delete but the email reappears in 5-10 seconds. When I try to move the email on the standard version it tells me:
"Some items could not be moved. This may be because the folder has reached its size
limit."

Also when the files are deleted from outlook 2007, 2010 and activesync, they still show up on the inbox in OWA. I am able to delete emails from Junk folder and empty deleted items.

I have found this link and am upgrading the exchange to SP3
http://www.errorhelp.com/search/details/152694/some-items-could-not-be-moved-this-may-be-because-the-folder-has-reached-its-size-limit

Could it be related to the repair done and not doing isinteg on the database file?

I know this is a long email, but I really appreciate your time and effort in helping me out.
0
pdahan
Asked:
pdahan
  • 3
  • 2
  • 2
  • +1
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Could it be related to the repair done and not doing isinteg on the database file? - Yes very much possible

As with Exchange 2007 even with Std edition you can have total of 5DB's you can simply create a new DB and move mailboxes with Circular logging enabled and then check for few users and plan for all

- Rancy
"Happy New Year"
0
 
Tony GiangrecoCommented:
Initially would try running Exchange Server Best Practices Analyzer  from the Exchange management console. It checks multiple areas and provides a very good report.
0
 
pdahanAuthor Commented:
I have run a EXBPA health check, connectivity etc but everything is clean and good. I am currently running isinteg alltests will let you know if that works.

Thank you for you help so far. If you have any other ideas please let me know.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Tony GiangrecoCommented:
I'd also run the server BPA
0
 
NicolusCommented:
I concur with Rancy.  Why try to fix a corrupt database when you can migrate to a new one.
0
 
Tony GiangrecoCommented:
0
 
pdahanAuthor Commented:
I did the isinteg and that did fix it, if anyone else is having the same problem please refer to the link below on how to use this tool:
http://support.microsoft.com/kb/301460

Also Rancy, do you really think that after all these problems I should migrate to a new database or should I leave it as it is?

Thank you for all you replies and help.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
To be true this is good but if you move to a new one you will always be assured there is no whatsoever glitches in it ........... so New DB is a recommendation and not forceful suggestion

- Rancy
"Happy New Year"
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now