Solved

Cannot delete or move emails from the inbox folder

Posted on 2012-12-25
8
1,810 Views
Last Modified: 2012-12-26
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
Comment
Question by:pdahan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 52

Accepted Solution

by:
Manpreet SIngh Khatra earned 500 total points
ID: 38720169
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
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38720224
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
 

Author Comment

by:pdahan
ID: 38720299
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
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38720302
I'd also run the server BPA
0
 
LVL 4

Expert Comment

by:Nicolus
ID: 38720317
I concur with Rancy.  Why try to fix a corrupt database when you can migrate to a new one.
0
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38720327
0
 

Author Comment

by:pdahan
ID: 38720465
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
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38721819
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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

635 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question