Technology Feed
Twitter
Tuesday, 18 November 2008
A regular occurrence in our Exchange 2007 Server has been Event ID 1040 with Source MSExchange ActiveSync, the event appears approximately every fifteen minutes.
The event tells us:
Event Type: Warning
Event Source: MSExchange ActiveSync
Event Category: Requests
Event ID: 1040
Description:
The average of the most recent [89] heartbeat intervals used by clients is less than or equal to [540].
Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and Direct Push technology. Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed.
The event details recommends visiting Microsoft Help and Support specifically http://support.microsoft.com/?&kbid=905013 which explains the issue may be firewall related, in particular “…firewall has not been configured to let HTTP(S) requests live longer than the minimum heartbeat interval“. The default setting is 9 minutes (540 seconds).
To address this we upped our firewall timeout for this particular connection to 30 minutes however the problem still occurred. We are currently working with our firewall vendor on this issue and will keep you posted.
Related
- Mobile ActiveSync and Microsoft Exchange 2007
- A solution for SSL Certificates and ActiveSync problems
- Windows Mobile 6 and Exchange Server Settings
- Dealing with Event ID 1000 UserEnv
- Exchange 2007 Event 8207 MSExchangeFBPublish Finally Fixed
any update on this issue, i am having same problem?
No update yet – our firewall provider have looked into the problem twice but have yet to identify any particular issue. The last thing they told me they needed the roaming users to initiate syncs and wait for time-outs at specified times – this isn’t really practical as our field users rarely have a few hours spare.
I started getting this issue 11/29. Please keep me appraised as well.
We are getting the same message, please hold me update if you find a solution to this.
[...] to the previous article: Dealing with Event ID 1040 MS Exchange ActiveSync we are still experiencing this problem. Apparently the only port required for Direct Push to work [...]