We help IT Professionals succeed at work.

Exchange 2007 OWA Access

PanamaBosco
PanamaBosco asked
on
Medium Priority
374 Views
Last Modified: 2012-05-06
While trying to access our company exchange 2007 OWA, we keep getting this response and no access is permitted. I have not installed any software. The only thing that was turned on was Windows automatic update on my Server 2008 Std, which also hosts our exchange 2007 Server. Which has been working fine.
Server Error in '/owa' Application.
--------------------------------------------------------------------------------
 
Runtime Error 
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 
 
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
 
 
<!-- Web.Config Configuration File -->
 
<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 
 
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
 
 
<!-- Web.Config Configuration File -->
 
<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Open in new window

Comment
Watch Question

Expert of the Quarter 2009
Expert of the Year 2009

Commented:
That error doesn't really show much of any use unfortunately.
Has it ever worked?
If you run the Best Practises tool from the toolbox, does that show anything of interest?

-M

Author

Commented:
Yes, it was working perfectly until last week after a windows update that forced the server to reboot on its own.

Author

Commented:
I ran the Best Practices Tool but nothing negative.
Expert of the Quarter 2009
Expert of the Year 2009
Commented:
It looks like a netframework error. However there isn't a great deal to work with.
There was an update for Exchange in last week's patches, which I haven't seen any reports of problems with it.

Try removing the OWA Virtual directory and recreating it.
http://telnet25.wordpress.com/2009/01/21/how-to-reset-virtual-directories-exchange-2007/

-M

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

Ask the Experts
CERTIFIED EXPERT

Commented:
You will need to make the change suggested in the error message to get the required debugging information.  The message is suggesting that you find your root web.config file (maybe in C:\inetpub ?), and add the line

  <customErrors mode="Off"/>

somewhere between

  <system.web>

and

  </system.web>

Author

Commented:
Thanks. frame network 3.5 reinstallation fix it.
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.