If you can solve this you are my hero.

We use exchange 2013, but these clients are using outlook 2010

We have a mailbox - lets call it PS.  It used to be a public folder and we forced them to a shared folder (totally recreated the mailbox and moved items over).  The one major issue with the clients are they were going to lose their quick clicks.  Quick click settings are independent in public folders, but are shared in shared folders (meaning if someone changes the default, it changes for all) .  We migrated to this shared folder in February.  What the users found out, and never told me, is that they were still all able to set their default quick click, and it doesn't change the others.  This is NOT how shared folders act.  infact I cannot reproduce this on ANY shared folder - but somehow they are able to.  at 5pm to 530 EVERYDAY their quick clicks start working correctly and all user default quick click settings goes back to the last person who set theirs - they throw a fit, complain and then when they start their next morning they set their quick clicks independently again and work the whole day.

This is NOT the main issue, but just some background I feel I must share.

There are about 15 users, they have their normal inbox, but they open this PS folder in a new window and work mostly out of that folder.  All 15 users are in online mode(cached disabled) due to the lag cached causes when they are trying to grab or categorize emails.  They categorize the email with their name, work on the clients file, and then when done, they mark it completed and move the email down one level to a subfolder in the PS inbox

So, as a recap, they have been using this since February.  They used this for a good month with no major issues. in late march they started to receive many "cannot move errors" .  It seems to have gotten worse over the months and all 15 users have experienced and will experience this many times a day - there is no rhyme or reason, and is very sporadic.  This error prompts when they move the message from the PS inbox, to the PS inbox subfolder.  "Can't move the items. The item   could not be moved. It was either already moved or deleted, or access was   denied" .  After the move error is received, they do not have to move the mail again, it actually DOES move the item.  however it doesn't show for that person it is moved until they refresh their mailbox, but others see it was moved. 

Users also will notice that their PS inbox will stop auto refreshing new mail, but the mailbox count in bottom left remains accurate. (which they can fix by resorting, doing a send/receive does not fix the refresh).  It appears that the refresh issue occurs when one or multiple users receive the cannot move error

We also notice strange issues like when a user categorizes the email, it doesn't appear to categorize to them - but others can see it categorized and the user has to open the email to see the category

to muddy the waters - other select users on the production floor have access to this mailbox, and every now and then, users will connect to this mailbox(incached) to lookup an email - could their infiltration cause this hiccup?

Where we are today:

