Microsoft KB Archive/110390

= Automatically Starting SNA Server Through Control Panel =

Article ID: 110390

Article Last Modified on 2/17/2007

-

APPLIES TO


 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 4.0 Service Pack 1
 * Microsoft SNA Server 4.0 Service Pack 4
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1

-



This article was previously published under Q110390



SUMMARY
To automatically start SNA Server when you start your system, use the Services application to configure the SnaServer service startup method as Automatic. Also, if you are using NetView alerts and Run command, the NVAlert and NVRunCmd services should also be configured to start automatically.

With SNA Server versions 3.0 and 4.0, the following services need to be setup through Control Panel/Services in order to start automatically: Shared Folders Gateway, TN3270, TN5250, SNAPrint. All other 3.0 and 4.0 services are started automatically. With Microsoft Host Integration Server 2000 and SNA Server 4.0, you must modify the following services in Windows Services in order to start automatically: Shared Flders Gateway, TN3270, TN5250, and SNAPrint. All other Host Integration Server 2000 and SNA 4.0 services are started automatically.



MORE INFORMATION
Following is a description of each SNA Server service, and how each service is configured to start when SNA Server is installed:

SnaBase: Automatic startup. This service must be started before any other SNA Server service can run. We recommend that the SnaBase service remain set to "Automatic Startup" because several other SNA Services depend on this service.

SnaServer: Manual startup. This can be changed to Automatic startup if desired. This may also be started/stopped using the SNA Server Admin program.

SNA Server link services (SnaDlc1, SnaSdlc1, and so on): Manual startup.

SNA Server automatically starts the link services as needed. These services should NOT be configured to automatically start using Control Panel. Specifically, the SnaBase service starts these automatically. Also, the SnaServer service doesn't start unless all link services used by this server are running.

NVAlert, NVRunCmd: Manual startup. These services can be changed to Automatic startup if desired. SNA Server will not automatically start these services.

SnaNetMn: Manual startup. SNA Server will automatically start this service if NetView connectivity is configured on an SNA Server connection. This service should NOT be configured to automatically start using Control Panel, and fails with the following error message if the administrator tries to start it manually:

SNA Server Error #0352

Unable to open the configuration file, rc=618

Shared Folders Gateway: Manual startup. This service can be changed to Automatic startup if desired.

SNA MngAgent: Manual startup. This service should not be changed to Automatic startup. It will be started automatically when SnaBase is started.

Sna RPC Service: Manual startup. This service should not be changed to Automatic startup. It will be started automatically when SnaBase is started.

SnaPrint: Manual startup. This service can be changed to Automatic startup if desired.

TN3270: Manual startup. This service can be changed to Automatic startup if desired.

TN5250: Manual startup. This service can be changed to Automatic startup if desired.

SNA Host Account Synchronization: Manual startup. This service should not be configured for Automatic startup. It will be started automatically if SNA Server's Host Security features are installed and configured.

SNA Host Account Cache: Automatic startup.

SNA WinNT Account Synchronization: Automatic startup.

Additional query words: prodsna

Keywords: kbenv KB110390

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.