Article ID: 110582
Article Last Modified on 12/5/2003
APPLIES TO
- Microsoft SNA Server 2.0
- Microsoft SNA Server 2.1
- Microsoft SNA Server 3.0
- Microsoft SNA Server 2.11 Service Pack 1
- Microsoft SNA Server 2.11 Service Pack 2
This article was previously published under Q110582
SYMPTOMS
If an SNA Server link service fails to start for any reason, the SNA Server service will not start. Using SNA Server Admin, the server switches from Pending to Inactive when it is started.
WORKAROUND
To work around this problem, remove any SNA Server link services that depend on adapters that are not present, or determine why the SNA link service failed to start. Possible causes for link service initialization failures include, but are not limited to, the following:
- Adapter not present in the machine.
- Interrupt conflict with another device in the machine.
- DLC driver not installed or bound to the network adapter.
MORE INFORMATION
When SNA Server is installed, the SNA Server service is configured to depend on all underlying link services to start. However, if an underlying link service fails to start for any reason, SNA Server fails to start and the following error will be logged in the Windows NT system log:
Note that <snalink> is the name of the SNA Server link service specified during SNA Server setup (default names are SnaSdlc1, SnaDlc1, SnaDft1, SnaX251). This error occurs because the <snalink> service did not start. The reason for the failure should be present in a preceding error in the system event log, reported as Event ID #7000.
This no longer occurs with SNA Server versions 3.0 and later.
Additional query words: prodsna SNA service 7000 7001
Keywords: kbnetwork KB110582
