Microsoft KB Archive/897317

From BetaArchive Wiki
Knowledge Base


FIX: The SnaBase process does not automatically terminate when all the SNA applications are closed and the "Terminate sponsor connection on disconnect" option is enabled on the Host Integration Server 2004 Client

Article ID: 897317

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Host Integration Server 2004 Standard Edition




SYMPTOMS

The SnaBase process does not automatically terminate when the following conditions are true:

  • All the SNA applications are closed on a Microsoft Host Integration Server 2004 Client. These applications may include 3270 Emulators and APPC applications.
  • The Terminate sponsor connection on disconnect option is enabled on the Host Integration Server 2004 Client.


CAUSE

This problem occurs because the Terminate sponsor connection on disconnect option was never added to the Host Integration Server Client code base.

The Terminate sponsor connection on disconnect option was originally available in the SNA Server Client for Windows 9x. This option was not available in the SNA Server Client for Windows NT because the SnaBase process only ran as a Windows Service in this client. It did not make sense to have the SnaBase service automatically terminate when SNA applications were closed because ordinary users do not have the appropriate permissions to start services in many customer environments.

In Host Integration Server 2000, the SNA Server Client for Windows 9x became the Host Integration Server 2000 End User Client. The Terminate sponsor connection on disconnect option for the SnaBase process was added to the Host Integration Server 2000 End User Client because the Host Integration Server 2000 End User Client and the SNA Server Client for Windows 9x are both based on the same underlying code. The SNA Server Client for Windows NT basically became the Host Integration Server 2000 Administrator Client.

Therefore, the Terminate sponsor connection on disconnect option was not available in the Host Integration Server 2000 Administrator Client. This is true even though the Host Integration Server 2000 Administrator Client can be configured to have the SnaBase process run as a Windows Service or as an application that is similar to the Host Integration Server 2000 End User Client. The code for the Terminate sponsor connection on disconnect option was never added to the Host Integration Server 2000 Administrator Client code base.

Host Integration Server 2004 only has a single Host Integration Server Client. The Host Integration Server 2004 Client is based on the Host Integration Server 2000 Administrator Client code base. Although the Terminate sponsor connection on disconnect option is available in the Host Integration Server 2004 Client Configuration Wizard, the option was never added to the underlying code base. Therefore, the option does not function.

RESOLUTION

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:



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
   ----------------------------------------------------
   17-Jun-2005  23:19  6.0.1962.0  215,040  Snabase.exe      
   17-Jun-2005  23:19  6.0.1962.0  648,704  Snadmod.dll                     

Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply this hotfix, the SnaBase process automatically terminates after the last SNA application is closed. The SnaBase process uses the configured time-out value that is specified in the Terminate sponsor connection on disconnect option.

The Terminate sponsor connection on disconnect option only applies when the Host Integration Server 2004 Client is configured to use one of the following deployment types:

  • Just me (run as application)
  • Everyone (run as application)

You can enable the Terminate sponsor connection on disconnect option in the Host Integration Server 2004 Client Configuration Wizard when you use a deployment type of Windows Service. However, the option will not function. Typically, you do not want the SnaBase process to automatically terminate when the SnaBase process is configured to run as a Windows service.

Additionally, the Terminate sponsor connection on disconnect option only applies if the SnaBase process is automatically started when a SNA application is started. If the SnaBase process is manually started by running Snabase.exe, the SnaBase process will not terminate when the last SNA application is closed.

The Terminate sponsor connection on disconnect option is also available in the following SNA Server 4.0 and Host Integration Server 2000 clients:

  • SNA Server Client for Windows 9x
  • Host Integration Server 2000 End User Client

Because of changes that were made to sponsor connections starting with Host Integration Server 2000, the Terminate sponsor connection on disconnect option does not provide as many advantages as the option did in earlier versions than Host Integration Server 2000.

Before Host Integration Server 2000, SNA Server clients maintained a permanent sponsor connection to the SnaBase service on the sponsor SNA Server of the SnaBase service. The Terminate sponsor connection on disconnect option let SNA Server clients automatically terminate the SnaBase process when the last SNA application was closed so that SNA Server clients did not maintain network connections to their sponsor servers.

In Host Integration Server 2000 and in later versions, the SnaBase process that is running on Host Integration Server clients automatically closes the sponsor connection after 5 minutes. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

317805 Sponsor connection changes in Host Integration Server


Because of this change in Host Integration Server, the only advantage of using the Terminate sponsor connection on disconnect option on a Host Integration Server clients is to free the system resources that are used by the SnaBase process.

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB897317