• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1400
  • Last Modified:

Active Sync error 3033

Recently, we had a couple of our employees purchase the new iPhones. Since then, I have been seeing several of these events logged on the Exchange server:

Event Type:     Warning
Event Source:   Server ActiveSync
Event Category: None
Event ID:       3033
Date:           10/7/2008
Time:           6:28:05 AM
User:           HQ\rand
Computer:       HQMAIL05
Description:
The average of the most recent [200] 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.  For more information about how to configure firewall settings when using Exchange ActiveSync, see Microsoft Knowledge Base article 905013, "Enterprise Firewall Configuration for Exchange ActiveSync Direct Push Technology" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=905013).


I read that I need to change my settings with the ISA manager, but I'm not sure if it applies, since to my knowledge, I am not using ISA. I also saw here http://support.microsoft.com/kb/905013 that I could add registry values that might clear the issue, but I don't know if that would still apply to ISA settings. Their phones work, but I would like to get rid of the event.
0
numb3rs1x
Asked:
numb3rs1x
3 Solutions
 
ach_patilCommented:
I would suggest you try to make Registry changes.. It has worked for me in some previous instances.
Make sure you back up your registry before you do it.
0
 
numb3rs1xAuthor Commented:
I'm willing to do this, but it seems the values they want to have set in the registry would affect firewall settings or sync with firewall settings? What are the registry values actually changing? Am I even using what it is that they would change?
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
numb3rs1xAuthor Commented:
openBSD 4.3 pf firewall.
0
 
Jian An LimCommented:
well, i don't have much knowledge about that type of firewall.... but usually it is related to firewall
0
 
numb3rs1xAuthor Commented:
So what is it related to on the firewall? Is it some kind of adjustment I can make?
0
 
Jian An LimCommented:
look for heartbeat intervals  ? but does it give you any error like your mobile wont connect?
0
 
numb3rs1xAuthor Commented:
The mobile devices work fine. There isn't anything defined as a heartbeat on the BSD firewall that I'm aware of. The event is an annoyance I guess. I would like to get rid of it if it wouldn't be too much trouble.
0
 
Jian An LimCommented:
well, it is the heartbeat interval ... something to do with firewalls ....

and i am not BSD firewall expert ...

under this doco http://support.microsoft.com/kb/905013

The following table contains the values that can be modified as they relate to the heartbeat interval. These registry values are not present in a fresh installation of Exchange Server 2003 SP2. The server reverts to hard-coded defaults if these registry values are missing. The administrator must manually create these registry values if he or she wants to set the values. These values can be set in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MasSync\Parameters
Collapse this tableExpand this table
Name Data type Values Default Description
MinHeartbeatInterval DWORD 1 - MaxHearbeatInterval 60 seconds Minimum heartbeat interval
MaxHeartbeatInterval DWORD MinHeartbeatInterval -3540 2700 seconds (45 minutes) Maximum heartbeat interval
HbiSampleSize DWORD 1 or higher 200 samples Heartbeat interval sample size
HbiAlertThreshold DWORD 1 or higher 480 seconds Heartbeat interval alert threshold
Notes
In this table, the value "1 - MaxHearbeatInterval" indicates any value between 1 and the value of MaxHearbeatInterval. Also, the value "MinHeartbeatInterval -3540" indicates any value between the value of MinHeartbeatInterval and 3540.
If any one of these values is set in the registry, and the specified value falls outside the listed values for that parameter, initialization of Exchange ActiveSync will revert to the defaults. Additionally, an event is logged in the Application event log. However, an event is not logged in the Application event log if the value is set to zero. When a value is set to zero, the behavior is as if the value were absent. In other words, the hard-coded default is used.
Exchange ActiveSync reads these values one time at startup. Therefore, if an administrator decides to change the values, the IIS Admin Service must be restarted for the changes to take effect.
0
 
numb3rs1xAuthor Commented:
So in reading, I'm gathering that I would have to set my timeout intervals to more than 9 minutes on the firewall for port 443 to the Exchange server? They are set to 10 seconds by default. Am I looking at the right thing?
0
 
Jian An LimCommented:
according to article it says

Modify the Connection Timeout from the default 120 seconds (2 minutes) to 1800 seconds (30 minutes).
0
 
Jian An LimCommented:
it is a limitation on your firewall ... it do not mean i did not point out how to fix it ..
at least this should be keep, and point out it is a limitation on the firwall.


0
 
numb3rs1xAuthor Commented:
The firewall does not limit settings such as this. It is a fully configurable firewall with more functionality than most Cisco's. The problem is that nobody on this forum knows anything about it, and if I want to solve the problem, which isn't a critical problem in the first place, I would have to find someone who knows how this setting relates to the openBSD firewall.
0
 
lrmooreCommented:
From what I can understand on the links to the Microsoft KB article, these registry changes should be made on the Exchange server, not on the firewall.  
0
 
numb3rs1xAuthor Commented:
I saw that when I first opened this ticket. I guess I was hoping that I could avoid creating these entries since it makes me squeamish to make so many changes to the registry. The folder containing the folder to the four parameters isn't even there. You guys can close this if there isn't anyone who knows how to do this from the frewall side. I'll adjust those registry settings if the events become more of a nuisance than they are right now. Thanks though.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

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