Hi, We have an Exchange 2003 Active, Active, Passive cluster with 2 virtual servers and intermittently all users on one of virtual servers don't receive updates on their mobile devices from activesync. The users can successfully use outlook, and also OWA from IE (but not from chrome, safari, firefox). The users using OWA from non IE get page cannot be displayed on the inbox plane, but can browse the other folders. Doing an IISRESET doesn't solve it, but stopping the services on the node and restarting them sorts it until the next time. The RPC latency is 4ms, there are no disk queues to speak of and epoxy DAV queue lengths are 0. Any ideas where I can troubleshoot rather than restarting the node.

Hello, Try accessing https://localhost/Microsoft-Server-ActiveSync in IE on the problematic node. Please also check: 1. Any error event ID about ActiveSync in the application log. 2. IIS log about the activesync error code Thanks, Simon

Nothing in the application log however HTTPERR log lots of connection refused

Seems like you're having memory issues and exhuausting your NPP memory. Use the article below to determine if this is the case and setup perfmon to capture memory stats. What does Connections_Refused Mean? According to KB 820729, Connections_Refused means that the "Kernel Non Paged Pool memory has dropped below 20MB and HTTP.SYS has stopped receiving new connections". What all this means in English is this: On Windows NT systems, there are many types of memory with different properties. Kernel Non Paged Pool (NPP) memory is one such type, and the important thing to know is that on x86 machines, the size of this memory is fixed and has a maximum size of 128MB. In other words, you may have an x86 machine with 4GB of RAM, but if you only use 128MB and that 128MB all comes from NPP memory, your system is still "out of memory" regardless of how much is actually in use. [1/4/2006 - Correction - maximum size on x86 is "around 250MB" and 128MB with /3GB. For Windows Vista, it will be bounded by physical RAM and not arbitrary limit.] HTTP.SYS, being a kernel-mode driver, uses NPP memory for every single connection that is active, and we made a conscious decision to have it stop accepting connections when NPP memory falls below a threshold, arbitrarily set at 20MB. This is reasonable because lots of bad things can occur if NPP memory is depleted HOWTO: Diagnose IIS6 failing to accept connections due to Connections_Refused http://blogs.msdn.com/b/david.wang/archive/2005/09/21/howto-diagnose-iis6-failing-to-accept-connections-due-to-connections-refused.aspxJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com