Microsoft KB Archive/231988: Difference between revisions
m (Text replacement - "<" to "<") |
m (Text replacement - ">" to ">") |
||
Line 63: | Line 63: | ||
<br /> | <br /> | ||
<pre class="codesample"> -e<drive | <pre class="codesample"> -e<drive>:<directory>\ERRORLOG | ||
-d<drive | -d<drive>:<directory>\MASTER.DAT | ||
</pre> | </pre> | ||
Line 75: | Line 75: | ||
<br /> | <br /> | ||
<pre class="codesample"> -d<drive | <pre class="codesample"> -d<drive>:<directory>\MASTER.DAT | ||
-e<drive | -e<drive>:<directory>\ERRORLOG | ||
</pre> | </pre> | ||
Or modify the Parameters key under the following so that SQLArg0 is pointing to Master.dat and SQLArg1 is pointing to the error log: | Or modify the Parameters key under the following so that SQLArg0 is pointing to Master.dat and SQLArg1 is pointing to the error log: |
Latest revision as of 09:42, 21 July 2020
Article ID: 231988
Article Last Modified on 2/24/2004
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q231988
BUG #: 53719 (SQLBUG_70)
BUG #: 56974 (SQLBUG_70)
SYMPTOMS
When attempting to upgrade SQL Server version 6.5 to SQL Server version 7.0, the wizard continually reverts back to the Logon screen with no error message. The upgrade wizard allows the user to advance to either the Logon or Code page screen, but continually fails back to the Logon screen once you click Next.
This problem occurs when the Startup Parameters for SQL Server 6.5 have been modified from their original configuration. This can be seen under the following:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLSERVER\MSSQLSERVER\PARAMETERS
SQLArg0 points to the error log and SQLArg1 points to Master.dat Or, in the server configuration under Parameters, the master is listed under the error log parameter. For example:
-e<drive>:<directory>\ERRORLOG -d<drive>:<directory>\MASTER.DAT
WORKAROUND
Modify parameters in Enterprise Manager/Parameters so that master is above the error log. For example:
-d<drive>:<directory>\MASTER.DAT -e<drive>:<directory>\ERRORLOG
Or modify the Parameters key under the following so that SQLArg0 is pointing to Master.dat and SQLArg1 is pointing to the error log:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLSERVER\MSSQLSERVER\PARAMETERS
Another situation in which this problem may occur would be if the master.dat file is stored on the root drive.
For example:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLSERVER\MSSQLSERVER\PARAMETERS SQLArg0 -dD:\MASTER.DA
The user should modify the parameters so that Master.dat is placed inside a directory, and not on the root drive. For example:
SQLArg0 -dd:\MSSQL\DATA\MASTER.DAT SQLArg1 -ec:\MSSQL\LOG\ERRORLOG
The master.dat file MUST be in a directory other than a root and without a space in the path.
To work around this situation use the following steps:
- If SQL 6.5 is installed on the same computer, remove the SQL Server 7.0 installation.
- Follow the steps described in this Microsoft Knowledge Base article:
181602 INF: How to Move a Device to Another Location
Refer to Option #2 in the article.
- Install SQL Server 7.0.
- Use the Upgrade Wizard.
Another approach to workaround the problem is to dump the databases, uninstall SQL Server 6.5, then reinstall SQL Server 6.5 with the Master.dat file being written to a directory rather than to the root drive. Then, restore the SQL Server 6.5 databases, install SQL Server 7.0, and then run the Upgrade Wizard.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Additional query words: Upgrade hang
Keywords: kbbug kbpending KB231988