Solved

Exchange 2010 (SBS2011) , one user can't connect

Posted on 2015-02-03
1
432 Views
Last Modified: 2015-02-04
Just upgraded one site to SBS2011 a month ago, all seem ok, but yesterday, one user (out of 30) can't connect to the Exchange, Outlook 2007 just loops with 'Trying to retrieve', in the end, I reinstalled Office, reset the LAN, then after 30 mins, all worked again.
This morning, same thing happend, this time, I checked the  users OWA, and I get this :

An error occurred and your request couldn't be completed. If the problem continues, contact your helpdesk with this HTTP Status code: 500.

Request
Url: https://remote.xxxxxxxx.co.uk:443/owa/lang.owa
User host address: 81.xxx.164.xxx
User: Paul Xxxx
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Paul Xxxx
SMTP Address: paul@xxxx.co.uk
OWA version: 14.1.218.13

Exception
Exception type: System.Web.HttpException
Exception message: Request timed out.

Call stack
No callstack available

So I know the problem is from the Exchange rather than local.
Looking at the EV, I can't see anything wrong.
All the other users seem to work fine, if I OWA to all other users, they all connect first time, I tried to restart the Exchange Form Based Authentication, it made the login screen slightly faster but same error for this user.

Any experts know what can cause this ? or know how to fix it ?
Many thanks
0
Comment
Question by:Combemartin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 3

Accepted Solution

by:
Sudhir Bidye earned 500 total points
ID: 40585962
-Try configuring outlook profile for the same user on any other user workstation and confirm if you are facing the same issue on other workstation.
-If yes, then run New-MailboxRepairRequest command with -detectonly switch for this mailbox and check if it reports any corruption.

If it reports any corruption then you may need to fix it by new-mailboxrepairrequest command.

-You can also create a new mailbox database and  try moving that mailbox to the newly created mailbox.
0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question