Server Services Fail when Start Configuration Changed

 Last reviewed: April 17, 1997
Article ID: Q110666
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.0

SYMPTOMS

SNA Server services are designed to run under the System account, and fail to run if the administrator changes any of the services to start under a user context.

CAUSE

The SNA Server setup program automatically configures all SNA Server services to "Log On" under the System account. This includes SnaBase, SnaServer, any SNA link services, SnaNetMn, NVAlert, and NVRunCmd. If any of the services are changed to run under a user context, they will not run.

RESOLUTION

In the Control Panel window, choose the Services icon, and then choose the Startup button and make sure all SNA Server services are configured to start under the System account.

MORE INFORMATION

The following are the errors that may occur if these services were configured to start in any account OTHER than the System account:

SnaServer Service

  • SNATRC.DLL failed to initialize.
  • The Windows NT application event log will include:

    Event 650, SNA Server, Warning, ConnectNmPipe returned error rc=1 Event 121, SNA Server, Error, Fatal error occurred, product ID=00, 

           error code = 0001
    Event 589, SNA Server, Warning, Failed to display popup, rc=0. 

           A Create process call for the popup process failed. The return
       code is shown.
    Event 624, SNA Server, Warning, Creating dump file 

           C:\SNA\traces\snadump.log for SNASERVR.EXE
    Event 4005, perfctrs, Error, Load of a required DLL failed. Make sure 

           the DLL file is in the PATH. DOS Error number is returned in the
       data (7e).
  • SNA Server Admin will show the server service as "Stopping."
  • If started through Control Panel, Control Panel displays: 

          Could not start SnaServer service on <machine>
      Error 2140: An internal Windows NT error occurred
  • If started from the command line: 

          SnaServer service could not be started.

SnaBase Service

  • SNATRC.DLL failed to initialize.
  • The Windows NT application event log will include: 

          Event 650, SNA Server, Warning, ConnectNmPipe returned error rc=1
  • If started from the command line: 

        SnaBase service could not be started.

Additional query words: prodsna SNATRC.DLL 650 121
Keywords : kbnetwork ntnetserv
Version : 2.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.