Article ID: 159277
Article Last Modified on 11/19/2003
APPLIES TO
- Microsoft SNA Server 3.0, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 2.11 Service Pack 1, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q159277
SYMPTOMS
The init status delay time should be traced in milliseconds, not seconds.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SNA Server 2.11 and 2.11 Service Pack 1 (SP1). This problem was corrected in the latest Microsoft SNA Server 2.11 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
Sample Traces:
>08/31 14:42:35.978 (+ smidgen ) Event=TEV_SNAInitTimerStarted
Thread = 0x00000085 Session = 0x002664E0 Socket = 0x00000134
Delay = 1000 seconds
TN3270 admin init status delay set to 1 second.
>08/31 14:59:50.165 (+ smidgen ) Event=TEV_SNAInitTimerStarted
Thread = 0x00000050 Session = 0x00266500 Socket = 0x00000014
Delay = 15000 seconds
TN3270 admin init status delay is set to 15 seconds.
>08/31 15:00:35.931 (+ smidgen ) Event=TEV_SNAInitTimerStarted
Thread = 0x00000141 Session = 0x002664F0 Socket = 0x00000130
Delay = 45000 seconds
TN3270 admin init status delay is set to 45 seconds.
Additional query words: prodsna tn3270
Keywords: kbbug kbfix kbnetwork KB159277
