BUG: Improper Load of Master Hangs SQL Server

Last reviewed: April 30, 1997
Article ID: Q119912

The information in this article applies to:

  - Microsoft SQL Server version 4.2

BUG# NT: 866 (4.2)

SYMPTOMS

If you load an outdated dump of the master database, it may cause Microsoft SQL Server to not restart.

Bug number 866 covers a specific case of the problems that can occur if an incorrect dump of master is loaded. If you drop a database and recreate it so that it gets the same database id, and the log of the new database maps back into the same area on the same device that held the old database, then SQL Server will not restart if a dump of master is loaded that contains the old mapping for the database.

SQL Server version 4.2 generates a Dr. Watson window on the restart which reads:

   SQLSERVR.EXE had a stack overflow (0xc00000fd), address:0x0041f27f.

SQL Server version 4.21 will appear to start successfully, but all attempts to connect will time out, including even a local isql connection attempt. SQL Server cannot be stopped with the stoplight application or net stop, and the server must be rebooted.

WORKAROUND

If you have a copy of the MASTER.DAT from just before the load, restore it and restart SQL Server. If you have another dump of master that is good, restart SQL Server from the command line as follows:

   sqlservr -T3608

Then, connect as sa and load the proper dump of the master. If neither of these options is available, contact your SQL Server support provider. An attempt could be made to rebuild the master database as per Example 4 on page 316 of the "System Administrator's Guide," but this is a time consuming process that is best performed under the guidance of your SQL Server support provider.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem does not occur in Microsoft SQL Server version 6.0.

MORE INFORMATION

As mentioned in the SQL Server "System Administrator's Guide," you should always dump your master database whenever any of the system information in the database changes, and any attempt to load the master database must be made from this most current dump. Page 309 of the "System Administrator's Guide" lists the most common commands which alter system information in the master database.

Additional query words: Windows NT
Keywords : kbbug4.20 kbother SSrvWinNT
Version : 4.2
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.