Article ID: 256906
Article Last Modified on 6/24/2004
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 4.0, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 3.0 Service Pack 2, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 3.0 Service Pack 3, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 3.0 Service Pack 4, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 4.0, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 4.0 Service Pack 1, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 4.0 Service Pack 2, when used with:
- the hardware: Intel x86
- Microsoft SNA Server 4.0 Service Pack 3, when used with:
- the hardware: Intel x86
This article was previously published under Q256906
SYMPTOMS
During conversation startup for a Transaction Program (TP), SNA Server may fail unexpectedly with an Access Violation error message in the S1PROLU6 module.
If the Drwtsn32.exe file is installed as the default debugger on the computer running SNA Server, the following exception log may occur:
CAUSE
This problem can occur when a TP_ENDED(Hard) verb is issued for an invoked TP during conversation startup for the TP, which causes SNA Server to immediately clean up all internal resource structures allocated to the conversation.
If SNA Server is in the process of LU validation when this happens, then SNA Server tries to reference the resource structures allocated to the conversation, which now no longer exist, resulting in the Access Violation error message.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3.
This problem was first corrected in SNA Server 4.0 Service Pack 4.
Keywords: kbbug kbfix kbsna400presp4fix kbqfe kbsna400sp4fix KB256906