Have a look in IIS Manager to see which is missing, the OWA VDir, or the Lang.owa file that's supposed to be in it.
Main Topics
Browse All TopicsHi,
I put in a new Windows 2003 R2 x64 server for ourselves the other day. Installed Exchange 2007 etc. and all seemed well. During the install of Exchange I installed .Net Framework 2.0 and .Net Framework 3.0.
The other day I wanted to install some software that created a few virtual directories in IIS. It was asking for .Net 1.1 so I downloaded and installed it.
I then noticed no pages would show up when I browsed to http://servername. If I browsed to https://servername I'd get a certificate error, if I accepted that I'd just get an error, no page served up. I asked here and eventually came across what I thought was the solution, something to do with the various versions of ASP.NET and IIS in 32bit/64bit. So I folowed the instructions here - http://support.microsoft.c
IIS seems to be working better now. However when I go to https://servername/owa I get a certificate error (normal), accept this, get to the logon screen, enter my credentials (tried all different varieties), press OK, get to choose language settings, press OK again and get
---------
http://ntserver05/owa/lang
The page cannot be found
HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)
----------
I'm not sure now if this is an IIS problem or an Exchange 2007 problem, any help appreciated though! I'm not even certain if OWA was working after I first installed Exchange 2007 as I didn't get time to try it before screwing up the .Net 1.1 stuff, but I'm sure it was probably working fine as it was a clean build.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The OWA directory is there. I don't see lang.owa there, but it isn't there on a working Exch2007 server either, so I reckon that file is generated on the fly or something like that?
I was hoping not to have to reinstall Exch 2007 for something like this. I've never tried it, but if I just install over the top will it maintain data and settings? If the problem is IIS related I reckon it may not solve the problem anyway?
The OWA directory has quite a lot of stuff in it, is it just as simple as delete and create again? Is it not linked to Exch 2007 in some way that will make this procedure kinda risky?
The OWA VDirs are created using the powershell. I don't have one to hand right now, but the commands are Remove-OWAVirtualDirectory
http://technet.microsoft.c
Excellent, removing and adding the owa directory worked perfectly! Thanks guys!
Here are the commands I used from the Exchange Shell for future reference -
1.
Get-OwaVirtualDirectory
This gives a list of the OWA virtual directories, top one should be something like "owa (Default Web Site)".
2.
Remove-OwaVirtualDirectory
Deletes the default "owa" directory.
3.
New-OWAVirtualDirectory -OWAVersion "Exchange2007" -Name "owa (Default Web Site)"
Create the "owa" directory again.
I had the same problem (posted by the original author) and put together these instructions from a combination of this post, other EE posts, and various microsoft articles. Worked like a charm for me.
1. Open up the Exchange PowerShell command window.
2. Run: Get-OwaVirtualDirectory
This will display a list of all OWA-related virtual directories under the Default Web Site. Note that you may receive an error in red text on some or all of the virtual directories if they are not working properly (which is to be expected.)
3. Run the following commands to delete each virtual directory:
Remove-OwaVirtualDirectory
Repeat this step for each virtual directory found after running Get-OWAVirtualDirectory in step 1, replacing the owa (Default Web Site) with each virtual directory name.
Example:
Remove-OwaVirtualDirectory
Remove-OwaVirtualDirectory
Remove-OwaVirtualDirectory
Remove-OwaVirtualDirectory
4. Run the following commands to re-create each OWA virtual directory:
New-OWAVirtualDirectory -OWAVersion "Exchange2007" -Name "owa (Default Web Site)"
new-OwaVirtualDirectory -OwaVersion "Exchange2003or2000" -VirtualDirectoryType "Mailboxes" -DomainController dc_name
new-OwaVirtualDirectory -OwaVersion "Exchange2003or2000" -VirtualDirectoryType "Exadmin" -DomainController dc_name
new-OwaVirtualDirectory -OwaVersion "Exchange2003or2000" -VirtualDirectoryType "PublicFolders" -DomainController dc_name
new-OwaVirtualDirectory -OwaVersion "Exchange2003or2000" -VirtualDirectoryType "exchweb" -DomainController dc_name
Where dc_name is the name of your windows domain controller.
Thats itthese virtual directories should be re-created, and OWA should function.
ANOTHER SOLUTION:
For some, it is impossible to recreate the directory OWA.
What I have done:
1. Uninstall Framework 1.1
2. Installing Framework 2
3. Add Hostfix Framework 2
4. Delete the role Access Client (CAS) server via the installation CD Exchange: Start, Run, cmd: go on the CD, type: setup.com / mode: uninstall / role: CA
5. Installing the new role: setup.com / role: CA
6. Everything is back in order
Business Accounts
Answer for Membership
by: busbarPosted on 2007-04-20 at 04:13:48ID: 18945396
try to reinstall exchange 2007, if this is not available try to remove the OWA virtual directory and then recreate it again