• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3710
  • Last Modified:

unable to delete messages in OWA after exchange 2010 SP1 install

after installing SP1 for Exchange 2010 when we try to delete any messages in OWA the following error is displayed:
The action you tried to perform couldn't be completed because there's a configuration problem on the server. If the problem continues, contact your helpdesk.

does anyone know how to resovle this?

thx - S.
0
siber1
Asked:
siber1
  • 12
  • 9
1 Solution
 
ShareefHuddleCommented:
Here is what to do:

Try deleting or renaming the web.config file in your ...inetpub\wwwroot folder


http://social.technet.microsoft.com/Forums/en-GB/exchange2010hosters/thread/e45d7277-b205-4791-a430-631b163a5072
0
 
siber1Author Commented:
actually, that is not a good solution for me as this file contains the redirect that i need to use to HTTPS
also, i would think there must be a better solution that deleting a key file on the server.

0
 
ShareefHuddleCommented:
Ok well try this:

Rename the web.config file.

Then follow the steps in Brian's blog for your redirection.

http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
ShareefHuddleCommented:
Forgot to also add backup your default web site to :)
0
 
siber1Author Commented:
just tried that, and the same problem occurs.
when i rename the web.config file, and re setup the redirect, a new web.config file is generated. I still have the same issue. cannot delete messages or move to personal archive. the exact message is:

The action you tried to perform couldn't be completed because there's a configuration problem on the server. If the problem continues, contact your helpdesk.
0
 
ShareefHuddleCommented:
Does it work on owa lite?
0
 
ShareefHuddleCommented:

Open IIS Manager and select the Default Web Site. On the right hand side, under actions, click bindings. On one of the http bindings is the Internal FQDN for OWA and removing this fixed the problem.
0
 
siber1Author Commented:
yes, works in OWA lite.

I just took off the redirect and deleted the web.config file completely. still having the same issue.
0
 
siber1Author Commented:
not sure i follow, under the HTTP bindings i am not specifying a host header value, so no internal FQDN is present.
0
 
ShareefHuddleCommented:
Hmmmmmm....
0
 
ShareefHuddleCommented:
And you did iisreset? I know it's a dumb question but just want to make sure :)
0
 
siber1Author Commented:
yes, several times.
0
 
ShareefHuddleCommented:
Is this in your web.config?

<system.webServer>
<httpRedirect enabled="true" />
</system.webServer>

If so remove it and iisreset
0
 
siber1Author Commented:
I have deleted the web.config all together. it no longer exists. i also removed the redirects i had in place. still the same issue.
0
 
ShareefHuddleCommented:
Check your /exchange and verify that it doesn't state redirect request to it
0
 
siber1Author Commented:
no luck. same issue.
0
 
ShareefHuddleCommented:
Do you have your ssl port set to all unassigned or ip specific?
0
 
ShareefHuddleCommented:
Well it is late here. If you find the fix please post.

Have you looked at this msexchange forum?

http://forums.msexchange.org/m_1800538473/mpage_1/key_/tm.htm#1800538473
0
 
siber1Author Commented:
Hi Sharee, i ended up calling MSFT and the issue is now resolved. I ended up having to change the way i was redirecting, as well as reset the virtual directories.

cheers!

S.
0
 
siber1Author Commented:
ended up calling MSFT to resolve.
0
 
ShareefHuddleCommented:
Do you mnd posting the steps they walked you through for the redirector?
0
 
swbruce21Commented:
I resolved this issue using by uninstalling the CAS role and reinstalling it.  It took about 45 minutes total because 4 hotfixes have to be reinstalled before you can reinstall CAS.  Each hotfix asks for a reboot.

There is also a temporary workaround that got me by for a couple of days before I fixed it. Disable "SSL Required" on the EWS virtual directory.  The connections still seem to be in an SSL session.  Some other applicaiton error events are caused by this temporary workaround.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 12
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now