Article ID: 915041
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Host Integration Server 2004 Standard Edition
- Microsoft Host Integration Server 2004 Enterprise Edition
SYMPTOMS
Consider the following scenario. A Microsoft Host Integration Server 2004 client is installed on a server that has Microsoft Windows Server 2003 Terminal Server enabled. The first user logs on to the terminal server. The first user can successfully run an SNA application through the Host Integration Server 2004 client. An example of an SNA application is a 3270 emulator. Successive users log on to the terminal server, and the successive users try to run an SNA application. In this scenario, the successive users receive the following error message:
When this problem occurs, an event that resembles the following is logged in the Application log:
Event Type: Error
Event Source: SNA Base Service
Event Category: None
Event ID: 567
Date: Date
Time: Time
User: domain\username
Computer: Computer name
Description:
Creation of a socket or named pipe failed, rc = 5, socket/pipe name = \\.\PIPE\COMNAP
The Drwtsn32.exe file may be the default debugger for the terminal server, and the Drwtsn32.exe file may be configured to create a User.dmp file. In this case, the stack output that appears in the User.dmp file resembles the following information when this problem occurs:
Application exception occurred:
App: C:\Program Files\Microsoft Host Integration Server\system\SnaBase.exe (pid=3620)
When: <Date> @ <Time>
Exception number: c0000005 (access violation)
function: SNATRC!SendPopupRequest
60b84a59 e866780000 call SNATRC!_SEH_prolog (60b8c2c4)
60b84a5e 33f6 xor esi,esi
60b84a60 8975e4 mov [ebp-0x1c],esi
60b84a63 8975e0 mov [ebp-0x20],esi
60b84a66 83cbff or ebx,0xffffffff
60b84a69 53 push ebx
60b84a6a ff35ccd8b860 push dword ptr [SNATRC!PQMutex (60b8d8cc)]
60b84a70 ff151410b860 call dword ptr [SNATRC!_imp__WaitForSingleObject (60b81014)]
60b84a76 8975fc mov [ebp-0x4],esi
60b84a79 a1c8d8b860 mov eax,[SNATRC!PopShrPtr (60b8d8c8)]
FAULT ->60b84a7e 39580c cmp [eax+0xc],ebx ds:0023:0000000c=????????
60b84a81 0f8491000000 je SNATRC!SendPopupRequest+0xc6 (60b84b18)
60b84a87 8b7008 mov esi,[eax+0x8]
60b84a8a 8bfe mov edi,esi
60b84a8c 897ddc mov [ebp-0x24],edi
60b84a8f 69f620040000 imul esi,esi,0x420
60b84a95 8b4c0610 mov ecx,[esi+eax+0x10]
60b84a99 894808 mov [eax+0x8],ecx
60b84a9c a1c8d8b860 mov eax,[SNATRC!PopShrPtr (60b8d8c8)]
60b84aa1 395808 cmp [eax+0x8],ebx
60b84aa4 7508 jnz SNATRC!SendPopupRequest+0x5c (60b84aae)
*----> Stack Back Trace <----*
ChildEBP RetAddr Args to Child
0084e6a8 6744cd6b 0084e6c0 008b0014 0084ee2c SNATRC!SendPopupRequest+0x2c (FPO: [Non-Fpo])
0084ecc0 67457c1b 0084ee2c 00000000 674bcf60 SNADMOD!sepdpop_int+0x40f (FPO: [1,384,3])
0084ece4 67458e80 0084ee2c 00000000 00000000 SNADMOD!sepdnmsd_int+0x1a4 (FPO: [EBP 0x0084ece8] [4,3,4])
0084ed00 6746939f 0084ee2c 00000000 00000000 SNADMOD!sepdnmsd+0x35 (FPO: [4,0,2])
0084efc4 67430ab6 00000237 00000000 00000000 SNADMOD!com_mess+0x19a (FPO: [Non-Fpo])
0084eff0 60785426 00000010 00000237 607892ec SNADMOD!SnaLog+0x197 (FPO: [EBP 0x00000237] [3,0,4])
0084f040 6743be96 00860044 674bdf60 00ac0000 SNALM!ListenForConnection+0x1d8 (FPO: [EBP 0x00860044] [4,10,4])
0084f06c 6744b432 00860044 674bdf60 674b3238 SNADMOD!ListenConnection+0xa7 (FPO: [Non-Fpo])
0084f620 6744bad0 00000000 00000001 00000005 SNADMOD!sbpdinit_dll_int+0x1b2f (FPO: [Non-Fpo])
0084f640 010269f5 00000001 00000005 0000001c SNADMOD!sbpdinit_dll+0x19 (FPO: [Non-Fpo])
0084faf8 01028b3d 00000001 0084ffb0 0084ff7c SnaBase!InitSnaBase+0xbce (FPO: [Non-Fpo])
0084ffa0 0102a3da 00000001 0084ffb0 0100aa48 SnaBase!SnaBaseMainRoutine+0x190 (FPO: [Non-Fpo])
0084ffb8 77e66063 0008258f 00000000 00000000 SnaBase!ServiceThread+0x1b (FPO: [Non-Fpo])
Note This problem does not occur if the users who log on to the terminal server have administrative credentials.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Snabase.exe | 6.0.2034.0 | 216,064 | 12-Jun-2006 | 23:36 | x86 |
| Snadmod.dll | 6.0.2034.0 | 662,016 | 12-Jun-2006 | 23:36 | x86 |
| Snaevent.dll | 6.0.2034.0 | 472,064 | 12-Jun-2006 | 23:36 | x86 |
| Snalm.dll | 6.0.2034.0 | 50,688 | 12-Jun-2006 | 23:36 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kberrmsg kbfix kbqfe kbpubtypekc kbhotfixserver KB915041
