Service Pack 3 failed! - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

Service Pack 3 failed!

Author

Topic

vtk
Starting Member

2 Posts

Posted - 2002-01-15 : 01:37:35

Hello,

We tried to install Service Pack 3 on SQLServer(7.00.623) on Window2000 Terminal Server. It didn't raise any errors

while installing. After installing we checked the version of sqlserver using "SELECT @@VERSION" command. But it is

still showing below said message.

"Microsoft SQL Server 7.00 - 7.00.961 (Intel X86)
Oct 24 2000 18:39:12
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 1)"

We also cheked in Log file. Here are the 2 errors.
********************************************************
06:24:19 Begin Action: Self Registration
06:24:25 Failed to register files c:\MSSQL7\Binn\dtsui.dll
06:24:25 End Action: Self Registration

06:24:54 C:\WINNT\TEMP\_ISTMP15.DIR\osql.exe -n -d master -i "c:\MSSQL7\install\upgrade.sql" -U sa -P
06:25:16 Process Exit Code: (6006) There are no EFS keys defined for the user.
********************************************************
Except this, every statement exit code is (0).

Please help me in this problem.

Thanks in advance,
V.Thandava Krishna.

mphelps
Starting Member

12 Posts

Posted - 2002-01-15 : 05:21:49

This article from microsoft has a partial match

PSS ID Number: Q264123
Article last modified on 08-24-2001

:7.0 Service Pack 2,7.0 Service Pack 3

======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft SQL Server versions 7.0 Service Pack 2, 7.0 Service Pack 3
-------------------------------------------------------------------------------

IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help
topic in Regedt32.exe.

SYMPTOMS
========

When you try to install SQL Server 7.0 Service Pack 2 (SP2) or Service Pack 3
(SP3), the installation fails while it is trying to run SQL Server script files.
The following error message demonstrates an example of this failure with the
Upgrade.sql file. This problem might also occur with other SQL Server scripts
during the upgrade process.

Error running script: upgrade.sql(1)

Followed by:

An error occurred when running the upgrade on your server.

The following errors are logged in the Sqlsp.log file located in the temp
directory of the computer on which it was run:

11:59:32 Mode: Normal
11:59:34 Resuming Setup - starting at position 2
11:59:40 Begin CleanUpInstall
11:59:42 C:\TEMP\_ISTMP7.DIR\scm.exe -Silent 1 -Action 6 -Service MSSQLServer
12:00:22 Prcess Exit Code: (0)
12:00:32 C:\TEMP\_ISTMP7.DIR\scm.exe -Silent 1 -Action 1 -Service MSSQLServer -StartupOptions \-f \-m
12:00:53 Process Exit Code: (0)
12:01:03 C:\TEMP\_ISTMP7.DIR\osql.exe -n -d master -q"exit" -U sa -P
12:01:03 Process Exit Code: (1)
12:01:03 C:\TEMP\_ISTMP7.DIR\osql.exe -n -d master -i "D:\MSSQL7\install\upgrade.sql" -U sa -P
12:01:03 Process Exit Code: (1)
12:01:13 Error running script: upgrade.sql (1)
12:01:13 C:\TEMP\_ISTMP7.DIR\scm.exe -Silent 1 -Action 6 -Service MSSQLServer
12:01:33 Process Exit Code: (0)
12:01:33 C:\TEMP\_ISTMP7.DIR\scm.exe -Silent 1 -Action 6 -Service MSSQLServer
12:01:43 Process Exit Code: (0)
12:01:45 An error occurred when running the upgrade on your server.
12:01:45 Installation Failed.

The Upgrade.out file found in the \Mssql7\Install directory also contains the
following error message:

Login failed for user 'username'

CAUSE
=====

Just before the setup attempts to run the SQL Server script files, it puts SQL
Server in single user mode. If there are any applications or processes that
automatically connect to SQL Server after it starts, they use up the single
available connection before the setup process can connect to SQL Server. This
prevents the SQL Server script file from running and causes the error message to
occur.

WORKAROUND
==========

WARNING: Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that
problems resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it. If
you are running Windows NT or Windows 2000, you should also update your
Emergency Repair Disk (ERD).
To work around this problem, follow these steps:

1. Delete the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\"Resume"

2. Rename the Sqlsp.log file located in the temp directory of the computer on
which the service pack setup was run.

3. In Control Panel, double-click Services. Stop all services and set them to
manual, except the following:

- Alerter
- Computer Browser
- Event Log
- License Logging Service
- Messenger
- Net Logon
- NT LM Security Support Provider
- Plug and Play
- Remote Procedure Call (RPC) Locator
- Remote Procedure Call (RPC) Service
- Server
- Spooler
- TCP/IP NetBIOS Helper
- Time Service
- Workstation

4. Close all applications that might be open, including Microsoft Internet
Information Server (IIS), BackupExec, NEtIQ, and Microsoft Systems Management
Server (SMS).

5. Restart the computer, and then log on with an account that has Local
Administrator privileges for that computer. Run the service pack
installation. If the setup still fails, repeat the preceding steps and
continue with step 6.

6. Disconnect the computer from the network.

If you are unable to disconnect the computer from the network, try to identify
which application or user is logging on to SQL Server when it starts by using
these steps:

1. To enable auditing in the SQL Enterprise Manager, from the Tools menu,
click SQL Server Configuration Properties, and then click Security.

2. Under Audit Level, select All to audit both successful and failed login
attempts.

This inserts an entry in the SQL Server error log and Microsoft Windows NT
Application Log for each login attempt with the userid of the user.

NOTE: You should turn Auditing off when it is no longer required because it can
cause the SQL Server error log and Windows NT Application Log to fill up.

7. Run the SQL Server Service Pack setup again.

MORE INFORMATION
================

Another situation in which this error occurs is when the BUILTIN/Administrators
login is missing in SQL Server or is not part of the sysadmin role. This happens
because, during installation, the setup program launches Upgrade.sql using an
ISQL-trusted connection, and the BUILTIN/Administrators group is used to grant
to the members of the Windows NT 4.0 or Windows 2000 local administrators group.

Additional query words: sp sp2 sp3

======================================================================
Keywords : kbSQLServ700sp2
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ700SP2 kbSQLServ700SP3
Version : :7.0 Service Pack 2,7.0 Service Pack 3
Issue type : kbprb
=============================================================================
Copyright Microsoft Corporation 2001.

Hope it helps you.

quote:
I don't suffer from insanty, I enjoy every second of it

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources