Calling CONVERT before RECEIVE_ALLOCATE may lead to event 60
Article ID: 180229
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 4
- Microsoft Host Integration Server 2000 Standard Edition
- Microsoft Host Integration Server 2000 Service Pack 1
This article was previously published under Q180229
SYMPTOMS
If WinAPPCStartup() is not included at the beginning of a Windows-based
invokable transaction program, and if the TP first calls the CONVERT API,
the TP's call to RECEIVE_ALLOCATE may subsequently stop (hang) and not
complete.
CAUSE
By first calling the CONVERT API prior to calling RECEIVE_ALLOCATE, the SNA
client APPC interface was being confused, causing it to fail to properly
match the incoming attach request to the application's RECEIVE_ALLOCATE
call. If a Windows-based transaction program does not begin with
WinAPPCStartup(), SNA Server automatically calls WinAPPCStartup() when the
application calls the first APPC function. However, if this call is
preceded by a Common Service Verb function (such as CONVERT), this can
confuse the APPC interface.
WORKAROUND
The application can work around this problem by explicitly calling
WinAPPCStartup prior to calling any Common Service Verb functions.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it
becomes available.
Additional query words: APPC invokable TP WinAPPCStartup
Keywords: kbbug kbnofix KB180229