BUG: Upgrade Fails if Not Enough Space on Master for Tempdb

 Last reviewed: March 12, 1997
Article ID: Q149650
4.21a 6.00 WINDOWS kbsetup kbermsg kbbug4.21a kbbug6.00

The information in this article applies to:

  • Microsoft SQL Server, versions 4.21a and 6.0

BUG#: 14671 (4.21a)

SYMPTOMS

If there is not enough space available on the master device to create tempdb, any upgrade of SQL Server versions 4.2x or 6.0 to a newer version will fail with the message: 

   The SQL server upgrade could not be successfully completed. MSSQLserver
   The service could not be started. Please check the error/event log to
   determine the cause - 1060.

CAUSE

Tempdb is recreated based on the size of the model database during an upgrade. If there is not enough disk space left on the master device for the creation of tempdb, the upgrade will fail. For example, if model is 5 MB and there is only 2 MB of free disk space left on the master device, the creation of tempdb will fail because it will try to be created at a size of 5 megabytes, but there is only 1 MB available to be used on the master device. You need to keep in mind that there is 4K of space reserved on the master device for the configuration block, which will not allow you to allocate the last megabyte to a database.

The following is an example where the upgrade will succeed if model has been altered to a larger size: If Master device has 5 MB of disk space left and tempdb is currently 2 MB and model is 6 MB, the upgrade will succeed. Tempdb will be recreated at 6 MB. First, it will reuse the original 2 MB, then it will use the remaining 4 MB available on master.

WORKAROUND

Backup all databases and rebuild master to change the size of model back to the default size. If you rebuild the master database, you must recreate the user databases, reload each database from the most recent dump, and then reapply any changes not included in the dump.

  • OR -

For version 4.2x upgrades, create a new device, then alter tempdb to reside on the new device. Tempdb should be altered to be at least the same size of model before the upgrade. In addition, refer to Knowledge Base article Q149566 ("BUG: Upgrade/Install Fails if Model DB is Larger Than Msdb"), which will also cause an upgrade to fail due to an increase in the size of the model database.

For version 6.0 upgrades, expand the master device to a size large enough for tempdb to be created.

STATUS

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

Additional reference words: 6.00.121 install, SP1 SP2 SP3 SP4 service pak
KBCategory: kbsetup kbermsg kbbug4.21a kbbug6.00
KBSubcategory: ssrvinst
if the model database is
creation of tempdb.
Keywords : ssrvinst
Version : 4.21a 6.00
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: March 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.