Re: Single user unable to access OWA
- From: "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com>
- Date: Wed, 19 Dec 2007 11:40:00 -0500
Thanks Andy. Sometimes a reboot fixes things that should not be broken.
:-)
--
Larry
"APS" <AndyS@xxxxxxxxxxxxx> wrote in message
news:CA62647F-5EFA-4E6C-AD0C-3499C5D188F6@xxxxxxxxxxxxxxxx
Lary,
Not sure if there was a fix. Robert helped rule out a lot of options and
I
tried to troubleshoot further, but ultimately the problem seems to have
been
resolved either by using the internal net to logon or due an SBS reboot
yesterday (the MS December updates were applied). Not sure if it is
relevant
but I got an application error ID 1001 "fault bucket" following the reboot
and an Application Error 1000 "faulting appliation RPCServ.exe module
ntdll.dll" on reboot. Have to add that I have had these before after MS
update reboots. Last night the user was able to access OWA via the
https://fqdn/exchange route just as in the past.
Sorry not to be more specific.
Andy
"Larry Struckmeyer" wrote:
So, can someone please share the fix?
--
Larry
"APS" <AndyS@xxxxxxxxxxxxx> wrote in message
news:8A2B5CF3-4975-4D51-BDEC-8156C8BD61AF@xxxxxxxxxxxxxxxx
Robert,
User was able to access OWA remotely last night, via
https://fqdn/exchange.
So problem is solved. Thanks for your assistance with the
troubleshooting.
Andy
"v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li" wrote:
Hi Andy,
Thanks for your reply.
Do the user logon OWA from external with the same machine as in LAN?
If
the
machines are different, please ensure you clear password cache on this
computer too.
You can also make a clean boot to make sure the problem is not caused
third
party software:
1. Click Start->Run...->type msconfig and press Enter.
2. Click Services tab and select Hide All Microsoft Services and
Disable
All third party Services.
3. Click Startup tab and Disable All startup items.
4. Click OK and choose Restart.
5. After reboot, check whether the problem still occurs.
6. 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.
Hope this helps.
I am looking forward to hear from you.
If you need further assistance, please don't hesitate to let me know.
Best regards,
Robert Li(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: Single user unable to access OWA
<thread-index: AchBW3+GANbhe8cFSpKMcYmzHzsswA==
<X-WBNR-Posting-Host: 207.46.192.207
<From: =?Utf-8?B?QVBT?= <AndyS@xxxxxxxxxxxxx>
<References: <A4C3E94D-6DFD-4D93-BF37-E3085FCF95F8@xxxxxxxxxxxxx>
<uhGzFS#OIHA.1184@xxxxxxxxxxxxxxxxxxxx>
<7EBA7BEE-85A5-487A-9B4F-641D7BB6D7BD@xxxxxxxxxxxxx>
<AebHy2JPIHA.360@xxxxxxxxxxxxxxxxxxxxxx>
<FA6A9EDF-BD8D-4DA4-8A77-07F97D670449@xxxxxxxxxxxxx>
<yTKuI7SPIHA.5204@xxxxxxxxxxxxxxxxxxxxxx>
<867B7905-FE00-4123-AF97-A023A1AC9817@xxxxxxxxxxxxx>
<Subject: Re: Single user unable to access OWA
<Date: Tue, 18 Dec 2007 01:51:01 -0800
<Lines: 316
<Message-ID: <B7262E87-1310-4713-9A15-438D08FA8E89@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.backoffice.smallbiz
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.backoffice.smallbiz:1370
<NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
<X-Tomcat-NG: microsoft.public.backoffice.smallbiz
<
<Robert,
<
<External login to OWA fails once beyond the ADSL router (CISCO) for
this
<user still. The user accesses https://fqdn/exchange and gets a
<https://fqdn/Remote/logon.aspx page "The username or password is
incorrect.
<Verify that CAPS LOCK is not on....."
<
<Can't workout why any logon traversing the router should be seen
differently
<on the SBS from one originating from a LAN port on the router.
<
<Will ask user to change password, just in case this solves issue.
<
<Andy
<
<"APS" wrote:
<
<> Robert,
<>
<> Thanks for the further hints. The user has returned to the office
today
<> giving me the opportunity to test his ability to logon to OWA from
the
LAN
<> before trying any of your recommended solutions. He was able to
access
OWA
<> via the link on Companyweb and via http://SERVER/exchange. I then
attached a
<> laptop to a switch ont he external network of the SBS. Accessing
OWA
via the
<> https://FQDN/exchange was also successful. This suggests that
everything is
<> operative.
<>
<> I hope this means that logging on via the LAN has cleared any
possible
<> issues with SBS/OWA: the user will check tonight from a remote
site.
Will
<> report back next week.
<>
<> Thanks for your support.
<>
<> Andy
<>
<> "Robert Li [MSFT]" wrote:
<>
<> > Hi Andy,
<> >
<> > Thanks for your reply.
<> >
<> > Since only one user can't access OWA, the issue may be caused by
user
<> > permission or Exchange Attribute. Based on my experience, I'd
like
to
give
<> > you the following suggestion:
<> >
<> > Step 1: The issue may be caused by incorrect user permission
settings.
<> > Please run the change user permission wizard and try again.
<> >
<> > Note: I assume this user is domain user.
<> >
<> > 1. Open Server Management and click Users.
<> > 2. Click Change User Permission and then click Next.
<> > 3. Click User Template and Replace any previous permissions
granted
to
the
<> > users. Click Next.
<> > 4. Click problematic user account, click Add,
<> > 5. Click Next and then click Finish.
<> >
<> > Step 2: The issue may be related to corrupt Exchange attribute,
you
can
<> > follow steps below to reset its Exchange attributes.
<> >
<> > 1. In Outlook, Export all mails in Mailbox as .PST file.
<> >
<> > Please follow the instruction below to export all mails in the
mailbox
as
<> > .PST file.
<> >
<> > 287070 OL2002: How to Back Up, Restore, or Move Outlook Data
<> > http://support.microsoft.com/?id=287070
<> >
<> > 2. Remove the Exchange Attribute for problematic user with
corrupt
Exchange
<> > Attribute.
<> >
<> > 1) In Exchange 2003 computer, launch Active Directory Users and
Computers.
<> > 2) In the Users Container, right click the user with corrupt
attribute,
<> > click Exchange Task.
<> > 3) Click Remove Exchange Attribute and click Next to finish the
process.
<> >
<> > 3. Run Cleanup Agent
<> >
<> > 1) In Exchange 2003 computer, launch Exchange System Manager.
<> > 2) Expand the mailbox store where the problematic mailbox
located,
right
<> > click the mailboxes container, select Run Cleanup Agent.
<> > 3) Then you will see the problematic mailbox with a red X.
<> >
<> > 4. Create a new mailbox for the user.
<> >
<> > 1) In Exchange 2003 computer, launch Active Directory Users and
Computers.
<> > 2) In the Users Container, right click the user with corrupt
attribute,
<> > click Exchange Task.
<> > 3) Click Create a new Mailbox and select Mailbox Store for the
new
mailbox,
<> > click Next to finish the process.
<> >
<> > 5. After that, please follow article 287070 above to import the
PST
file in
<> > Outlook.
<> >
<> > How to manage .pst files in Outlook 2002 and in Outlook 2003
<> > http://support.microsoft.com/kb/287070
<> >
<> > If the problem persists, please help me collect the information I
requested.
<> >
<> > I am looking forward to hear from you.
<> >
<> > If you need further assistance, please don't hesitate to let me
know.
<> >
<> > Best regards,
<> >
<> > Robert Li(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
.
- References:
- Re: Single user unable to access OWA
- From: Larry Struckmeyer
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- From: Robert Li [MSFT]
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- From: Robert Li [MSFT]
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- From: v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li [MSFT])
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- From: Larry Struckmeyer
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- Prev by Date: Re: Single user unable to access OWA
- Next by Date: Re: owa and internal / external domain
- Previous by thread: Re: Single user unable to access OWA
- Next by thread: michael lalonde
- Index(es):
Relevant Pages
|
Loading
