Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
"Item could not be found" when I move an message
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
"Item could not be found" when I move an message - 21.Mar.2006 6:39:21 AM
|
|
|
rwmnau
Posts: 3
Joined: 3.Aug.2004
From: Phoenix, AZ
Status: offline
|
I'm not sure if this is the correct forum, but the problem only seems to manifest itself through OWA, so I thought I'd start here. I have a handful of messages in one user's mailbox that display an error message when I try to move them to another folder form the inbox - they say "Item could not be found. It may have been moved." I searched online, and the only thing I can find related to this error seems to be that it occurs if you install URLScan, which I haven't done. Does anybody have any thoughts about what might be causing this? I seem to be able to delete the messages (move them to the trash), but I can't move them to another folder. This doesn't happen to every message in the user's inbox - just certain messages. The only thing I've noticed that the messages have in common is that they have a period somewhere in the subject line. I don't know if this is causing it, but it seems to be a pretty consistent commonality in the messages that exhibit this behavior. Any thoughts at all? Does the store need some sort of repair, or is there a problem with IIS where it suddenly can't handle periods in subject lines? It wasn't always this way, but it's been this way long enough that it can't be traced back to a certain event. Thanks for any help that you're able to provide! UPDATE - I realize that I didn't share this before, but I have Exchange 2003 Standard installed on top of a Windows 2003 Standard Service. I'm not sure if it has R2 installed - I'm not in front of it currently - but it at least has SP1 installed. I don't know if somehow, some URLScan-type functionality was added in this update, but I haven't added URLScan by itself. Does anybody have any ideas?
< Message edited by rwmnau -- 22.Mar.2006 6:47:54 PM >
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|