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:
Attempts to start a Profiler trace against a specific server may connect to the wrong server. You may first notice this behavior as events "missing" that you would expect to have been captured.
A computer running Microsoft Windows 95, Windows 98, or Windows Millennium Edition (Windows Me) configured to send error-based alerts by means of SQL Server Agent may fail to send the alerts.
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 theMicrosoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
NOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 4.
The English version of this fix should have the following file attributes or later:
Version File name Platform ------------------------------------- 7.00.977 Comnevnt.dll Intel 7.00.977 Comnevnt.dll Alpha
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
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:
Download the appropriate version of the patch for your hardware platform from the following Microsoft Web site:
Run the self-extracting executable file to obtain the patch. During the extraction process, you will be prompted to specify a destination directory for the files. You must run the self-extracting executable on an Intel-based system to obtain both the Alpha and Intel versions of the patch.
After extracting the patch, read the included Readme.txt file for specific installation instructions for your environment.
NOTE: If you run SQL Server Profiler from the SQL Server itself, and you profile events only for the local server, it may not be necessary to apply the hotfix. Confirm whether Profiler is connecting to the correct server by adding the Server Name column to a trace. Any client computer that has more than one server registered and that uses Profiler should install the hotfix.
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.