Article ID: 284351 - View products that this article applies to.
This article was previously published under Q284351
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 101132 (SQLBUG_70)
If one of the SQL Server client utilities, such as Enterprise Manager or Profiler, has been used to register more than one SQL Server, and SQL Server 7.0 Service Pack 3 has been installed, the following may occur:
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301511NOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 4.
(http://support.microsoft.com/kb/301511/EN-US/ )INF: How to Obtain the Latest SQL Server 7.0 Service Pack
The English version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
Version File name Platform ------------------------------------- 7.00.977 Comnevnt.dll Intel 7.00.977 Comnevnt.dll Alpha
NOTE: The self-extracting executable is not localized; however, you can install the self-extracting executable on a localized server.
To install the hotfix, perform the following steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.
When this problem occurs with SQL Server Profiler, the title bar will show that you are connected to the desired server, but if you generate activity against that server, these events are not captured. Profiler is actually connected to the first SQL Server registered. If the Server Name column is included in the trace definition, it contains the name of the server that is actually being monitored.
On a computer running Windows 95, Windows 98 or Windows Me, error-based alerting may not work if the first registered server is not the local server. This is because SQL Server Agent starts a Profiler trace to be notified of errors.