Article ID: 286168
Article Last Modified on 2/21/2007
APPLIES TO
- 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
- Microsoft SNA Server 4.0 Service Pack 4
- Microsoft Host Integration Server 2000 Standard Edition
This article was previously published under Q286168
SYMPTOMS
SNA Server or Host Integration Server 2000 systems being used to distribute DLC 802.2 link services for use by branch SNA Servers and/or Host Integration 2000 servers in a Distributed Link Service (DLS) environment may experience an application exception in Snalink!UpdateDLSData.
NOTE: The problem only occurs when a DLS connection terminates unexpectedly. Therefore, the Application Event log may contain events normally associated with connection outages prior to the application exception. Common connection outage events logged by SNA Server/HIS 2000 include the following events: 23, 227, 226.
CAUSE
The application exception occurs when a NULL message pointer is passed into the UpdateDLSData function.
RESOLUTION
SNA Server 4.0
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 should have the following file attributes or later:
| File name | Date | Time |
|---|---|---|
| Snadlc.dll | 01/26/2001 | 09:13AM |
NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
Host Integration Server 2000
To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
328152 How to Obtain the Latest Host Integration Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
| File name | Date | Time |
|---|---|---|
| Snadlc.dll | 01/26/2001 | 09:13AM |
NOTE: Because of file dependencies, the most recent fix that contains the preceding 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. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
MORE INFORMATION
If DRWTSN32.exe is configured as the default debugger, information similar to the following is added to the DRWTSN32.LOG when this application exception occurs:
Application exception occurred:
App: exe\snalink.dbg (pid=89)
When: 12/5/2000 @ 19:8:42.58
Exception number: c0000005 (access violation)
[data omitted...]
6338917d 7fec jg UpdateDLSData+0x8b (6338916b)
6338917f a17c1a3963 mov eax,[DlsData+0x344 (63391a7c)] ds:63391a7c=63391a80
63389184 6840173963 push 0x63391740
63389189 50 push eax
6338918a 6849173963 push 0x63391749
6338918f ffd3 call ebx
63389191 83c40c add esp,0xc
63389194 c7053817396300000000 ds:63391738=00000000
mov dword ptr [DlsData (63391738)],0x0
6338919e 8bb42420010000 mov esi,[esp+0x120] ss:00baff0c=63387d83
633891a5 6849183963 push 0x63391849
FAULT ->633891aa 660fb64e0a movzx cx,byte ptr [esi+0xa] ds:0161ea08=??
633891af 51 push ecx
633891b0 e84f350000 call GetClientWorkstationName (6338c704)
633891b5 85c0 test eax,eax
633891b7 0f84cd010000 je UpdateDLSData+0x2aa (6338938a)
633891bd 8d542414 lea edx,[esp+0x14] ss:021ce7f3=????????
633891c1 52 push edx
633891c2 6a03 push 0x3
633891c4 6a00 push 0x0
633891c6 6849173963 push 0x63391749
633891cb 6802000080 push 0x80000002
633891d0 ff1500103863 ds:63381000=77dd992e
call dword ptr [_imp__RegOpenKeyExA (63381000)]
In addition, an event similar to the following will be logged in the Application Event Log:
Additional query words: HIS 2000
Keywords: kbbug kbfix kbhostintegserv2000sp1fix kbhostintegserv2000presp1fix KB286168
