WAPPC32 Ignores User ID Provided By APPC App On Consecutive Allocate Requests

ID: Q218165

The information in this article applies to:

Microsoft SNA Server, versions 3.0SP3, 4.0, 4.0SP1, 4.0SP2

SYMPTOMS

If the host supports LU6.2 persistent verification or already verified security, and an APPC application calls TP_STARTED once, followed by multiple [MC_]ALLOCATE requests for consecutive conversations, the User ID provided in subsequent [MC_]ALLOCATE requests may be ignored, causing the persistent verification session to be used.

However, if the APPC application issues a new TP_STARTED for every [MC_]ALLOCATE request, this problem does not occur.

CAUSE

The Wappc32.dll file was failing to clear the user_id field on subsequent allocation requests (where security=AP_SAME) made over an LU6.2 session that supports persistent verification or already verified security.

RESOLUTION

SNA Server 3.0

To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:

Q184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack

SNA Server 4.0

File name	Date	Time
Wappc32.dll	xx/xx/xx	xx:xx

NOTE: Date and time information will be provided as soon as it becomes available.

NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0 SP3, SNA Server 4.0, 4.0 SP1, 4.0 SP2. This problem was first corrected in SNA Server 3.0 Service Pack 4.

MORE INFORMATION

APPC applications which call TP_STARTED before every [MC_]ALLOCATE will not encounter this problem.

This problem occurs in the following conditions:

The LU6.2 session supports either "persistent verification" or "already verified" security.

The APPC application must call TP_STARTED once, followed by consecutive [MC_]ALLOCATE requests, with security = AP_SAME and a user_id and password is specified.

The SNA Server APPC API and message traces will reveal the following behavior. In this case, the APPC application issues three consecutive MC_ALLOCATE requests with security=AP_SAME along with userID and password on a session that supports persistent verification. But, the Wappc32.dll file appears to resend the initial user ID over and over, ignoring the user ID provided by the application:

APPC app issues MC_ALLOCATE, sends userid = WNW039, password = WHYNOT1, FMH-5 includes userid = WNW039, password = WHYNOT1

APPC app issues MC_ALLOCATE, sends userid = WNWXXX, password = YYYY, FMH-5 includes userid = WNW039, password = YYYY

APPC app issues MC_ALLOCATE, sends userid = XXXX, password = ZZZZZ, FMH-5 includes userid = WNW039, password = ZZZZZ

Note that the APPC DLL always sends the same user ID, ignoring the user ID provided in the verb control block by the application.

Additional query words:


Keywords          : 
Version           : WINDOWS:3.0SP3,4.0,4.0SP1,4.0SP2
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: July 8, 1999