Article ID: 192807
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
This article was previously published under Q192807
SYMPTOMS
The SNABase service may not start initially but can be started manually after the system completes startup. In addition, an event ID 590 may be logged in the application event log.
CAUSE
The SNABase service cannot start until all dependency services have completed initialization. The SNABase service is designed to time out if the dependency services do not start after 10 seconds. SNA Server's SNABase service is dependent upon the following services:
Workstation, Server, and NT LM Security Support Provider
If any of these other services do not start in a timely fashion, the SNABase service will not be able to start, and an event ID 590 may be logged in the application event log.
RESOLUTION
SNA Server 3.0
To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack
SNA Server 4.0
This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
STATUS
Microsoft has confirmed that this is a problem in SNA Server versions3.0 SP3, 4.0, and 4.0 SP1. This problem was first corrected in SNA Server 3.0 Service Pack 4.
MORE INFORMATION
The following registry entry has been added to allow a configurable timeout parameter for the SNABase service:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SnaBase\Param eters:
Name: ServerStartupTimeout Type: REG_DWORD Value: <timeout in seconds> (The default is 10.)
Keywords: kbbug kbfix KB192807
