FIX: Upgrade Wizard Fails with "Backup 6.x Devices - phase II" Error if Using Tape

Article translations Article translations
Article ID: 244538 - View products that this article applies to.
This article was previously published under Q244538
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56542 (SQLBUG_70)
Expand all | Collapse all


The Upgrade Wizard may fail with the following message:
Backup 6.x Devices - phase II
When upgrading from SQL Server 6.5 to SQL Server 7.0 if the following conditions are met:
  • SQL Server 6.5 is being upgraded to SQL Server 7.0 on the same server.
  • The server is running the Japanese version of Windows NT.
  • The Japanese version of SQL Server is being upgraded.
  • TAPE is chosen as the data transfer method.
In addition, the following entry is the only entry that is written to the UPGRADE.LOG file:
##### Thursday, September 28, 2000 - 01:01:18 #####
6.x Master SQL Executive 6.x ##### Thursday, September 28, 2000 - 01:02:40 #####		
6.x ##### Thursday, September 28, 2000 - 01:03:58 #####
6.x ##### Thursday, September 28, 2000 - 01:05:43 #####
The preceding entries are repeated every time you attempt the upgrade.


When running the Upgrade Wizard, a temporary file, named ~BACKUP.INI, is created in the <SQL 7.0 directory>\upgrade directory, where <SQL 7.0 directory> is the root directory where SQL 7.0 is installed (by default, c:\mssql7). During creation of this file, the carriage return line feed is not getting properly written to the file.


To work around this problem, when the Upgrade Wizard screen gets to the window that displays the following:
and before pressing the FINISH button, use Notepad to change the ~BACKUP.INI file, adding a carriage return and line feed as indicated below.

BEFORE making the change, the file will contain the following:
some data
AFTER making the change, the file should contain the following:
some data
Once this change has been made, save the file and then press the FINISH button.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


This problem occurs only on Japanese language SQL Servers.


Article ID: 244538 - Last Review: October 22, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix KB244538

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from