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 :(