RE: OWA Login Problem

[Jenny wu [MSFT]]

Hi Stephen,

Thanks for using the SBS newsgroup.

From your description, I understand the issue to be: users can not login
the OWA site from internet with the error message "You could not be logged
on to Outlook Web Access. Ensure that your user name and password are
correct, and then try again." If I am off base, please don't hesitate to
let me know.

Let us follow below steps to trouble shoot the issue:

- Do you have Exchange 2003 SP1 installed?

- Does the issue happen in LAN? Please log on domain with a regular domain
user account, then try to logon OWA site using URL:
https://servername/exchange, what is the result?

- How you create domain users? Please try to add user account with Add User
Wizard and then test the issue, what is the result? If it fails, please add
the user account to the Administrators group and then test, does the issue
still occur?

- Is OWA enabled for the users? To verify this, go to Server Management,
Users, User Properties, Exchange Features and OWA under Protocols.

- Are the users restricted to log on to only specific workstations? To
check this, go to Server Management, Users, User Properties, Account and
Log on to. If it is set to "The following computers", change it to "All
computers" and have a try.

- If you disable Forms Based Authentication, does OWA works internally?

To disable Exchange Forms Based Authentication:

1. Open Exchange System Manager.
2. Expand Server, <server name>, Protocols, HTTP
3. Right-click Exchange Virtual Server, Properties. Settings tab.
4. Uncheck Enable Forms Based Authentication. Click OK.
5. Go to a command prompt, type "iisreset" and press ENTER.

- Do you have 831464 installed? After it is installed, make sure you clear
%windir%\IIS Temporary Compressed Files, IE cache as well as ISA cache if
you are using SBS 2003 premium.

Detailed steps:

1. Download and apply the 831464 update:

831464 FIX: IIS 6.0 Compression Corruption Causes Access Violations
http://support.microsoft.com/?id=831464

2. Clear the cached, compressed copy of the affected files on the SBS
server:

A. Clear the IIS server files:

*. Go to your %windows%\IIS Temporary Compressed Files directory
*. Select all of the content in this directory and delete it.

B. Go to a command prompt, type "iisreset".

3. If you have ISA installed on the SBS server, take the following steps to
clear the ISA cache.

A. Stop the Web Proxy service.
B. Locate the Urlcache folder.
C. From the multiple files in this folder, locate the *.cdat file in this
folder.
D. Delete the *.cdat file.
E. Start the Web Proxy service.

Related Knowledge Base article:

301471 How to Delete the Web Cache on Internet Security and Acceleration
Server
http://support.microsoft.com/?id=301471

4. You should also delete the cached files on the client to make sure that
the corrupted files from the cache are not used. To do so, follow these
steps:

A. In Internet Explorer, click Internet Options on the Tools menu .
B. Click the General tab, and then click Delete Files.
C. Click OK.

Hope above information helps! I am happy to be of assistance to you and
look forward to your reply.

Have a nice day!

Sincerely,

Jenny Wu
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 Login Problem
>thread-index: AcZR4NtQ3S7+x79qTiG569szIYggPQ==
>X-WBNR-Posting-Host: 71.14.47.130
>From: =?Utf-8?B?U3RlcGhlbiBHcm90ZQ==?=
<Stephe...@discussions.microsoft.com>
>Subject: OWA Login Problem
>Date: Mon, 27 Mar 2006 12:56:02 -0800
>Lines: 14
>Message-ID: <324CDD27-5C09-40EE...@microsoft.com>
>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.1830
>Newsgroups: microsoft.public.windows.server.sbs
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:256004
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I can access OWA (the opening page) over the Internet fine, but we keep
>getting an error message when anybody tries to login.
>
>We access OWA via: https://mail.domain.com/exchange and get the following
>message.
>
>"You could not be logged on to Outlook Web Access. Make sure your
>domain\user name and password are correct, and then try again."
>
>I know we have the correct login information... Any Ideas and any help is
>appreciated.
>
>--
>Stephen Grote
>

[markr...@yahoo.com]

Jenny,

I have the same problem with users accessing OWA.

They receive the following error message after entering their username
and password,"You could not be logged on to Outlook Web Access. Ensure
that your user name and password are orrect, and then try again."

I have created all users via the add user wizzard using the mobile user
template. They receive the message internally and externally when
attempting to access OWA. The only point I have found is if I add them
to the Domain Admins group - they are then able to access OWA
internally and externally successfully. I have not made any changes to
the install of SBS2003 - using most all of the defaults.

Any suggestions - I have been pulling my hair out for a few weeks.

Thanks for any suggestions...

Mark
(markr...@yahoo.com)

[Jenny wu [MSFT]]

Hi Mark,

Thanks for posting here.

From your description, I understand that you have similar problem with the
post. However different issues may have different root causes, I would like
to suggest that you create a new thread to post your question. 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.

And other partners who the newsgroups regularly can either share their
knowledge or learn from your interaction with us. Also, this is to make
sure that the responders can better track the problem. Thank you for your
understanding.

You can visit SBS newsgroup in the following link:

http://www.microsoft.com/technet/community/newsgroups/server/sbs.mspx

Have a nice day!

Sincerely,

--------------------
>From: markr...@yahoo.com
>Newsgroups: microsoft.public.windows.server.sbs
>Subject: Re: OWA Login Problem
>Date: 23 Apr 2006 17:51:23 -0700
>Organization: http://groups.google.com
>Lines: 184
>Message-ID: <1145839883.8...@g10g2000cwb.googlegroups.com>
>References: <324CDD27-5C09-40EE...@microsoft.com>
> <bO$hXrjUG...@TK2MSFTNGXA01.phx.gbl>
>NNTP-Posting-Host: 66.87.106.107
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1145839889 7419 127.0.0.1 (24 Apr 2006
00:51:29 GMT)
>X-Complaints-To: groups...@google.com
>NNTP-Posting-Date: Mon, 24 Apr 2006 00:51:29 +0000 (UTC)
>In-Reply-To: <bO$hXrjUG...@TK2MSFTNGXA01.phx.gbl>
>User-Agent: G2/0.2
>X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.1.4322; InfoPath.1),gzip(gfe),gzip(gfe)
>Complaints-To: groups...@google.com
>Injection-Info: g10g2000cwb.googlegroups.com; posting-host=66.87.106.107;
> posting-account=n23YUg0AAACiw6gc2H54hFRsPFk_YdzD
>Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed00
.sul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.
giganews.com!nntp.giganews.com!postnews.google.com!g10g2000cwb.googlegroups.
com!not-for-mail
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:262764
>X-Tomcat-NG: microsoft.public.windows.server.sbs