RE: no OWA
- From: Younger88 <Younger88@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 May 2008 12:13:00 -0700
Hi Terence
I have checked the permission on the directories you gave me and modified
the authenication and access Control options . The only folder that didnt
have the correct permissions was the "inetpub" folder. The Inetpub folder
didnt have the Authenticated Users added.
We have made progress. I can now browse to the Company Web
(https://servername/) internally and externally!! But i get a error when
trying to access OWA and OMA. When i try and access
https://servername/exchange i get this error:
440 Login Timeout
When i try and access the OMA i get the following error:
"Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange Server
2003. Currently your mailbox is stored on an older version of Exchange
server. Please contact your system administrator for additional assistance."
do you have any suggestions?
Many thanks again
Brian
"Younger88" wrote:
Hi Terence.
thank you for your reply. I will try this later.
Please can you tell me what ASP.NET version the virtual directories or the
defualt website should be running?
thanks
"Terence Liu [MSFT]" wrote:
Hello Brian,
Thank you for your email.
After analyze your metabase and screenshoots, I suggest we try the
following steps:
1. Correct the settings in IIS:
a. Open IIS on SBS
b. Right click Default Web Site, select properties
c. Select Home Directory tab, select "DefaultAppPool" in the Application
pool box.
d. Select Directory Security tab, click Edit button under Authentication
and access control
e. Tick Integrated Windows authentication option.
f. Click OK twice,
g. In the Inheritance Overrides window, click OK directly.
h. Run command iisreset to reset IIS.
Then, test this issue.
2. Grant the Authenticated Users group a minimum of Read and Execute
permissions, Read permissions, and List Folder Contents permissions on the
appropriate Exchange and Microsoft Windows directories. To assign the
correct permissions, follow these steps:
a. In Windows Explorer, locate and right-click the Exchsrvr\Exchweb
folder, and then click Properties.
b. Click the Security tab, and then make sure that the Authenticated Users
group has the following permissions:
Read and Execute
List Folder Contents
Read
c. Verify that the system account has the Full Control permission on the
Exchweb directory.
d. Repeat step a through step c for the following directories:
Windows\System32
Windows \System32\Inetsrv
Windows \System32\Wbem
Exchsrvr\Bin
Exchsrvr\RES
C:\Inetpub
Note: You may have to restart the World Wide Web Publishing service for
these settings to take effect.
3. Do you run any 3rd-party web server on SBS? Please try to do clean boot
on SBS to isolate 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.
g. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
1. Gather the IIS log and Metabase again and send to me.
2. Gather MPS network report on SBS:
a. Download MPSrepot_network from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE
b. Run MPSRPT_NETWORK.exe.
c. The tool will automatically collect the information. This procedure will
take 10~15 minutes.
d. Open Windows Explorer, navigate to the folder:
%SystemRoot%\MPSReports\Network\Reports\Cab\
e. Send the .cab file directly to me at v-terliu@xxxxxxxxxxxxx
I 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: no OWA
| thread-index: Aciw/HoSwYbKndcPRySNuf9zgz02iw==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?WW91bmdlcjg4?= <Younger88@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <251824BC-D3A7-4432-8549-AE682D0D73A9@xxxxxxxxxxxxx>
<oNlSkbzrIHA.1788@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: no OWA
| Date: Thu, 8 May 2008 04:13:00 -0700
| Lines: 292
| Message-ID: <DEA001FF-A797-4786-B361-F8FAB5639761@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.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:106771
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi Terence,
|
| thank you so much for the compresensive reply. It was very easy to
follow.
| However this solution didnt seem to work. I still cannot get access to
the
| OWA.
|
| the answers to your following questions:
| >1. Can you access OMA from internal clients?
| > no, i get the following error:
| "Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange
Server
| 2003. Currently your mailbox is stored on an older version of Exchange
| server. Please contact your system administrator for additional
assistance."
|
| > 2. Can you access RWW or companyweb from internal clients?
| > no, i get this error in IE:
| You are not authorized to view this page. HTTP Error 401.1. Unauthorized:
| Access is denied due to invalid credentials.
| Internet Information Services (IIS)
|
| > 3. Please capture screenshots on the error page when you try to access
OWA
| > from internal clients and send the pictures to me at
v-terliu@xxxxxxxxxxxxx
| > sent a document with print screen of errors to you email address
|
| > 4. Gather IIS log:
| > Will be attached in the email i send to your email address
|
| > 5. Gather IIS Metabase:
| Will be attached in the email i send to your email address
|
| Many thanks for your time and knowledge on this matter.
|
| Many thanks
|
|
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Customer,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that you unable to access
OWA
| > after you migrate the SBS 2000 to SBS 2003 sp1. If I have misunderstood
the
| > problem, please don't hesitate to let me know.
| >
| > Based on my research, I think the OWA virtual directory in IIS may be
| > corrupted when the migration. I suggest we try the following steps to
reset
| > the OWA virtual directory to see if we can resolve this issue:
| >
| > To delete and to re-create the virtual directories for Outlook Web
Access,
| > use one of the following method:
| >
| > 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.
- Follow-Ups:
- RE: no OWA
- From: Terence Liu [MSFT]
- RE: no OWA
- References:
- no OWA
- From: Younger88
- RE: no OWA
- From: Terence Liu [MSFT]
- RE: no OWA
- From: Younger88
- RE: no OWA
- From: Terence Liu [MSFT]
- RE: no OWA
- From: Younger88
- no OWA
- Prev by Date: Moving from test lab to production, will Change IP Address tool do it all?
- Next by Date: Re: Remote server Backups
- Previous by thread: RE: no OWA
- Next by thread: RE: no OWA
- Index(es):