Article ID: 242876
Article Last Modified on 6/24/2004
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
- Microsoft SNA Server 4.0 Service Pack 2
- Microsoft SNA Server 4.0 Service Pack 3
This article was previously published under Q242876
SYMPTOMS
The SNA Host Account Cache (Snaudb.exe) may stop unexpectedly. When this occurs, the following Host Security features may stop functioning until the service is restarted:
- Single Sign-On (SSO)
- Password Replication to/from a host (for example, Mainframe, AS/400) system
If Drwtsn32.exe is configured as the default debugger on the Windows NT Server running the SNA Host Account Cache service, a Drwtsn32.log file similar to the following is generated in the Windows NT system directory:
In addition, an event similar to the following is logged in the Windows NT application event log when the Access Violation error occurs:
CAUSE
The Access Violation error occurs if a Host Security component (for example, the Backup Host Account Cache service, SNA WinNT Account Synchronization service, and so on) attempts to register with the Master (or Primary) SNA Host Account database immediately after the component un-registers itself with the Master Host Account database.
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:
215838 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.
MORE INFORMATION
This fix corrects the timing window that can cause the Access Violation error to occur when a Host Security component tries to register itself with the Master Database (MDB) immediately after it un-registers itself.
The following is an excerpt from a SNA Host Account Cache internal message trace (Udbmsg1.atf) that captures a UDI_REGISTER message that immediately follows a UDI_UNREGISTER message from a backup SNA Host Account Cache Database:
MSG_OUTGOING to ServerType: MDB, Address: 0x27e4b0
Message Type: UDI_UNREGISTER. Sequence Number: 0
Request: Number of UnRegistration Vectors: 1, Status: 0
RegistrationVector #0: DomainName: USPASS, ResourceType: SDB, Address: USFLPK1DEVPD05
____________________________________________________________
MSG_OUTGOING to ServerType: MDB, Address: 0x27ed50
Message Type: UDI_REGISTER. Sequence Number: 0
Request: Number of Registration Vectors: 1, Status: 0
RegistrationVector #0: DomainName: USPASS, ResourceType: SDB, Address: USFLPK1DEVPD05
MSG_OUTGOING to ServerType: MDB - Error: ErrorCode: 1722
MSG_OUTGOING to ServerType: MDB - Error: ErrorCode: 1722
___________________________________________________________
The ResourceType of Secondary Database (SDB) correlates to a Backup SNA Host Account Cache service.
The timestamps in the trace file show that these messages were received at approximately the same time.
Keywords: kbbug kbfix kbsna400presp4fix kbqfe kbsna400sp4fix KB242876
