FIX: "Random Sponsors" Option Does Not Work on HIS 2000 End-User Client (323189)



The information in this article applies to:

  • Microsoft Host Integration Server 2000

This article was previously published under Q323189

SYMPTOMS

The Host Integration Server (HIS) 2000 End-User Client always connects to sponsor servers in the order in which they are listed in the SNA Resource Location Wizard, even if the Select SNA Service computer in random order (also known as the Random Sponsors) option is selected.

CAUSE

This behavior occurs because the routine used by the HIS 2000 End-User Client to place the configured sponsor servers in the client's service table does not randomly add the sponsor servers when the Select SNA Service computer in random order option is selected.

RESOLUTION

Microsoft Host Integration Server 2000

The English version of this fix has the file attributes (or later) 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 
   -------------------------------------------------
   16-May-2002 15:49 5.0.0.836  65,808 Dmodappc.dll 
   16-May-2002 15:49 5.0.0.836  61,712 Snadmod.dll 
   16-May-2002 15:49 5.0.0.836 233,744 Snakrnl.dll 
   16-May-2002 15:49 5.0.0.836 102,672 Snands32.dll 
   16-May-2002 15:49 5.0.0.836 155,920 Wappc32.dll 
   16-May-2002 15:49 5.0.0.836  98,576 Snabase.exe 

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files. 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

STATUS

Microsoft has confirmed that this is a problem in Microsoft Host Integration Server 2000. This problem was first corrected in Host Integration Server 2000 Service Pack 1.

Modification Type:MinorLast Reviewed:4/13/2005
Keywords:kbBug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB323189 kbAudDeveloper