Hello, I am trying to get my OWA set up and it seems i am either configuring something wrong or missing something all together. I haven't ever been able to access my OWA site on this Exchange server. This is a new Exchange build with no previous versions. I do have a website set up and running through IIS. I am using DotNetNuke to run my website and i already know how to configure DNN to access OWA, but when im in IIS, I right click on my OWA virtual directory and select browse and i get the following error.
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.
Details: To enable the details of this specific error message to be viewable on the local server machine, 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 "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
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.
I do have a website set up and running through IIS. I am using DotNetNuke to run my website and i already know how to configure DNN to access OWA
What is DotNetNuke and why are you using it to manage IIS on Exchange?? Why not just leave the configuration as default. What do you mean you are trying to "configure" OWA? OWA works with no configuration changes needed out of the box! Are you able to connect to the default site? (as you mentioned, there is a certificates error but that is because you are still using the self-signed certificate. You need to purchase a public SAN certificate with multiple names to resolve this issue).
_____________________________
Ibrahim Benna - Microsoft Exchange MVP Forum Moderator Navantis
DotNetNuke is just a website manager that runs on our exchange server. It controls our webpage virtualization through SQL and .css files. It doesn't manage IIS. the DefaultWebPage file path is to the DotNetNuke directory on the local hard drive.
I have reinstalled exchange and server 2003 and OWA has never worked correctly out of the box for me.
The default site is www.highwindscasino.com so i know it is working correctly. And when in IIS, I do see the OWA virtual directory, I just don't have the ability to actually access it. Is it because my default site isn't in the Inetpub directory? Is there any configuration at all to get OWA set up? Even the smallest details would be greatly useful.
To be honest with you, I always tell my clients to leave the server running Exchange simply as an Exchange server. If you need to install applications on the machine, make sure they are exchange-aware applications. I really have no experience with DotNetNuke and strongly feel it could be the root of your issues. Since it is managing IIS then Windows would not be manage it and Exchange REQUIRES IIS to be functioning properly. I would recommend you uninstall this application and let Windows manage IIS on this server. By doing this at least we can eliminate if this app is causing the issues.
_____________________________
Ibrahim Benna - Microsoft Exchange MVP Forum Moderator Navantis
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> haven't ever accessed OWA 
haven't ever accessed OWA - 
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
