Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 585
  • Last Modified:

Outlook Anywhere Problem - Mailbox Logon Latency Failure

Hi,

We have Exchange 2010 (SP3 RU2) installed at two of our sites (single forest / domain). There are mailbox servers at both sites (let's call them site A and site B).

For users who's mailbox are at site B, Outlook Anywhere works fine. But not for users who's mailboxes are at site A. All other services appear fine (OWA, ECP, AS etc).

When I run MS Remote Connectivity Analyser for a site A user, it fails and reports RPC Proxy can't be pinged. If I run Test-OutlookConnectivity -protocol:http against the site A users mailbox (and use Get-Credentials), it fails on the last test...

RunspaceId                  : e0c7e2a2-feb6-427a-a6fc-7fbb670601b2
ServiceEndpoint             : UKSP-EXCAS01.AD.Local
Id                          : MailboxLogon
ClientAccessServer          : UKSP-EXCAHT02.ad.local
Scenario                    : Mailbox::Logon.
ScenarioDescription         :
PerformanceCounterName      : Mailbox: Logon latency
Result                      : Failure
Error                       :
UserName                    : <user>
StartTime                   : 19/12/2013 15:32:30
Latency                     : -00:00:00.0010000
EventType                   : Error
LatencyInMillisecondsString : -1.00
Identity                    :
IsValid                     : True

Does anyone know what this actually means (logon latency -1), and what to try next?

The same test for a site B user works fine.

Thanks in advance!
0
HoricePlant
Asked:
HoricePlant
  • 4
1 Solution
 
SeanSystem EngineerCommented:
make sure all your services on the CAS server are started. Are you using load balancing of any kind?
0
 
HoricePlantAuthor Commented:
Yep - all (relevant) services are running. We do have Kemp LoadMasters configured for load balancing the CAS servers at each site. Site B (that works), also uses the Edge Security Pack to deploy external services.

The LoadMaster at Site A (where OA doesn't work) is pure load balancing only.
0
 
HoricePlantAuthor Commented:
Hi, and Happy New Year to all...

I'm back at work, and still have this issue. Today. I've uninstalled and reinstalled the Client Access role on the server, but are still seeing the same problem. I don't believe this is down to the Kemp Loadmasters, and there are no errors on the Loadmasters logs.

It would seem to be a permission issue where users based at site A don't have permission to logon to a mailbox using http. Connecting using MAPI is fine.

Any more thoughts welcome!
0
 
HoricePlantAuthor Commented:
Issue resolved by reinstalling CAS role.
0
 
HoricePlantAuthor Commented:
I would have liked to have gotten to the bottom of the issue, but ran out of time.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now