Article ID: 110666
Article Last Modified on 10/29/2003
APPLIES TO
- Microsoft SNA Server 2.0, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q110666
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.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Microsoft is researching this problem and will post more information in this article when the information becomes available.
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
- The Windows NT application event log will include:
- SNA Server Admin will show the server service as "Stopping."
- If started through Control Panel, Control Panel displays:
- If started from the command line:
SnaBase Service
The Windows NT application event log will include:
Event 650, SNA Server, Warning, ConnectNmPipe returned error rc=1
- If started from the command line:
Additional query words: prodsna SNATRC.DLL 650 121
Keywords: kbbug kbnetwork kbpending KB110666