Microsoft KB Archive/178254: Difference between revisions
m (Text replacement - ">" to ">") |
m (Text replacement - """ to """) |
||
Line 107: | Line 107: | ||
== CAUSE == | == CAUSE == | ||
This problem can occur if an SNA Server connection is configured to | This problem can occur if an SNA Server connection is configured to "Support Dynamic Remote APPC LU Definition". The SNA Server service assumes that the TP (transaction program) did not end following a session activation failure. However, if the TP does end, the SNA Server fails with an access violation. This problem may also cause an SNA Server access violation in function s1prfpda(). | ||
</div> | </div> |
Latest revision as of 11:09, 21 July 2020
Article ID: 178254
Article Last Modified on 9/22/2005
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
This article was previously published under Q178254
SYMPTOMS
SNA Server (Snaservr.exe) may fail unexpectedly with an access violation, causing the following symptoms:
- The following event will be logged into the Windows NT application event log:
- The following log entry will be created in the <ntroot>\drwtsn32.log file:
CAUSE
This problem can occur if an SNA Server connection is configured to "Support Dynamic Remote APPC LU Definition". The SNA Server service assumes that the TP (transaction program) did not end following a session activation failure. However, if the TP does end, the SNA Server fails with an access violation. This problem may also cause an SNA Server access violation in function s1prfpda().
RESOLUTION
Obtain the following fix or wait for the next SNA Server 3.0 service pack.
This fix should have the following timestamp:
11/21/97 10:58a 437,440 <snaroot>\system\snaservr.exe 11/21/97 10:58a 412,692 <ntroot>\symbols\exe\snaservr.dbg 11/21/97 10:58a 825,072 <snaroot>\system\trcservr.exe 11/21/97 10:58a 751,608 <ntroot>\symbols\exe\trcservr.exe
NOTE: SNA Server 3.0 Service Pack 2 should be applied prior to applying this fix.
STATUS
Microsoft has confirmed this to be a problem in SNA Server version 3.0, version 3.0 Service Pack 1, and version 3.0 Service Pack 2.
This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Keywords: kbbug kbfix kbqfe kbhotfixserver KB178254