Trap Occurs in the snaservr!s1pnsuns Function (819764)
The information in this article applies to:
- Microsoft SNA Server 4.0 SP4
SYMPTOMSWhen SNA Server 4.0 is running, a trap may occur in the snaservr!s1pnsuns function. A Dr. Watson log file may show data that is similar to the following: State Dump for Thread Id 0x6bd
eax=01190000 ebx=00000030 ecx=00000000 edx=00000000 esi=01d3d864 edi=00000079
eip=010549cf esp=00bafe64 ebp=01d3d864 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: s1pnsuns
010549a0 6683ff77 cmp di,0x77
010549a4 0f84e8020000 je s1pnsuns+0x9d2 (01054c92)
010549aa 6683ff78 cmp di,0x78
010549ae 0f84de020000 je s1pnsuns+0x9d2 (01054c92)
010549b4 6683ff73 cmp di,0x73
010549b8 0f84d4020000 je s1pnsuns+0x9d2 (01054c92)
010549be 8b442424 mov eax,[esp+0x24] ss:01e0e86b=????????
010549c2 25ffff0000 and eax,0xffff
010549c7 8d1440 lea edx,[eax+eax*2] ds:01190000=01110100
010549ca a1d0691801 mov eax,[sct (011869d0)] ds:011869d0=01190000
FAULT ->010549cf 8b4cd0ec mov ecx,[eax+edx*8-0x14] ds:0125ea07=00000000
010549d3 894c241c mov [esp+0x1c],ecx ss:01e0e86b=????????
010549d7 8b54d0f0 mov edx,[eax+edx*8-0x10] ds:0125ea07=00000000
010549db 8d44241c lea eax,[esp+0x1c] ss:01e0e86b=????????
010549df 50 push eax
010549e0 56 push esi
010549e1 89542428 mov [esp+0x28],edx ss:01e0e86b=????????
010549e5 e85685ffff call s1pnsdpn (0104cf40)
010549ea 6683ff76 cmp di,0x76
010549ee 7548 jnz s1pnsuns+0x778 (01054a38)
010549f0 8b5c2438 mov ebx,[esp+0x38] ss:01e0e86b=????????
010549f4 0fbf4b0a movsx ecx,word ptr [ebx+0xa] ds:0125ea37=0000
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
01d3d864 00100001 11000b00 00000000 00000000 9b600004 snaservr!s1pnsuns (FPO: [EBP 0x00000000] [1,59,4]) CAUSEThe trap occurs when the SNA Server service (Snaservr.exe) receives a Close(SSCP) request for a session control block that is being used by a SSCP-PU session. The SNA Server service then issues a NOTIFY message on this session. The mainframe rejects the NOTIFY message with an 0x0826 message, and the trap occurs while the SNA Server service tries to build a CSI status message to send to the SNA Manager.RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SNA Server 4.0 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) 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.
Date Time Version Size File name
----------------------------------------------------
16-May-2003 11:35 4.0.0.607 468,864 Snaservr.exe
16-May-2003 11:35 4.0.0.607 936,368 Trcservr.exe
Note Because of file dependencies, the most recent fix that contains
these files may also contain additional files. STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 10/5/2005 |
---|
Keywords: | kbQFE kbfix kbbug KB819764 kbAudDeveloper |
---|
|