We have some "old" servers that are still running SQL 2000 (for various reasons). They have been updated to service pack 4.
In the SQL admin tool, the version number is reported as 8.00.2040. In Windows (Add/Remove Programs list), the version is reported as 8.00.2039. Altiris also sees the version as 2039 since it is reading the Add/Remove list.
Hi, I am trying to install the service pack 3 for sql server 2000 but cannot do it. I keep getting stuck at the screen where it asks u for the windows authentication or the sa password.
I select the sa password option and enter the password but it gives me an error saying that it was unable to connect.
I have msde version 8.00.534 that is sp2 I think. When I attempt to upgrade to sp3a I get: “The instance name specified is invalid� . I am working with win XP home edition that include IIS. Have some suggestions? Thanks
I have msde version 8.00.534 that is sp2 I think. When I attempt to upgrade to sp3a I get: “The instance name specified is invalid� . I am working with win XP home edition that include IIS. Have some suggestions? Thanks
We are having trouble installing SQL2000 service pack 4 on our server. The package runs through and looks like it installs files to c:, but the install never asks us for any of the questions regarding the install of service pack 4. One issue we were thinking about was that MSDE was installed on the server also. We have a 2003 server with SQL 2000 sp3 (8.00.760)
1) Sql2ksp3.exe. Updates for database components. 2) Sql2kasp3.exe. Updates for Analysis Services components. 3) Sql2kdesksp3.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000).
Number 2 makes perfect sense. Analysis Services is separate from the rest of the database.
What is the difference between 1 & 3? What is the Desktop Engine, how do I know if I'm using it, and how do I know if it has already been patched?
I'm trying to install Service Pack 4 to our default instance of SQL Server 2000 with SP3a, on a Windows 2003 Server, which also has a named instance of SQL Server 2005 on it and a named instance of SQL Server 2000 with SP4.
The installation appears to be running just fine, but MUCH too quickly. The last window appears stating something along the lines of 'Updating Active X components'. I'm expecting the scripts to run to update my system stored procedures, etc., but that never occurs. The installer just quits.
No errors in the Windows logs, nor in SQL, and no C:WindowsSQLSP.log file.
I tried the installation again, but this time used a different copy of the service pack 4 installer, with the same results, and again no SQLSP.log file.
Since I was going to remove the named instance of SQL Server 2000 anyway, I verified that my SP4 installer was good by uninstalling the named instance of SQL Server (the one with SP4 already), reinstalling a named instance of SQL Server 2000, and reapplying SP4 to this named instance. Everything went flawlessly.
I then tried reapplying SP4 to the default instance of SQL Server 2000, and this time a SQLSP.log file was finally generated. In the error log, the last entries are:
19:10:03 C:PROGRA~1COMMON~1MICROS~1SQLDEB~1SQLDBR~1.EXE sqldbreg2.exe -RegServer 19:10:04 An error occurred while setting the registry value for: SoftwareMicrosoftMSSQLServerMSSQLServer 19:10:04 Could not restore AuditLevel registry key 19:10:04 Action CleanUpInstall: 19:10:04 Installation Failed.
I confirmed that the service accounts that are running SQL Server both have local administrative access to the server (which may or may not matter), and that they are both sysadmin, so I don't think it's a permissions issue to the registry. I've also verified that the account I was using to run the SP installation also has local admin access on that box.
So, I compared my HKLMSoftwareMicrosoftMSSQLServerMSSQLServer registry entry from our production server to the one on the test server, I see that our test server's entry is completely empty. On production there are numerous subkeys, such as CurrentVersion and RPCNetLib.
I'm planning on copying the registry entries from production to test. Should this be sufficient, or are there other things I should look out for?
I have an installation of SQL Server 2000. Both MBSA and @@versionshow this to be the gold release. When I install Service Pack 3a, itshows no error. But after restart of the server, it's still unpatched,by both MBSA and @@version.Any idea what may be going on here?
I have been asked to provide a SQL Server 2000 Service Pack 4 validation procedure... I have been unable to locate any reference to how this can be validated in either the program itself or in the registry... Any help is appreciated...
I am trying to install Service Pack 4 to set up the SQL Server 2000 but I am having problem. When I clicked the setup.bat, the screen just "froze" with the message " validating user. Please wait..."
We had a disaster last week (SAN Corruption) and it hit a bunch of my sql serves. I have been able to recover all but one. The one I am having a problem with is a NAMED Instance that I obviously don't know the original SP level on. When I try to restore MSDB it won't let me because of a version conflict Is there any way to tell what the SP Level is either from a system DB .mdf or LDF file or from a backup file without restoreing? Right now I'm installing SQL Server to a test server and I'm going to try and restore the system dbs at each patch level.. seems like there must be a better way!!
Hi, i tried to install SQL Server 2000 Developer and MSDE the whole day on my Windows XP SP2. MDAC is the latest, that come with WinXP SP2 (2.81). The installation fails at the end after 100% complete.
It says: Translated: "the setup programm starts the server and installs the configuration you chose..." ("das setup-programm startet den server und installiert die von ihnen gewählte konfiguration...")
then it takes some time and the failure appears, saying: "the setup programm could not configure the server. you can find more information in the server-failure-log files and in "C:windowssqlstp.log."
Does Anyone know if there is a way to verify the SQL Service Pack Version on 7.0 on Windows 2000 Advanced server?
I'm getting this results for select @@version
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 1)
I installed Service Pack 5 on SQL 7.0 successfully, but when I go back to run @@version, it gives me Service Pack 2 which is the old pack. Does anyone know why and had an experience with this?? Thanks wonderful people!!!
I have a cluster server, with SP3 coming out I wanted to upgrade the SP2 I have right now, when I start SP3 installation it starts and quickly exits from the program. DO I need to uncluster the server before applying SP3? or there is a way arround it?
has anyone had this experience before after we installed service pack 2 our jobs are taking about 10hrs, some run it says it's succesfull but it didn't update the tables.
I have installed service pack-1 on SQL SERVER 7.0 Standard Edition. After the pack is installed @@version is still showing 7.00.623 instead of 7.00.699 HELP !!!
Does anyone else have any concern about this Watson technology creeping in to SQL Server in SP3? I don't like it in Explorer and I'm sure not going to like it in SQL Server!
BTW, Forrest article about the new security patches at http://www.databasejournal.com/news/article.php/1475241 is in error, I think, when it refers to SP4.
Is the sql server 2000 service pack 3 worth applying to production database server or should I still wait. i do have sql 2000 service pack 2 on the server ?