RE: OWA Not working Page not Found

Hello Customer,

Thank you for kind update.

Since the previous steps cannot resolve your issue, I would like to suggest
you reset the Exchange OWA virtual directories on SBS:

Note: if you had already perform the steps in this KB, please try to
confirm the steps.

How to reset the default virtual directories that are required to provide
Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services
in Exchange Server 2003
http://support.microsoft.com/?id=883380

I. Rest OWA virtual directories
1. Install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource
Kit Tools, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en
Note If you do not want to install all the IIS tools on your computer, you
can install only the Metabase Explorer 1.6 component. To do this, follow
these steps:

a. Double-click iis60rkt.exe, and then follow the instructions that are on
your screen until you reach the Setup Type page of the IIS 6.0 Resource Kit
Tools Setup Wizard.
b. On the Setup Type page, click Custom, and the click Next.
c. Click to clear all the IIS Resource Kit Tools and components check
boxes except the Metabase Explorer 1.6 check box.
d. Click Next, and then click Finish.

2. Back up your IIS metabase. To do this, follow these steps:
a. Start IIS Manager.
b. Right-click Default Web Site, point to All Tasks, and then click Save
Configuration to a File.
c. In the Save Configuration to a File dialog box, type a configuration
name in the File name input box, and then click OK.

3. Delete the virtual directories for Outlook Web Access. To do this,
expand the Default Web Site in the left pane of IIS Manager, right-click
Exadmin, and then click Delete. Click Yes when you are prompted with the
question of whether you want to delete this item.

Repeat this step for the following virtual directories:
Exchange
ExchWeb
Microsoft-Server-ActiveSync
OMA
Public

4. Quit IIS Manager.
5. Click Start, point to All Programs, point to IIS Resources, point to
Metabase Explorer, and then click Metabase Explorer.
6. Expand LM, right-click DS2MB, and then click Delete. Click Yes when you
are prompted with the question of whether you want to delete this key and
all subkeys.
7. Quit IIS Metabase Explorer.
8. Click Start, point to All Programs, point to Administrative Tools, and
then click Services.
9. To restart the Microsoft Exchange System Attendant service, follow
these steps:
a. Click Start, click Run, type services.msc , and then click OK.
b. Right-click Microsoft Exchange System Attendant, and then click
Restart.
c. When you are prompted to restart the dependant Exchange Server
services, click Yes.

Note When you restart the Microsoft Exchange System Attendant service, the
Microsoft Exchange Information Store service is also restarted. In this
scenario, your Exchange Server users lose connectivity to their Exchange
Server mailboxes.
The virtual directories are re-created. To verify that the virtual
directories are re-created, start IIS Manager, and then view the Default
Web site folder.

Important If the virtual directories are not re-created after 15 minutes,
restart your computer.
10. Reset the access permissions to Anonymous. To do this, follow these
steps:
a. Start IIS Manager, right-click ExchWeb, click Properties, and then
click the Directory Security tab.
b. Under Authentication and access control click Edit, and then verify
that the Enable anonymous access check box is turned on.
c. Click to select the Integrated Windows authentication check box, click
OK, and then click Apply.
d. If you an Inheritance Overrides dialog box appears, click Select All,
and then click OK.
e. Under Authentication and access control, click Edit, and then click to
clear the Integrated Windows authentication check box.
f. Click OK two times, and then quit IIS Manager.

Use a Web browser to verify that you can connect to your Outlook Web Access
server. If you are also running other mobility services, verify that you
can connect to these services by using an appropriate client.

II. This issue may relate to some antivirus or anti-spam filter on this
issue. Therefore, I suggest you disable any anti-spam and anti-virus
software on SBS and client computer. Then test this issue.

III. If the issue persists, please try to do clean boot on SBS and client
computer at same time to narrow down this issue:

To clean boot the problematic computer, please use the steps below:
a. Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.

b. In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.

c. Click to clear the check mark from the "Load startup items" below
Selective Startup.

d. Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services. Please note that the Exchange services could be marked as
non-Microsoft. Please do not disable those services.

e. Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.

f. After restarting, please check whether this issue will reoccur.

If we cannot resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:

1. Please try to create a new user account, then access its OWA. Do you get
the same error?

2. Please capture screenshots on the error 404 page and send the pictures
to me at v-terliu@xxxxxxxxxxxxx

3. Gather IIS log:

a. Open IIS snap-in.

b. Right click Default Web Site and click Properties.

c. Uncheck the "Enable Logging" box and click Apply.

d. Go to C:\WINDOWS\system32\LogFiles\W3SVC1 folder and move all files to a
backup location.

e. Check "Enable Logging" box and click OK.

