The HIP service repeatedly logs Event 803 error messages when the HIP service receives a TCP/IP packet that does not contain any recognizable data in Host Integration Server 2004

A Microsoft Host Integration Server 2004 Transaction Integrator (TI) host-initiated processing (HIP) service listens for incoming requests from a host application over the TCP/IP port. The TCP/IP port is configured in the local environment (LE) that was created in TI Manager. As soon as a socket connection is established over the configured listening port, the HIP service tries to process the data that is included in the incoming TCP/IP packet.

If the HIP service determines that the data that is contained in the TCP/IP packet is not valid, the HIP service logs an error message.

For example, the following scenario has been reported. An HIP service listens for incoming requests from an application. The application runs on an IBM iSeries (AS/400) system. In this scenario, the HIP service repeatedly logs the following error message: This Event 803 error is logged because the HIP service receives incoming requests from a load balancing solution, and this load balancing system continually polls the port that the HIP service was listening on. The incoming TCP/IP packet does not contain any recognizable data. Therefore, the HIP service correctly logs the Event 803 error message to indicate that it has received invalid data that cannot not be processed.

A software update is available for the HIP service that lets you use a registry entry to control the frequency of the Event 803 error messages. You can use this software update to prevent the event log from being filled by Event 803 error messages. This behavior may occur in certain environments, such as the environment that is described in the "Introduction" section. In these environments, "invalid" data comes from an application that tries to verify that the listening port for the HIP service is available.

This software update only applies to the following HIP host environment (HE) types:

�	Enhanced listener message (ELM)
�	Transaction request message (TRM)

The software update does not apply when you use one of the following HE types:

�	Endpoint
�	Data

After you apply this software update, follow these steps to enable the new frequency setting:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate the following subkey in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar\Defaults
3.	Right-click Defaults, point to New, and then click Key.
4.	Type IgnoreDroppedCalls, and then press ENTER.
5.	Right-click IgnoreDroppedCalls, point to New, and then click DWORD Value.
6.	Type ReportingFrequency, and then press ENTER.
7.	Double-click ReportingFrequency, type the Event 803 reporting frequency that you want in the Value data box, and then click OK. Note By default, Hexadecimal is selected for the Base value. If you want to enter the value in decimal, click Decimal.
8.	Close Registry Editor.
9.	Stop and then restart the HIP Listener to enable the registry entry.

The valid range for the ReportingFrequency registry value is listed in the following table.

Minimum value (decimal)	Minimum value (hexadecimal)	Maximum value (decimal)	Maximum value (hexidecimal)
100	2147483647	64	FFFFFFFF

After you apply this software update and set the registry entries, the following behavior will occur:

�	The HIP service logs an Event 803 error message the first time that it receives invalid data after the TCP/IP socket is opened.
�	Then, the HIP service logs an Event 803 error message every ReportingFrequency interval.

For example, if you use the minimum value of 100, the following behavior occurs:

�	The first time that the HIP service receives an incoming TCP/IP package that has invalid data, an Event 803 error message is logged.
�	After every 100 TCP/IP packets that have invalid data, an Event 803 error message is logged.

This process repeats every time that the HIP service starts.

Important If you configure the ReportingFrequency registry entry to use a large value, you may experience delayed logging of Event 803 errors messages that actually represent a real problem. Therefore, use caution when you implement this functionality.

Software update information

A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Host Integration Server 2004 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time	Platform	Service pack requirement
Flowcontrol.dll	6.0.2022.0	72,192	31-Mar-2006	21:31	x86	SP1
Hipproxy.dll	6.0.2022.0	30,720	31-Mar-2006	21:31	x86	SP1
Hipservice.exe	6.0.2022.0	47,104	31-Mar-2006	21:31	x86	SP1
Tianchor.dll	6.0.2022.0	45,056	31-Mar-2006	21:31	x86	SP1

Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.