Re: SQL Service Pack doesn't upgrade SQL Server

From: Chip Andrews (chipandrews@usa.net)
Date: 03/13/03

  • Next message: Willis Johnson: "RE: SQL Service Pack doesn't upgrade SQL Server" 
    From: "Chip Andrews" <chipandrews@usa.net>
To: "Gregory D. Hess" <gdh@fsproduce.com>, "Focus-Ms (E-mail)" <focus-ms@securityfocus.com>
Date: Wed, 12 Mar 2003 19:14:12 -0500

    Gregory,

    Check the %windir%\sqlsp.log file for errors as well as the Event Log.

    Is there any reason you chose SQL Auth (you may have botched the password)?
    You can always install the service pack using Windows Auth while logged in
    as Administrator (assuming you haven't revoked/removed the local
    Administrators groups from the System Administrators role).

    Chip Andrews
    www.sqlsecurity.com

    ----- Original Message -----
    From: "Gregory D. Hess" <gdh@fsproduce.com>
    To: "Focus-Ms (E-mail)" <focus-ms@securityfocus.com>
    Sent: Wednesday, March 12, 2003 4:20 PM
    Subject: SQL Service Pack doesn't upgrade SQL Server

    I am trying to upgrade an SQL Server 2000 Standard Edition from RTM to
    service pack 3. I downloaded and extracted the files, backed up the
    databases and shutdown SQL Server. Then I ran x86\setup\setupsql.exe as
    directed in the SP3 Readme file. After setup was complete I was asked to
    reboot the server. When it came back up I checked the version, and it is
    still at RTM (8.00.194). I received no errors during the install that would
    suggest that the upgrade was not successful, yet for some reason it was. I
    also tried upgrading to SP1, and got the same results.

    For the Authentication mode I used SQL authentication and gave the sa
    password. The server is a W2k Domain Controller on Windows service pack 3.
    There is only one SQL Server instance on this computer.

    What would cause the SQL service pack not to install?

    -Greg Hess

    ----------------------------------------------------------------------
    ALERT: How a Hacker Uses SQL Injection to Steal Your SQL Data!
    It's as simple as placing additional SQL commands into a Web Form input
    box giving hackers complete access to all your backend systems!
    http://www.spidynamics.com/mktg/sqlinjection33

  • Next message: Willis Johnson: "RE: SQL Service Pack doesn't upgrade SQL Server"

    Relevant Pages

    • Re: SQL Server Std over SBS 2003 std
      ... What Henry is referring to is that SBS2003 Premium comes with SQL2000 ... Sorry if I sound dumb but SQL is a whole new topic for me. ... You could just install SQL Server std on the SBS Box (that is what an ... You could also upgrade to SBS 3002 R2 Premium with SQL Server 2005 ...
      (microsoft.public.windows.server.sbs)
    • Re: Sharepoint Upgrade to SQL Server Halts at Setup is Preparing to Copy Files
      ... associated SQL Agents/dependant services and then start the upgrade or 2) ... Once the other instances are stopped see if the setup continues.. ... > We already have SQL Server installed on our server prior to this upgrade, ...
      (microsoft.public.windows.server.sbs)
    • Re: Update MSDE2000 to SQL2000 on same server
      ... Yes you do an upgrade from MSDE to SQL 2000 Enterprise. ... a full database backup of all databases. ... Step 2 Click SQL Server 2000 Components. ...
      (microsoft.public.sqlserver.setup)
    • RE: SBS 2003 Unable to connect to database STS_Config
      ... MSDE to store SharePoint uses the MSSQL$SharePoint database, ... SharePoint named instance to full SQL. ... You cannot upgrade the Monitoring instance to SQL ... What I see is the SQL server group and under ...
      (microsoft.public.windows.server.sbs)
    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
      (microsoft.public.sqlserver.connect)