Microsoft KB Archive/891085

= FIX: You receive an error message when you try to install SQL Server 2000 Service Pack 4 =

Article ID: 891085

Article Last Modified on 1/16/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



BUG #: 473161 (SQL Server 8.0)



Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.



SYMPTOMS
When you try to install Microsoft SQL Server 2000 Service Pack 4 (SP4), you see the '''Validating user. Please wait.''' dialog box during the installation. When SQL Server Setup tries to perform this step, you receive the following error message:

Setup was unable to validate the logged on user. Press Retry to enter another option, or Cancel to exit setup.

When you click Retry, you receive the same error message. When you click Cancel, you receive the following error message:

Setup was unable to verify the state of the server for an upgrade. Verify the server is able to start and that you provided a valid sa password and restart setup.



CAUSE
This problem occurs when an open local shared memory connection is pending when the Setup program starts. When you install SQL Server 2000 SP4, the Setup program stops the SQL Server 2000 services. If a local shared memory connection is pending, the local shared memory listener does not successfully start after the SQL Server 2000 services are restarted.

When the application or service that has the local shared memory connection is on the same computer as an instance of SQL Server, Microsoft Windows interprocess communication (IPC) components are used for the connection. Local named pipes and local shared memory are examples of Windows IPC components. For example, you may experience this problem if you installed Microsoft SQL Server 2000 Reporting Services on the same computer that is running SQL Server.

Note To verify that SQL Server listens on the local shared memory protocol, examine the SQL Server error logs. A message that is similar to the following is logged in the error logs:

2004-11-09 20:22:18.64 server SQL server listening on TCP, Named Pipes.



WORKAROUND
To work around this problem, close all applications that have a local shared memory connection to SQL Server before you install SQL Server 2000 SP4. For example, if Reporting Services is installed on the same computer that is running SQL Server, stop the Reporting Services ReportServer service before you install the service pack. To do this, follow these steps:  Click Start, click Run, type cmd in the Open box, and then click OK. Type the following command at the command prompt, and then press ENTER to stop the ReportServer service:

net stop ReportServer

 At the command prompt, type exit .

After you install SQL Server 2000 SP4, restart the ReportServer service. To do this, follow these steps:  Click Start, click Run, type cmd in the Open box, and then click OK. Type the following command at the command prompt, and then press ENTER to restart the ReportServer service:

net start ReportServer

</li> At the command prompt, type exit .</li></ol>

Note Restarting the computer before you install SQL Server 2000 SP4 may not resolve the problem. This will not resolve the problem because some of the services that connect to SQL Server have a startup type that is set to Automatic.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

Steps to reproduce the problem

 * 1) Install SQL Server 2000.
 * 2) Install SQL Server 2000 SP3a.
 * 3) Install Reporting Services.
 * 4) Install SQL Server 2000 SP4.

<div class="references_section">