Re: Single user unable to access OWA
- From: APS <AndyS@xxxxxxxxxxxxx>
- Date: Fri, 14 Dec 2007 03:08:00 -0800
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 rights.
--------------------
<Thread-Topic: Single user unable to access OWA
<thread-index: Acg8pVcpeCUYzSc+Sp60Gg50FgkA/Q==
<X-WBNR-Posting-Host: 207.46.19.168
<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>
<Subject: Re: Single user unable to access OWA
<Date: Wed, 12 Dec 2007 01:57:00 -0800
<Lines: 252
<Message-ID: <FA6A9EDF-BD8D-4DA4-8A77-07F97D670449@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:1359
<NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
<X-Tomcat-NG: microsoft.public.backoffice.smallbiz
<
<Robert,
<
<Thanks for the response.
<
<Step 1: no existing passwords on any of the remote machines in question.
<Step 2: tested on multiple remote machines with lots of different setups,
so
<don't see it is likely to be a conflict unless with a MS core product.
<However, will ask user to try this on one remote machine
<Step 3: Will suggest user tries this on remote machine
<Step 4: No SP2 on SBS
<
<Will ask User to grab a screen dump of the remote OWA failure and prepare
<for MPS report. May take a while.
<Thanks for you help
<
<Andy
<
<
<
<
<"Robert Li [MSFT]" wrote:
<
<> Hi Anky,
<>
<> Thanks for posting in our newsgroup.
<>
<> Based on my research on this issue, please take the following steps to
<> narrow down this issue:
<>
<> Step 1: The problem may be caused by the order password stored on the
<> computer, please try the following on the problematic computer:
<>
<> 1. Open Control Panel. Double click User Account.
<> 2. On the Advanced tab, click Manage Passwords.
<> 3. Remove the existing passwords and click OK.
<> 4. Monitoring to see if the problem is resolved.
<>
<> Step 2: Please 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.
<>
<> Step 3:This may be caused by IE Brower. Please take the following steps
to
<> reset IE.
<> If you use IE 7, please take the steps in the following article:
<> How to use Reset Internet Explorer Settings (RIES)
<> http://support.microsoft.com/kb/923737
<> If you use IE 6:
<> 1. Click Tools' Internet Options.
<> 2. On the General tab, click to delete history, cookie and temporary
files.
<> Step 4: After you installed Windows 2003 SP2 on SBS server, it may cause
<> network problem, please Disable Receive Side Scaling and offloading
support.
<>
<> To disable Receive Side Scaling:
<>
<> 1. Click Start, click Run, type ncpa.cpl, and then click OK.
<> 2. Right-click a network adapter object, and then click Properties.
<> 3. Click Configure, and then click the Advanced tab.
<> 4. In the Property list, click Receive Side Scaling, click Disable in
the
<> Value list, and then click OK.
<>
<> To disable offloading support
<>
<> 1. Click Start, click Run, type regedit, and then click OK.
<> 2. Locate and then click the following registry subkey:
<> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
<> 3. In the details pane, right-click EnableTCPA, and then click Modify.
<> 4. In the Value data box, type 0 (zero), and then click OK.
<> 5. Exit Registry Editor.
<> 6. Restart the computer.
<>
<> More info:
<> You may experience network-related problems after you install Windows
<> Server 2003 SP2 or the Scalable Networking Pack on a Windows Small
Business
<> Server 2003-based computer
<> http://support.microsoft.com/kb/936594
<>
<> If the problem persists , please help me collect the following
information
<> for deep research:
<>
<> 1. The screen shot of the error message when accessing OWA.
<>
<> 2.MPS Report
<>
<> 1) Download MPS report tool from:
<>
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
<> 15706/MPSRPT_SETUPPerf.EXE
<> 2) Run the MPSRPT_SETUPPerf.exe on the server box.
<> 3) Wait for 10~15 minutes.
<> 4) Open Windows explorer, navigate to
<> %SYSTEMROOT%\MPSReports\Setup\Reports\cab\
<> 5) Send the .cab file to v-robeli@xxxxxxxxxxxxx with subject: Single
user
<> unable to access OWA.
<>
<> 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: Acg75fPkeie/kDEBTquCCtb+l5q+Fw==
<> <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>
<> <Subject: Re: Single user unable to access OWA
<> <Date: Tue, 11 Dec 2007 03:07:00 -0800
<> <Lines: 69
- Follow-Ups:
- Re: Single user unable to access OWA
- From: APS
- Re: Single user unable to access OWA
- 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
- Prev by Date: Re: Single user unable to access OWA
- Next by Date: michael lalonde
- Previous by thread: Re: Single user unable to access OWA
- Next by thread: Re: Single user unable to access OWA
- Index(es):
Relevant Pages
|