The information in this article applies to:
SUMMARYThe services installed by SNA Server version 3.0 and later run under a user account context. This user account is set to be a domain administrator with additional permissions. Though Microsoft recommends that the user context not be changed after initial installation, some instances may arise where the service user account needs to be changed to a different user. If this user context does not have the correct permissions, the services may fail to start and cause SNA Server to fail. MORE INFORMATION
In most cases when the SNA Server services fail to start, it is the result
of the services[ASCII 146] user password being changed, the user account being
deleted, or the user being deleted and re-added through the Windows NT User
Manager utility. Also note that if the user account that the SNA Server
services are running under does not have "Password Never Expires" selected
under that user profile, every time the password for this user is changed,
each SNA Server service must be manually changed to reflect the new
password. This is not done dynamically and must be done by the
administrator. This can be a source of more administrative overhead and
greater chance of incorrect settings being made to the SNA Server services.
Most issues involving a problem with the SNA Server services can be resolved by saving the snaroot\System\Config\Com.cfg file, removing SNA Server, and reinstalling SNA Server. This re-writes the registry and updates the user manager with an account that has the correct permissions and service dependencies. Additional query words:
Keywords : |
Last Reviewed: March 11, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |