BUG: The SQL Server 2000 Service Manager Utility Does Not List Instances That Have Not Enabled Network Connections

This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 363267 (SHILOH_BUGS)
SYMPTOMS
If you configure an instance of SQL Server 2000 or SQL Server 2000 Desktop Engine (also known as MSDE 2000) to disallow network connections, that instance will not appear in the SQL Server 2000 Service Manager utility.
CAUSE
The SQL Server ODBC driver does not return instance names to the SQL Service Manager if the instance does not support network connections.
WORKAROUND
To work around this behavior, stop and then start the service for the instance by following these steps:
  1. Right-click My Computer, and then click Manage.
  2. Double-click Services and Applications in the left-hand screen.
  3. Double-click Services.
  4. Right-click the service for the instance of SQL Server. The name of the service for a default instance of SQL Server 2000 is MSSQLServer. The name of the service for a named instance of SQL Server 2000 is MSSQL$instancename.
  5. Click the action that you want applied to the instance, such as stop or start.
STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000.
disablenetworkprotocols
Properties

Article ID: 814132 - Last Review: 02/27/2014 21:16:54 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Desktop Engine (Windows)

  • kbnosurvey kbarchive KB814132
Feedback