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

Exchange 2010 SP1 OWA premium not working

After rollup 2 for OWA on Exchange 2010 SP1 OWA stopped working alltogether.  We got the basic client to work(kinda) after setting the default language, right now there are two issues.
1)  premium client doesn't work
2) basic client can't open any attachment or follow a URL w/in an email, trying to open an attachment or click on a link within the email pops up another window that displays the current basic client
We have had an incident open with Microsoft for nearly two weeks and no solution.
  • 7
  • 5
1 Solution
Hi SOPHSupport,

Can you please try the following from an elevated EMS:

cd "C:\Program Files\Microsoft\Exchange Server\V14\Bin\"

Please copy the output and paste here. Test OWA premium connectivity and attachment options too.

Let me know how you get on.
SOPHSupportAuthor Commented:
The output from running the updateCas.ps1 script is at the bottom.  Results for OWA follow
I can login to premium client and get to the inbox,
1) In IE 8 clicking on email won't open it, I get "your network connection is unavailable" however using the reading pane <actions> I can open the email and reply. After opening the email via the reading pane I can open the email directly from the inbox- not all email just the ones I opened via reading pane-actions.
2) In IE 8 and Firefox options doesn't work
3) In FireFox some messages will open directly some won't
4) In FireFox sometimes attachements open mostly I get the error "There was a problem opening your mailbox.  You may have already signed in to Outlook We App on a different browser tab.  If so, clos this tab and return to the other tab.  If that doesn't work, you can try: closing your browser/deleting cookies"

Basic OWA works the same as it did.  Try to open attachment reopens the OWA inbox.

Output of UpdateCas follows
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Bin>Version
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Bin>[16:51:01] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\Current' to 'C:\Program\Files\Microsoft\Exchange Server\V14\Bin>Files\Microsoft\Exchange Server\V14\ClientAccess\owa\'
 [16:51:07] Found 1 OWA virtual directories.
 [16:51:07] Updating OWA virtual directories
 [16:51:08] Processing virtual directory with metabase path 'IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa'.
 [16:51:08] Metabase entry 'IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa/' exists. Removing it.
 [16:51:08] Creating metabase entry IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa/
 [16:51:08] Configuring metabase entry 'IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa/'.
 [16:51:08] Saving changes to 'IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa/'
 [16:51:08] Saving changes to 'IIS://PHEALTH-CAS.sophad.local/W3SVC/1/ROOT/owa'
 [16:51:08] Update OWA done.
 [16:51:08] Updating ECP to version
 [16:51:08] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\Current' to 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\'
 [16:51:08] Update ECP done.
 [PS] C:\Program Files\Microsoft\Exchange Server\V14\Bin>
Is it possible to ask Microsoft Support to provide you with a summary of what has been done so far in terms of troubleshooting and to paste it here. Please ask them to be as detailed as possible.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

SOPHSupportAuthor Commented:
I wish I could ask them, been waiting for them to get back to me for about 1 week.  What they did
rebuilt owa, checked directory permissions and examined quite a few things.  On my own I came across the following in a blog and it solved an initial problem where OWA was pretty much dead, but it left us where we are now.

set-OwaVirtualDirectory "owa (default web site)" -DefaultClientLanguage 1033
Have you emailed the support reps manager(s), if keep the pressure on explaining that most of your organisation cannot use webmail or mobile functionality, they should come back to you.
SOPHSupportAuthor Commented:
My institution is a Premier customer for what thats worth.  Complained to our rep several times, he promises but not much happens.  I don't call on M$ very often, probably been over 4 years since last call, but in the past they provided the best support I had ever experienced.  
In any event I got to looking at the problem and some of it seems to be related to the redir.aspx since the functions that don't work appear to use this executable.  Looking at the output of the UpdateCas I noticed IIS refers to the machine by the private dns which is different then the public.
The private DNS referred to by IIS is normal, that command is to copy across any files that may have been corrupted. I would keep the pressure on, I've had a situation like that before where at 3am, I sent an email to all MS reps in the chain of emails demanding that Microsoft get back to me. I got a response 10 mins later from a senior manager explaining that he will get an engineer to the issue resolved, 2 hours later all sorted. I made the call as a MS Partner, never the less in my case the Exchange server in question could not receive emails. You just have to explain that you're getting pressure from management that this is affecting more than 50% of the business.

Could you tell me are you running Exchange on 2008 or 2008 R2? Do you have a self signed cert or proper 3rd party?
SOPHSupportAuthor Commented:
2008R2 proper signed cert from 3rd party
SOPHSupportAuthor Commented:
Found the problem(s)
Using IIS managment tool, drill down to the exchange site, in the redirect property make sure to uncheck 'redirect all to ...'   This solves the inability to open URLs w/in messages, download attachments and a few others.  

I haven't completed this yet but expect it to work, set default language to 0, this should enable options, change password, set automatic replies.  This should likely correct the problems with the view functions as well.

There is a site that lists what the redirect properties should be, from the default site down, and it comes with pictures!  As soon as I can find where I put the link I will update this post.

There is another link that discusses setting the default language to 0 as a fix for the remaing unsolved symptoms.  I will update this post with the cmdlt syntax as soon as I verify it works.

Very disappointed with Microsoft support, this should have been a 30minute fix.
Great to hear, if could you provide the website link you found your solutions from.
SOPHSupportAuthor Commented:
Finally got Microsoft to respond and the problem solved.  From looking at the number of web pages that discuss this problem it appears that it is fairly common and there are many purported solutions that do provide some 'relief', i.e. changing the settings for redirect within the IIS managment tool.  
However, at least in our situation, the real problem is the webconfig file in the C:\program files\Microsoft\Exchange Server\V14\ClientAccess\OWA folder.  As I mentioned earlier changing the redirect settings for the exchange directory 'fixed' most of the OWA problems users in our 2010 Exchange were experiencing but for our legacy 2003 users it no longer allowed them to use servername\exchange as the URL to open the 2003 OWA.  The solution that resolved all issues was in the aforementioned web.config file,  there was a second system.webserver at the end of the file that shouldn't be there (I placed this section at the end of this missive), and according to the MS rep the GUI for managing IIS settings is unreliable so to eliminate any issues raised by our use of the GUI we went through the command line to set all of the sites redirect settings.  Oh joy.

web.config stanza that we removed follows
        <httpRedirect enabled="false" destination="https://phealth.soph.uab.edu/owa" childOnly="true" />
                <add path="*">
                        <add provider="ASP" verbosity="Verbose" />
                        <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" />
                        <add provider="ISAPI Extension" verbosity="Verbose" />
                        <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI" verbosity="Verbose" />
                    <failureDefinitions statusCodes="403" />
        <httpErrors errorMode="Custom">
            <error statusCode="403" subStatusCode="4" path="https://phealth.soph.uab.edu/owa" responseMode="Redirect" />
SOPHSupportAuthor Commented:
Really disappointed with MS support (not individuals at Experts Exchange).  It shoudn't require 2 weeks and getting angry to have a case escalated.  In the past if the 1st rep couldn't solve the problem in an hour he would escalate it, if 2nd rep couldn't solve he would ...   I can recall having developers step in without my having to ask.  I appreciate the problem being solved but it took too long and I had to call repeatedly and complain.  Given the web.config file was not changed by me or my staff this seems certain to be an issue in MS upgrade QA.  
ok guys any one of you can give us a steps for solution or the command line which fixes the redirection issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now