This article was previously published under Q312537
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 101115 (SQLBUG_70)
If a restore operation is in progress on a SQL Server 7.0 server and at the same time a user opens or uses a SQL Server 2000 version of Enterprise Manager against the SQL Server 7.0 server, the SQL Server service may stop unexpectedly. The SQL Server error log does not give any indication as to why the SQL Server service stopped.
A deadlock occurs between the restore operation and the SQL statement issued by Enterprise Manager to list the databases when the database folder expands. SQL Server does not handle the deadlock correctly during a restore operation and an unhandled exception occurs, which stops the service.
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:
Date Time Version Size File name Platform ---------------------------------------------------------------- 29/12/2000 22:41 7.00.976 4.81 MB Sqlservr.exe x86 29/12/2000 22:41 7.00.976 11.1 MB Sqlservr.exe Alpha
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
To work around this problem, use the SQL Server 7.0 version of Enterprise Manager to administer SQL Server 7.0 servers if you restore databases regularly.
If you still use the SQL Server 2000 version of Enterprise Manager, the fix discussed in the following Microsoft Knowledge Base article may reduce the chance of experiencing the problem because it reduces the amount of time SQL Server issues the SELECT FROM SYSDATABASES statement:
282416 FIX: Opening the Database Folder in SQL Server Enterprise Manager 2000 Takes a Long Time
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.
You can see the deadlock if you run the SQL Profiler against the SQL Server 7.0 server and capture the Lock:Deadlock event when the problem occurs.