Microsoft KB Archive/271070

= BUG: Desktop Engine and Personal Edition Fails When You Upgrade MSDE 1.0 & Desktop Edition 7.0 =

Article ID: 271070

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q271070



BUG #: 235680 (Shiloh_bug)



SYMPTOMS
When you select the upgrade option during the installation of Microsoft SQL Server 2000 Personal Edition or Microsoft SQL Server 2000 Desktop Engine, if there is a previous edition of Microsoft SQL Server 7.0 Desktop Edition or Microsoft Data Engine (MSDE) 1.0 installed, the following error message might occur:

Update process failed. Check the log file for more

information. You can run setup again to complete the

upgrade.



CAUSE
There is not enough system memory to run all the necessary SQL scripts that are part of the upgrade process.



WORKAROUND
You need to add more memory to the computer for the installation or upgrade to complete successfully. For Microsoft Windows 98, the upgrade process that takes place after the installation of SQL Server 2000 requires 48 MB of RAM rather than the 32 MB as stated in Microsoft SQL Server Books Online.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.



MORE INFORMATION
Although SQL Server 2000 Books Online states that you can install the Desktop Engine and Professional Editions and use them to upgrade previous editions of MSDE 1.0 and SQL Server 7.0 Desktop Edition on a computer that is running Microsoft Windows 98 with 32 MB RAM, those statements are not fully accurate. You can install both the Desktop Engine and Professional Editions onto a Windows 98 computer that has 32 MB RAM only if it is an original installation, and not an upgrade of an existing installation of an earlier Microsoft SQL Server 7.0 version.

If this is the cause of a failed installation or upgrade attempt, then the log that records the progress of SQL Server 2000's Personal Edition set up, located on C:\Windows\Sqlstp.log ends with statements similar to the following: 21:03:39 C:\194PER~1\X86\BINN\OSQL.EXE -S TESTBOX -b -n -d master -o &quot;C:\MSSQL7\install\servmsgs.out&quot; -i &quot;C:\MSSQL7\install\servmsgs.sql&quot; -U sa -P 21:03:57 Process Exit Code: (0) 21:03:57 C:\194PER~1\X86\BINN\OSQL.EXE -S TESTBOX -b -n -d master -o &quot;C:\MSSQL7\install\web.out&quot; -i &quot;C:\MSSQL7\install\web.sql&quot; -U sa -P 21:04:08 Process Exit Code: (0) 21:04:09 C:\194PER~1\X86\BINN\OSQL.EXE -S TESTBOX -b -n -d master -o &quot;C:\MSSQL7\install\replcom.out&quot; -i &quot;C:\MSSQL7\install\replcom.sql&quot; -U sa -P 21:04:58 Process Exit Code: (1) 21:18:05 Error running script: replcom.sql (1) 21:18:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER 21:18:21 Process Exit Code: (0) 21:18:23 Action CleanUpInstall: 21:18:24 StatsGenerate returned: 2 21:18:24 StatsGenerate (0x8008227,0x2,0xf0000,0x0,1033,303,0xc,0x1,0,0,0 21:18:24 StatsGenerate 1,LOGGED_ON_ACCOUNT) 21:18:24 Installation Failed. The SQL Server 2000 Desktop Engine Edition does not create a Sqlstp.log file. Instead, the setup or upgrade uses a command line parameter setting to determine where a log that records the progress of the installation is written. If the installation or upgrade fails with the error message described in the &quot;Symptoms&quot; section, and the reason for the failure is lack of memory, then the log file has a section similar to this: MSI (c) (27:DF): Doing action: UpgradeDatabases.2D02443E_7002_4C0B_ABC9_EAB2C064397B Action start 12:33:47: UpgradeDatabases.2D02443E_7002_4C0B_ABC9_EAB2C064397B. MSI (c) (27:DF): Creating MSIHANDLE (110) of type 790542 for thread -242465 Loading extended custom action library sqlcax.dll Starting custom action UpgradeDatabases Stopping service Starting service Upgrading master database Stopping service Starting service Running upgrade script 1 of 18 (messages) Running upgrade script 2 of 18 (u_tables) Running upgrade script 3 of 18 (instlang) Running upgrade script 4 of 18 (procsyst) Running upgrade script 5 of 18 (oledbsch) Running upgrade script 6 of 18 (instcat) Running upgrade script 7 of 18 (ansiview) Running upgrade script 8 of 18 (xpstar) Running upgrade script 9 of 18 (instmsdb) Running upgrade script 10 of 18 (sqldmo) Running upgrade script 11 of 18 (replsys) Running upgrade script 12 of 18 (odsole) Running upgrade script 13 of 18 (servmsgs) Running upgrade script 14 of 18 (web) Running upgrade script 15 of 18 (replcom) Running upgrade script 16 of 18 (repltran) Upgrade process failed. Check the log files for more information. You can run setup again to complete the upgrade. Upgrade process returned error code 1 Action ended 12:50:50: UpgradeDatabases.2D02443E_7002_4C0B_ABC9_EAB2C064397B. Return value 1. MSI (c) (27:DF): Skipping action: RemoveUpgradedProduct.2D02443E_7002_4C0B_ABC9_EAB2C064397B (condition is false) MSI (c) (27:DF): Doing action: Additionally, the default directory where SQL Server 7.0 is installed has a file that states the cause for the failure: C:MSSQL7\INSTALL\REPLCOM.OUT

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Creating procedure sp_MSdrop_replcom

Msg 701, Level 17, State 1, Server TESTBOX Procedure sp_MSdrop_replcom, Line 543

There is insufficient system memory to run this query.

-or- C:\MSSQL7\INSTALL\REPLTRAN.OUT

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Creating procedure sp_MSdrop_repl_tran.

Msg 701, Level 17, State 3, Server TESTBOX Procedure sysobjects, Line 645

There is insufficient system memory to run this query.

After the original error message occurs, you might be able to start the SQL Server service without encountering any errors. However, because one or more scripts failed to run properly, the potential for unpredictable behavior in the future still exists, especially in regards to replication.

Additional query words: win98 win9x

Keywords: kbbug kbpending KB271070

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.