Microsoft KB Archive/899747
Article ID: 899747
Article Last Modified on 12/4/2007
- Microsoft Host Integration Server 2004 Standard Edition
- Microsoft Host Integration Server 2000 Standard Edition
On a Microsoft Host Integration Server-based system, the SnaBase service unexpectedly stops when a Common Programming Interface for Communications (CPI-C) application is started. This problem occurs if the Host Integration Server configuration includes more than 454 CPI-C Symbolic Destination Names.
When this problem occurs, you may receive an error message that is similar to the following:
Host Integration Server includes some conflicting CPI-C Symbolic Destination Name limits. The Host Integration Server management utilities let you create 481 CPI-C Symbolic Destination Names. However, this number exceeds the limits in other areas of the product. Therefore, you experience the problem that is mentioned in the "Symptom" section when you run a CPI-C application that has more than 454 CPI-C Symbolic Destination Names defined in the Host Integration Server configuration.
Host Integration Server 2004
No hotfix is currently available for Microsoft Host Integration Server 2004.
Host Integration Server 2000
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual 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 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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 09-Jul-2005 01:18 220.127.116.113 340,240 Snaadmin.dll 09-Jul-2005 01:17 18.104.22.1683 282,896 Snabase.exe 09-Jul-2005 01:17 22.214.171.1243 209,168 Snacfg.dll 09-Jul-2005 01:17 126.96.36.1993 143,632 Wcpic32.dll 09-Jul-2005 01:17 188.8.131.523 20,752 Wincpic.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Modify the Host Integration Server configuration to include 454 or fewer CPI-C Symbolic Destination Names.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply the hotfix to Host Integration Server 2000, you experience the following behavior:
- The maximum number of CPI-C Symbolic Destination Names is 454.
- If you try to create a CPI-C Symbolic Destination Name after the limit of 454 has been reached, you receive the following message:
- You cannot open a Host Integration Server configuration file (Com.cfg) that contains more than 454 CPI-C Symbolic Destination Names. If you try to open this file, you also receive the message.
- The SNA Manager MMC Snap-In will only display 454 CPI-C Symbolic Destination Names.
For more information about object type limits in Host Integration Server, click the following article number to view the article in the Microsoft Knowledge Base:
246685 Maximum number of supported objects that are allowed in SNA Server and in Host Integration Server
In both Host Integration Server 2004 and Host Integration Server 2000, a Drwtsn32.log file or a User.dmp file may be generated when this problem occurs. This file may include stack information that is similar to the following:
ChildEBP RetAddr Args to Child 00e1fbe0 77fcc774 00070000 0d00b9b0 00e1fc58 NTDLL!RtlpCoalesceFreeBlocks+0x2fb [D:\nt\private\ntos\rtl\heap.c @ 5775] 00e1fc8c 7c58e53a 00070000 00000000 0d00b9b8 NTDLL!RtlFreeHeap+0x142 [D:\nt\private\ntos\rtl\heap.c @ 3329] 00e1fcd4 67250a91 0d00b9b8 00e1fdd8 0102163e KERNEL32!GlobalFree+0x53 [e:\nt\private\windows\base\client\gmem.c @ 617] 00e1fce0 0102163e 0d00b9b8 00e1fdd0 0000000a snadmod!SNABufferFree+0x41 [c:\depothis2000sp2\source\dmod\win32\semfdmo2.c @ 5926] 00e1fcfc 01005090 004a00b4 00000000 00000000 snabase!get_cpic_sdns+0x4d [c:\depothis2000sp2\source\nap\win32\snarpc.c @ 579] 00e1fd5c 6722ed87 00e1000a 00e10004 00000000 snabase!ConfigRPCServer+0x215 [c:\depothis2000sp2\source\nap\win32\rpcsrvr.c @ 1530] 00e1fd88 6722e893 00e1000a 00e10004 00000000 snadmod!LocalProcessRpcData+0x287 [c:\depothis2000sp2\source\dmod\win32\rpc.c @ 2517] 00e1fdf4 01017ea8 01054bd0 00000001 01054bd0 snadmod!LocalProcessRpc+0xf3 [c:\depothis2000sp2\source\dmod\win32\rpc.c @ 2345] 00e1fe18 0101ce76 01054bd0 00000013 00000000 snabase!DoRpc+0xfe [c:\depothis2000sp2\source\nap\win32\semfetap.c @ 6338] 00e1fee8 01016dbb 01054bd0 67270004 01016ce1 snabase!ProcessIncomingSnapsMessage+0x97f [c:\depothis2000sp2\source\nap\win32\semfetap.c @ 9357] 00e1fef8 67247cb2 01054bd0 67270004 00000001 snabase!NapRoutingProc+0xda [c:\depothis2000sp2\source\nap\win32\semfetap.c @ 5558] 00e1ff54 6723cc5e 01054bd0 00000001 77f82091 snadmod!sepdq2_int+0x122 [c:\depothis2000sp2\source\dmod\win32\semfdmo2.c @ 767] 00e1ff74 6723d14a 00e1ffa4 00e1ffac 00e1ff9e snadmod!sbpdin_int+0x23e [c:\depothis2000sp2\source\dmod\win32\semfdmo1.c @ 5795] 00e1ffb4 7c57b388 00000000 00000000 00000000 snadmod!RamPipeThread+0x1ea [c:\depothis2000sp2\source\dmod\win32\semfdmo1.c @ 6066] 00e1ffec 00000000 6723cf60 00000000 00000000 KERNEL32!BaseThreadStart+0x52 [e:\nt\private\windows\base\client\support.c @ 460]
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
Additional query words: HIS
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB899747