KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q256906: SNA Server Fails Unexpectedly with Access Violation in S1PROLU6

Article: Q256906
Product(s): Microsoft SNA Server
Version(s): WINDOWS: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
Operating System(s): 
Keyword(s): kbsna300sp1 kbsna300sp2 kbsna300sp3 kbsna300sp4 sna4 kbsna400sp1 kbsna400sp2 kbsna400sp
Last Modified: 15-JUN-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- 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, on platform(s):
   - the hardware: Intel x86 
-------------------------------------------------------------------------------

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:

  Application exception occurred:
  App: obj\i386\snaservr.exe (pid=283)
  When: 2/23/2000 @ 15:22:55.937
  Exception number: c0000005 (access violation)
  function: s1prolu6
  010350e9 668b4010 mov ax,[eax+0x10] ds:019fea07=????
  010350ed 8d4de4 lea ecx,[ebp-0x1c] ss:025ae942=????????
  010350f0 8945f4 mov [ebp-0xc],eax ss:025ae942=????????
  010350f3 51 push ecx
  010350f4 0fbfc0 movsx eax,ax
  010350f7 8b0485a0791401 ds:00000000=????????
  mov eax,[s1scb+0x4e20 (011479a0)+eax*4]
  010350fe 668b8094000000 mov ax,[eax+0x94] ds:00000094=????
  01035105 8945f0 mov [ebp-0x10],eax ss:025ae942=????????
  01035108 0fbfc0 movsx eax,ax
  0103510b 8b04857cc21901 ds:00000000=????????
  mov eax,[s1lnkfh+0x14 (0119c27c)+eax*4]
  FAULT ->01035112 668b4004 mov ax,[eax+0x4] ds:019fea07=????
  01035116 50 push eax
  01035117 8945e0 mov [ebp-0x20],eax ss:025ae942=????????
  0103511a e883e7feff call s1pcsgo (010238a2)
  0103511f 8d45cc lea eax,[ebp-0x34] ss:025ae942=????????
  01035122 50 push eax
  01035123 ff75e4 push dword ptr [ebp-0x1c] ss:025ae942=????????
  01035126 e877e7feff call s1pcsgo (010238a2)
  0103512b 8b45f8 mov eax,[ebp-0x8] ss:025ae942=????????
  0103512e 80781202 cmp byte ptr [eax+0x12],0x2 ds:019fea06=??
  01035132 a194120001 ds:01001294=6020fcfc
  mov eax,[_imp____dwEnabledTraces (01001294)]
  01035137 7538 jnz s1prolu6+0x682 (01035171)

  *---- Stack Back Trace ----*
  FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
  00baff3c 01032dd2 00000029 011dbe18 00000000 0000001f trcservr!s1prolu6 (FPO:
  Non-FPO [0,18,3])

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:

  Q215838 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.

Additional query words:

======================================================================
Keywords          : kbsna300sp1 kbsna300sp2 kbsna300sp3 kbsna300sp4 sna4 kbsna400sp1 kbsna400sp2 kbsna400sp3 kbSNA400sp4fix kbSNA400PreSP4fix 
Technology        : kbAudDeveloper kbSNAServSearch
Version           : WINDOWS: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
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.