Article ID: 930878
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
SYMPTOMS
Consider the following scenario:
- You have two servers that are in different domain forests.
- The two servers have the same computer name.
- You install Microsoft SQL Server 2000 on one server, and you install Microsoft SQL Server 2005 on the other server.
- On the server that is running SQL Server 2005, you use SQL Server Management Studio to try to stop the remote instance of SQL Server 2000.
In this scenario, the remote instance of SQL Server 2000 does not stop. Instead, the local instance of SQL Server 2005 stops.
WORKAROUND
To work around this problem, use one of the following techniques:
- If SQL Server Enterprise Manager is installed on the server that is running SQL Server 2005, use SQL Server Enterprise Manager to stop the remote instance of SQL Server 2000.
Use SQL Query Analyzer to connect to the remote instance of SQL Server 2000. Then, run the following statement.
Shutdown with nowait
- Use Remote Desktop Connection (RDC) to connect to the remote server. Then, stop the remote instance of SQL Server 2000.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbtshoot kbprb kbpubtypekc kbexpertiseadvanced kbsql2005tool KB930878
