Solved

Outlook Anywhere Problem - Mailbox Logon Latency Failure

Posted on 2013-12-19
5
482 Views
Last Modified: 2014-08-06
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
Comment
Question by:HoricePlant
  • 4
5 Comments
 
LVL 9

Expert Comment

by:Sean
ID: 39729486
make sure all your services on the CAS server are started. Are you using load balancing of any kind?
0
 

Author Comment

by:HoricePlant
ID: 39729523
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
 

Author Comment

by:HoricePlant
ID: 39754210
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
 

Accepted Solution

by:
HoricePlant earned 0 total points
ID: 40235767
Issue resolved by reinstalling CAS role.
0
 

Author Closing Comment

by:HoricePlant
ID: 40243213
I would have liked to have gotten to the bottom of the issue, but ran out of time.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Suggested Solutions

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Distribution Group 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 Recipients >>…
To show how to create a transport rule 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 >> Rules tab.:  To cr…

713 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