Article ID: 178492
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 Q178492
SYMPTOMS
The TN3270 or TN5250 service may end unexpectedly with an access violation when saving the configuration file, even if the configuration file changes do not affect these services. This problem can occur if the SNA Server Manage Agent service (Mngagent.exe) is restarted on the SNA Server. The following symptoms will occur when this problem happens:
- All TN3270 or TN5250 client users will lose their sessions and the TN3270 or TN5250 Server service will no longer be running.
- The following event will be logged in the Windows NT application event log:
- A new entry will be created in the <ntroot>\drwtsn32.log file (the failing routine in mngbase.dll is the same for both TN3270 or TN5250):
CAUSE
When the configuration file changes, the TN3270 and TN5250 services are both notified and attempt to handle dynamic changes to their configuration data. However, if the mngagent service had been stopped and restarted, the configuration data location within the Manage shared memory may change, causing the services to access an invalid memory location causing an access violation.
WORKAROUND
Do not stop and restart the SNA Server Manage Agent service (Mngagent.exe).
STATUS
Microsoft has confirmed this to be a problem in SNA Server 3.0 (including SP1 and SP2).
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 KB178492