To resolve these logo certification issues, apply this hotfix. For more information about the logo certification issues that are fixed by this hotfix, see the "More Information" section.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have Microsoft Host Integration Server 2010 installed to apply this hotfix.
Restart informationYou do not have to restart the computer after you apply this hotfix.
Replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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.
For Microsoft Host Integration Server 2010, 32-bit Edition
|File name||File version||File size||Date||Time||Platform|
For Microsoft Host Integration Server 2010, 64-bit Edition
|File name||File version||File size||Date||Time||Platform||Service branch|
Known Logo Certification issues
Test Case 1.1.1: All Primary Functionality tests and Certification test cases passThe SnaBase service (snabase.exe) does not function correctly in a mixed IPv4/IPv6 environment. This problem occurs if IPv6 support is enabled on a Host Integration Server system that is running on a network segment that is not enabled for IPv6. The SnaBase service may stop unexpectedly when this problem occurs. An event message that resembles the following may be logged in the Application event log when the SnaBase service stops:
Source: Application Error
Faulting application snabase.exe, version 8.5.4143.0, time stamp 0x4be78cea, faulting module SNAIP6.DLL, version 8.5.4143.0, time stamp 0x4be78ce9, exception code 0xc0000005, fault offset 0x000000000000df3e, process id 0xe64, application start time 0x01cb06fc21e60f74
By default, IPv6 support is not enabled in Host Integration Server 2010. Therefore, this problem does not occur under typical usage because. To enable support for IPv6 for the Network Integration (SNA Gateway) features in Host Integration Server 2010, follow these steps:
- Run the Host Integration Server 2010 Configuration Tool.
- Click Network Integration.
- Click the Advanced button.
- Select the TCP/IP v6 option under Client Protocol Support.
- Click Close.
- Click Apply Configuration.
- Click Next, and then click Finish to complete the configuration wizard and to apply the changes.
- Close the Configuration Tool.
Test Case 4.3.1: Does the application appropriately use Heaps, Locks, and Handles resources?
- The 3270 Client (win3270.exe) fails the handle usage test when it runs under Application Verifier. This problem occurs when the 3270 Client is being reconfigured. The problem does not cause issues during typical usage because the 3270 Client handles the errors that occur when the 3270 Client is being reconfigured.
- The Snalink.exe service that is used to load Host Integration Server link services fails the handle usage test when it runs under Application Verifier. This problem occurs when the Snalink service is being stopped. The problem does not cause issues during typical usage because the Snalink service handles the exception that occurs when the service is stopped.
- The 5250 Client (win5250.exe) fails the handle usage test when it runs under Application Verifier. This problem occurs when the 5250 Client is being reconfigured. The problem does not cause issues during typical usage because the 5250 Client handles the errors that occur when the 5250 Client is being reconfigured.
- The HIS LU62 Resync Service (resyncsvc.exe) fails the Heaps test when it runs under Application Verifier. This problem occurs when the Host Integration Server configuration has no Local APPC LUs configured for SyncPoint support. The following error is logged in the Application event log when the HIS LU62 Resync Service is started, and no Local APPC LUs are configured to support SyncPoint:Event ID: 1000
Source: Application Error
Faulting application name: resyncsvc.exe, version: 8.5.4224.0, time stamp: 0x4c6379e4
Faulting module name: resyncsvc.exe, version: 8.5.4224.0, time stamp: 0x4c6379e4
Exception code: 0xc0000005
Fault offset: 0x000000000000d45e
Faulting process id: <process ID>
Faulting application start time: <time>
Faulting application path: C:\Program Files\Microsoft Host Integration Server 2010\system\resyncsvc.exe
Faulting module path: C:\Program Files\Microsoft Host Integration Server 2010\system\resyncsvc.exe
- The TN3270 Service (tn3servr.exe) fails the Heaps test when it runs under Application Verifier. This problem occurs when the TN3270 Service is started before the SNA Service is configured by using SNA Manager or snacfg.exe. During typical usage, the following events are logged in the Application event log when the TN3270 Service is started before the SNA Service is configured:Event ID: 1021
Source: TN3270 Server
No port security records available – no ports configured
Event ID: 102
Source: TN3270 Server
TN3270E Service initialization completed by initialization error.
Test Case 4.3.2: Does the application correctly handle Exceptions, Memory, and TLS resource usage?The Host Print service (snaprint.exe) fails the Thread Local Storage (TLS) test when it runs under Application Verifier. This problem occurs when the Host Print service is being stopped. The problem does not cause issues during typical usage because the Host Print service handles the exception that occurs when the service is stopped.
Test Case 4.3.3: Does the application correctly handle Dirty Stacks or use Dangerous APIs?The SNA Server service (snaservr.exe) fails the Dirty Stacks and Dangerous APIs tests when it runs under Application Verifier. This problem occurs when the SNA Server service is being stopped. The problem does not cause issues during typical usage as the SNA Server service handles the exception that occurs when the service is stopped.
Article ID: 2427006 - Last Review: Jan 21, 2011 - Revision: 1