• We found this mailbox hit a size of 120GB - we have purged this mailbox and it currently resides at 20GB.  This error is notorious for having a super full deleted items or corruption in deleted so the deleted items were cleansed in full
• All windows updates and office updates have been ran
• NIC driver update and all power save options disabled
• outlook anywhere disabled
• shared mailboxes are NOT in cached
• all users OSTs were deleted
• all users mail profiles were deleted and reestablished
• we use a netscaler/load balancer - we set one user to bypass this, because we thought they were getting disconnected, to try to fix the refresh error(they didn't move emails) - however it appears that the refresh error may be caused by the move error.  I think the netscaler disconnects every 2 min, so perhaps moving the file and it is disconnected, I think we will bypass the netscaler for a few users who move a lot of mail to see if any relief
• time stamps, and having the server team look at logs have provided no help
• Exchange is at rollup5 (I know there was an issues with similar in previous release)

I would like to start from scratch and have a full new mailbox created - but the team seems hesitant

Next steps could be to remove access from the production floor, so only the online users access this folder.

Perhaps faulty user rights, or they need elevated rights for some dumb reason, so we could up their rights

at this point I will try anything, please help :(

Hi Rderenzy,

I recommend you can do a test to narrow down the issue:

1. Remove all users access permission on PS mailbox.(you should backup these permission before removing)

2. Give only one user access permission to PS mailbox.

3. Let this user use PS mailbox and check if the same issues are persist.

Best regards,

thank you sir for the help

this actually WORKS - I did not remove the users, but when on the weekends, nights, or early mornings, we only have one user and they do NOT get the errors.

We are going to recreate the mailbox in full and hope for the best

thank you sir for the help

this actually WORKS - I did not remove the users, but when on the weekends, nights, or early mornings, we only have one user and they do NOT get the errors.

We are going to recreate the mailbox in full and hope for the best

• Marked as answer by Niko.ChengMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 3:05 AM
• Unmarked as answer by Rderenzy 16 hours 57 minutes ago

thank you sir for the help

this actually WORKS - I did not remove the users, but when on the weekends, nights, or early mornings, we only have one user and they do NOT get the errors.

We are going to recreate the mailbox in full and hope for the best

• Marked as answer by Niko.ChengMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 3:05 AM
• Unmarked as answer by Rderenzy 16 hours 57 minutes ago

Thanks for asking.

Deleting and recreating a whole new shared mailbox has cut down the move errors from 30/day to about 4/day.

However, now we are back up grown to 7-11/day

here is more info

What are users doing when this happens?

-Users are working out of a shared mailbox

-Users categorize the email (right click, select color/name) when done they will mark it completed with the flag status

                -They then move the email to a sub folder of the inbox

                                -This is when the move error happens however the email still moves

                                                -When the move error happens, other users will have to manually refresh the mailbox as it seems to break the auto refresh of the mailbox

What is this move error?

Microsoft has a KB on this exact error and reports the cause is a slow/busy drive

**Users do not get a move error early morning or late at night but only one user is working at that time

What have we done to try to resolve this?

• Deleted and recreated all users outlook profiles
  • Also removed/deleted all users OST files
• Performed windows updates in full
• Performed office updates in full
• Assured all users are not in cached mode
• NIC driver updated and optimized to remove any and all power save functions
• Outlook anywhere disabled
• Repaired office
• Reinstalled office
• Installed office 2013 (same issues)
• Rebuilt entire PC
• Rebuilt windows user profile
• Checked Event Viewer
  • No logs reported
• Timestamps handed over to server team to hopefully find error logs no results found
• Connected user directly to VIP could not work due to DriveTrain email issue
• Network has completed time out adjustments on the netscaler
• Severely decreased mailbox size with help of server team(Mitchell)
• Created a brand new mailbox with the help of the server team (Matt)
  • This cut move errors down from 30/day to 4/day
• Mitchel got Adam involved to do some networking traces with the app/server peices

Thanks for asking.

Deleting and recreating a whole new shared mailbox has cut down the move errors from 30/day to about 4/day.

However, now we are back up grown to 7-11/day

here is more info

What are users doing when this happens?

-Users are working out of a shared mailbox

-Users categorize the email (right click, select color/name) when done they will mark it completed with the flag status

                -They then move the email to a sub folder of the inbox

                                -This is when the move error happens however the email still moves

                                                -When the move error happens, other users will have to manually refresh the mailbox as it seems to break the auto refresh of the mailbox

What is this move error?

Microsoft has a KB on this exact error and reports the cause is a slow/busy drive

**Users do not get a move error early morning or late at night but only one user is working at that time

What have we done to try to resolve this?

• Deleted and recreated all users outlook profiles
  • Also removed/deleted all users OST files
• Performed windows updates in full
• Performed office updates in full
• Assured all users are not in cached mode
• NIC driver updated and optimized to remove any and all power save functions
• Outlook anywhere disabled
• Repaired office
• Reinstalled office
• Installed office 2013 (same issues)
• Rebuilt entire PC
• Rebuilt windows user profile
• Checked Event Viewer
  • No logs reported
• Timestamps handed over to server team to hopefully find error logs no results found
• Connected user directly to VIP could not work due to DriveTrain email issue
• Network has completed time out adjustments on the netscaler
• Severely decreased mailbox size with help of server team(Mitchell)
• Created a brand new mailbox with the help of the server team (Matt)
  • This cut move errors down from 30/day to 4/day
• Mitchel got Adam involved to do some networking traces with the app/server peices