f. Run IISReset command.

g. Reproduce the problem and send the log file in
C:\WINDOWS\system32\LogFiles\W3SVC1 folder to me for research.

4. Gather IIS Metabase:

1) Download the IIS Resource Kit tools from the following page:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en

2) Install it, run MBExplorer (Metabase Explorer)

3) Right click the "LM" node and choose "Export to file".

4) Specify a file name, specify the password and finish the export.

5) Send the file and the password to v-terliu@xxxxxxxxxxxxx

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: OWA Not working Page not Found
| thread-index: AcfQWlbz9qU4F4rDQ1e3e3hZAuEZ6g==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?QnJlbnQgS2VubmVkeQ==?=
<BrentKennedy@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <C0932DA4-BDC3-48B1-A277-27B1E171ED07@xxxxxxxxxxxxx>
<7yVgE5A0HHA.4844@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: OWA Not working Page not Found
| Date: Fri, 27 Jul 2007 07:28:02 -0700
| Lines: 256
| Message-ID: <77CCCB00-4A7A-49E9-AACC-05FDD3467922@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:52867
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Let me clarify:
| I get a "page not found" after i login to OWA.
|
| So when i go to https://serverip/exchange from the server itself or a
client
| machine, i get the OWA form based login. I then login with just the user
| name and password. After i hit the login button, i get a page with two
| frames and the two frames have pages in them, each says "page not found".
I
| see the colored bar that splits the page normally, its just the pages in
each
| frame say page not found.
|
| 1. I checked on that: Currently the smtp address that is bolded is
| "bktest@xxxxxxxxxxxxxxxxxxxxxx". The "bktest@xxxxxxxxx" smtp address is
not
| bolded but is the servers local domain. I have a test server setup with
a
| local and web domain and the web domain as bolded, works fine.
|
| I also tried to login with bktest@xxxxxxxxx and that also produces the
page
| not found. Now currently the servers default domain in the IIS security
| configuration is setup as " \ ". Which i would assume would log the
user in
| automatically as bktest@xxxxxxxxxx
|
| 2. Share point is installed on the server, but not the IIS default
website.
| When i tried to follow the directions in that KB i stopped at the part
where
| you edit the default website via the sharepoint administrator. When i
click
| on the default website i get a help page that tells me i need to run a
| command from the command prompt to install share point on that website.
So i
| figured sharepoint was not installed on the default website.
|
| 3. There is no proxy installed. I am accessing the machine directly from
| the console and clients. Liike i said, i can bring up the exchange owa
login
| page, its just once i login, i get two frames with page not found in each
| frame.
|
| Any ideas?
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Brent,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that you get "page not
found"
| > error when you access OWA. If I have misunderstood the problem, please
| > don't hesitate to let me know.
| >
| > Based on my research, there are many probably causes refer to this
issue. I
| > suggest we try the following steps to see if we can resolve this issue:
| >
| > I. This issue occurs if the user account that you used to log on to OWA
| > does not have an appropriate Simple Mail Transfer Protocol (SMTP)
address.
| >
| > To resolve this issue, obtain the latest service pack for Exchange
Server
| > 2003. For more information, click the following article number to view
the
| > article in the Microsoft Knowledge Base:
| > 836993 How to obtain the latest service packs for Exchange Server 2003
| > http://support.microsoft.com/?id=836993
| >
| > HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly
| > http://support.microsoft.com/?id=293386
| >
| > II. This problem may occur after you install Microsoft Windows
SharePoint
| > Services on a server that is running Microsoft Exchange Server. The
Windows
| > SharePoint Services ISAPI filter handles all incoming URLs. When you
browse
| > one of the Exchange Server 2003 virtual directories, the ISAPI filter
does
| > not locate the URL path of the folder.
| >
| > To resolve this problem, and to have Windows SharePoint Services and
| > Exchange Server 2003 both function correctly, you must enable Kerberos
| > authentication and exclude the folders (directories) that Microsoft
| > Exchange Server 2003 uses. To do so, follow these steps:
| >
| > 1. Configure the virtual server that is running Windows SharePoint
| > Services and Exchange Server 2003 programs to use Kerberos
authentication.
| >
| > When a virtual server is extended with Windows SharePoint Services,
| > Kerberos authentication is disabled Integrated Windows authentication
is
| > enabled. For Exchange Server 2003 to work correctly, you must configure
the
| > virtual server to use Kerberos authentication. For more information
about
| > how to configure Windows SharePoint Services to Use Kerberos
| > authentication, click the following article number to view the article
in
| > the Microsoft Knowledge Base:
| >
| > 832769 How to configure a Windows SharePoint Services virtual server to
use
| > Kerberos authentication and how to switch from Kerberos authentication
back
| > to NTLM authentication
| > http://support.microsoft.com/?id=832769
| >
| > 2. Exclude the following folders (directories) that Microsoft Exchange
| > Server 2003 uses:
| > Public
| > Exchange
| > Exadmin
| > OMA
| > Microsoft-Server-ActiveSync
| > ExchWeb
| >
| > To do so, follow these steps:
| > a. On the server that is running Exchange Server 2003 and Windows
| > SharePoint Services, click Start, click Administrative Tools, and then
| > click SharePoint Central Administration.
| > b. In the Virtual Server Configuration area, click Configure virtual
| > server settings.
| > c. On the Virtual Server List tab, click the virtual server that you
have
| > to add the excluded paths to.
| > d. Under Virtual Server Management, click Define Managed Paths.
| > e. In the Add a New Path section, type the path to exclude in the Path
| > box.
| > f. Click Excluded Path, and then click OK.
| > g. Repeat steps 4 through 6 for each folder that you want to exclude.
| >
| > You receive a "Page not found" error message when you use Outlook Web
| > Access (OWA) to browse the Exchange Server 2003 client after you
install
| > Windows SharePoint Services
| > http://support.microsoft.com/?id=823265
| >
| > III. This behavior may occur if you try to connect to a Exchange
computer
| > that is behind a reverse proxy server.
| > Please try to access the OWA from SBS itself, do you get the same issue?
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > kindly help me collect some information for further investigation:
| >
| > 1. Does this issue happen on all users or just the particular user?
| >
| > 2. Please try to access the OWA from another computer, or access from
SBS,
| > does the issue happen again?
| >
| > 3. Please capture screenshots on the error page and send the pictures
to me
| > at v-terliu@xxxxxxxxxxxxx
| >
| > 4. Gather IIS log:
| >
| > a. Open IIS snap-in.
| >
| > b. Right click Default Web Site and click Properties.
| >
| > c. Uncheck the "Enable Logging" box and click Apply.
| >
| > d. Go to C:\WINDOWS\system32\LogFiles\W3SVC1 folder and move all files
to a
| > backup location.
| >
| > e. Check "Enable Logging" box and click OK.
| >
| > f. Run IISReset command.
| >
| > g. Reproduce the problem and send the log file in
| > C:\WINDOWS\system32\LogFiles\W3SVC1 folder to me for research.
| >
| > 5. Gather IIS Metabase:
| >
| > 1) Download the IIS Resource Kit tools from the following page:
| >
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
| > B628-ADE629C89499&displaylang=en
| >
| > 2) Install it, run MBExplorer (Metabase Explorer)
| >
| > 3) Right click the "LM" node and choose "Export to file".
| >
| > 4) Specify a file name, specify the password and finish the export.
| >
| > 5) Send the file and the password to v-terliu@xxxxxxxxxxxxx
| >
| > Hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: OWA Not working Page not Found
| > | thread-index: AcfP2zbrOnKidArTT8y38n/0dqRm6w==
| > | X-WBNR-Posting-Host: 207.46.19.168
| > | From: =?Utf-8?B?QnJlbnQgS2VubmVkeQ==?= <Brent
| > Kennedy@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: OWA Not working Page not Found
| > | Date: Thu, 26 Jul 2007 16:18:02 -0700
| > | Lines: 25
| > | Message-ID: <C0932DA4-BDC3-48B1-A277-27B1E171ED07@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:52740
| > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Currently using SBS 2003(sp2) with exchange(sp2), sql(sp4),
| > sharepoint(sp2)
| > | and IIS installed. The local domain is DIA.local and the external
domain
| > is
| > | somedomain.com.
| > |
| > | When i login as test@xxxxxxxxx or just test, owa logs in, has the
frames
| > | page built, but both frames say "page not found".
| > |
| > | Its the same way if i try to login with DIA.local\test or if i set
the
| > | exchange virtual directory to default to "\".
| > |
| > | I have tried to:
| > | -Recreate the default website
| > | -Recreate the OWA site using a ms KB, it was rebuilt, but still no
change.
| > | -Rerun the CICW
| > | -Verified that the accounts are defaulted to (bolded)
| > "test@xxxxxxxxxxxxxx"
| > | in active directory.
| > |
| > | It seems like something in IIS or exchange is not jiving. I setup a
| > virutal
| > | server with sbs installed and it works fine with this configuration..
so
| > | something was done on this server that is preventing this from
working.
| > |
| > | For some reason the OWA on this box doesn't seem to work properly.
| > |
| > | Thanks for any help.
| > |
| > |
| >
| >
|

.