Outook 2010 with Exchange Server 2010 r2 hangs

[simonhind]

Hi

 

i am looking for a solution to outlook with exchange server

 

 

the technical stuff

 

everytime staff send New Email it hangs for 40 seconds to 5 minutes, it terribly slow and we don't know why

 

 

whats we've tried

we've enabled cache mode which resolves the lag, but the issue with this is its constantly asking for user credentials

which are correct but its not accepting the credentials and we know its correct

 

would appreciate some help on trying to resolve this for the school

Edited December 5, 2012 by simonhind

[glennda]

sounds like something is very wrong - are your Domain controllers ok?

 

anything major in the logs? are all the service urls configured correctly.

[simonhind]

The webapp is working fine, the mail exchange

 

Event logs show

 

MSExchange Availability : Event ID 4030

Process Microsoft.Exchange.InfoWorker.Common.Delayed`1[system.String]: Unable to find any replicas for free/busy folder

 

Process w3wp.exe () (PID=4560).

MSExchange ADAccess

Event ID : 2160

 

which we dont know how to fix

[glennda]

Do you use public folders?

 

What I mean by service urls - is under Server Configuration Client access (i think) - you have all the tabs for OWA, EAB, OAB etc. are these urls correct.

[simonhind]

yes all are correct, this has been going on for 2 weeks

 

but not all users are affected with "sending" new emails in outlook only some users outllook with hang for 40sec - 5mins

[glennda]

It seems to hint towards an issue with exchange communicating with your domain controllers (more specifically a global catalog) or just general communication.

 

Have you tried changing your configurational domain controller?

Edited December 5, 2012 by glennda

[sukh]

1. Post the 2080 event in the app log

2. Post all your URL's for all your services and Run the Test-Autoconfiguration from the client (Hold Ctrl and right click the Outlook icon) and follow instruction, untick the Guess options.

[techsup1983]

Hello. I would read about Exchange 2010 Server - ExPBA (Best Practice Analyzer) and give it a try.

 

Microsoft Exchange Server 2010 - ExBPA (Exchange Best Practice Analyzer)

 

Taken from the above link.

Health Check

The health check will warn you about any weaknesses on your Exchange server. Perhaps BPA's greatest strength is to alert you to those problems, which although not serious in themselves, will collectively slow down your server. Once ExBPA identifies an 'Issue', it gives you details, not only about the problem, but even better, on the solutions. Unless you have tried ExBPA, it's hard for me to put over just how many tests it can do, and therefore how much time ExBPA will save you in analyzing an Exchange Server's performance. In a word its - awesome.

Edited December 5, 2012 by techsup1983