We help IT Professionals succeed at work.

Outlook Web Access - Can't delete or move anything - Get 'Some items can't be deleted.' message when attempting.

ner_1808
ner_1808 asked
on
Medium Priority
1,085 Views
Last Modified: 2012-06-27
When I access my Outlook Web Access mailbox, all seems fine. If I try to move or delete a message I get the following alert:
"Some items can't be deleted. They were either moved, already deleted, or access was denied."

I am an exchange administrator so permissions should not be a problem. I have recently changed the OWA to use HTTPS and have installed RDP over HTTP network service on the server recently recently. These are the only changes made recently, except for the usual MS security type updates.

Any ideas would be useful. My Outlook access to the mailbox remains perfect.
Comment
Watch Question

Expert of the Year 2007
Expert of the Year 2006

Commented:
Try it from another machine.
Try flushing out the temporary internet files.
Does it affect any other users?

Ironically being the administrator can cause problems, as the administrator is actually restricted from doing certain things in Exchange. It doesn't not give you rights to do everything - which is why you should have two accounts - a user account and an administrator account.

Simon.
CERTIFIED EXPERT

Commented:
Is it possible that you have set up a server-side rule in Outlook to move or delete messages after you have read them?

Author

Commented:
Have deleted all off-line content and deleted all cookies too. Still receive the same message when attempting to delete and email.
I do have two accounts, one admin and one normal. I am using my normal account. I will check that my personal account does not have any admin rights, but I shouldn't think so.
No rules setup on the server.
I am assuming it is not affecting anyone else, as I am sure I would have had service desk calls by now, but again need to confirm!

Author

Commented:
I have check all permission issues and there are none.
I am publishing the OWA through ISA server and bridging the SSL externally to port 80 internally. This is the change I made. Previously all was fine when just using port 80.
If I connect directly to server internally on either HTTP or HTTPS then all is fine. If I try externally where it is being bridged then the delete command seems to fail.
I will remove the bridging to see if that resolves it later, but does anyone have any ideas why the bridging should cause a problem?
CERTIFIED EXPERT

Commented:
Someone had a similar issue here:

http://forums.isaserver.org/m_50254200/mpage_1/tm.htm#2002030356

Some of the suggestions might work.

Author

Commented:
I have finally solved this problem. Much wasted time with erroneous error messages. It turns out that ISA Server 2004 is designed to not accept wildcard certificates used internally. Only external wildcard certificates allowed and internal ones must be single host named ones. It would be nice if the ISA logs indicated that this might be the issue and I could have saved many hours of research and attempted fixing.

Oddly enough it was another https service I was publishing that failed totally that got me to this solution. I am now using HTTP internally till I sort out another issue with my Root CA!!

Thanks for your help anyway.
Commented:
Closed, 250 points refunded.
DarthMod
Community Support Moderator

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.