PRB: Restoring Master Database In Enterprise Manager Generates GetOverlappedResult() Error

• Microsoft SQL Server version 7.0

SYMPTOMS

When Enterprise Manager is used to restore the master database, a dialog box is displayed indicating that your connection has been broken. The exact message may differ depending on what network library is being used, but will be similar to the following one (using Named Pipes):

Microsoft SQL-DMO (ODBC SQLState: 01000)

ConnectionTransact (GetOverlappedResult()).
Connection broken

CAUSE

By design, SQL Server will always shut down at the end of restoring the master database. Before it shuts down, it sends two messages to the client. One to indicate the successful restore and a second to indicate that the connection will be dropped. These two Severity 10 messages, which follow, are mapped by ODBC as informational messages. The SQL-DMO call used in issuing the command filters out any informational messages generated by the server. Thus, the only error seen will be the one indicating the dropped connection.

WORKAROUND

In most cases, no action is required. Restart SQL Server so that it uses the newly restored master database.

If you have trouble restarting SQL Server after encountering such an error during the load, use Query Analyzer or another query tool to issue the RESTORE DATABASE command. It may be necessary to rebuild the master database before attempting a subsequent restore. This can be done using the Rebuildm.exe utility. For more details, see the "How to rebuild the master database" topic in SQL Books Online.

Upon successful completion of the RESTORE, a query tool such as Query Analyzer with display the following messages:

Msg 3150: The master database has been successfully restored. Shutting down SQL Server.
Msg 5702: SQL Server is terminating this process.

Additional query words: ExecuteImmediate MMC SEM

Keywords : SSrvAdmin SSrvEntMan kbSQLServ700
Version : winnt:7.0
Platform : winnt
Issue type : kbprb