Q112655 - BUG: Upgrade Fails on Server with Suspect Database

BUG: Upgrade Fails on Server with Suspect Database

Q112655

The information in this article applies to:

Microsoft SQL Server version 4.2x

BUG# 9799 (4.21)

SYMPTOMS

When upgrading from SQL Server for Windows NT version 4.2 to version 4.21, if the server has a database with a 'suspect' status , the upgrade indicate the following error message at the end:

cannot run isql.exe, check relevant.out

If you look under the install directory, there is no file named RELEVANT.OUT or ISQL.OUT.

SQL Server can start up with no problem. However, the system stored procedures will no longer be present in the master database. Trying to run

ISQL -Usa -P -S -iinstmstr.sql

to manually install the scripts will result in an access violation on the client connection.

WORKAROUND

Make sure there is no 'suspect' database before upgrading to SQL NT 4.21. If there is one, drop or recreate it before proceeding with the upgrade.

If you did not check to see if the server has a 'suspect' database and the upgrade failed, you have to either copy the backup copy of MASTER.DAT over or load the master database dump. Then, drop or recreate the 'suspect' database, and run upgrade again.

STATUS

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

Additional query words: setup Windows NT

Keywords : kbsetup
Issue type :
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2