BUG: The APPC DEACTIVATE_SESSION verb does not succeed and an AP_INVALID_SESSION_ID return code is returned

The APPC DEACTIVATE_SESSION verb may not succeed, and you may receive the following return codes:

• Primary return code: AP_PARAMETER_CHECK
• Secondary return code: AP_INVALID_SESSION_ID

This problem occurs regardless of whether the application is using the correct session ID as it was obtained from the original call to the ACTIVATE_SESSION verb.

This problem occurs because the Microsoft SNA Server service is incorrectly hard coded to expect the host system to send an 8-byte Session Instance Identifier in the BIND request. If BIND contains a Session Instance Identifier that is smaller than 8 bytes, the DEACTIVATE_SESSION verb does not succeed.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Host Integration Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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 tool in Control Panel.
Note Because of file dependencies, the most recent fix that contains the previous files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.

For more information about the format of the BIND request and the Session Instance Identifier structured data subfield, see the following IBM document: