Security Update for SQL Server 2005 Service Pack 3 (KB970892) fails to install
Microsoft released Security Update for SQL Server 2005 Service Pack 3 (KB970892) on October patch Tuesday. It fails to install on the SQL Express 2005 SP3 x64 BKUPEXEC instances on two of my my BEWS 12.5 SP2 media servers, as well as on a couple of other servers running SQL Express 2005 SP3 with other products, e.g. VMware vCenter Server, HP Digital Sending Software 4.0. Various forum posts found by Google suggest that having any of the SQL Server services disabled may cause this problem. In my case, the only disabled service is SQL Server Active Directory Helper. This service can be set to manual, but it will not start, and just setting it to manual doesn't solve the problem. These posts also suggest that having the SQL Server program folder compressed can cause the error, but this is not applicable to my situation.
I took a look at the Windows Update log and other than an error message with the return code 0x0000737d, I didn't see any useful information. I also looked at the hotfix installation log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB970892_sqlrun_sql.msp.log, and found the error message: "Error 29565. SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete. Start the Remote Registry service and go to Add/Remove Programs, select the Change button for Microsoft SQL Server 2005, and then select SQL instance HPDSDB and complete the setup."
The description of this security update at http://support.microsoft.com/kb/970892, in the More Information section, lists four TechNet articles with troubleshooting procedures for known issues. Article 955250 seems like it may be applicable, although the error message doesn't match. I'm still trying to work through this.
The security update is available at http://www.microsoft.com/downloads/details.aspx?familyid=0d878f4b-71e8-4170-9a14-1bce684811ce&displaylang=en for anybody who does not wish to rely on Windows Update.
Thanks for any additional thoughts that anyone may have.
Comments
In the error message, it has
In the error message, it has something about HPDSDB instance. Is this the name of your server, check if it has some instance by this name. It is not the bkupexec instance, but this other instance of SQL server on the machine, which appears to cause the issue. you may want to check if this service exists on the SQL server. If not, it could be some incomplete uninstall of SQL server from the past.
Thanks
The HBDSDB instance is from a
The HBDSDB instance is from a different server (HP Digital Sender Service 4.0). The instance names on the two Backup Exec media servers are both BKUPEXEC. The errors that occur are otherwise the same in any event. I don't think the problem is related to Backup Exec specifically, but is a general problem with the KB970892 patch and SQL 2005 Express SP3. I have a tech support case open with Microsoft and will post any useful results here. Thanks.
Hi jaspain, I am in the same
Hi jaspain, I am in the same situation. Please post the solution, once found, because it will be very helpful to all us.
Did someone try this: http://support.microsoft.com/kb/971818
Repair the SQL Server 2005 instance by using Add or Remove Programs in Control Panel. To do this, follow these steps:
Thanks for help and regards.
F.
I tried the KB971818
I tried the KB971818 workaround to no avail. First the "Complete the suspended installation" procedure got stuck because the SQL Express SP3 installation files were not available. When I supplied those, it proceeded further, but then failed with the error: "[Microsoft][SQL Native Client][SQL Server] Password Validation failed. The password does not meet the Windows policy requirements because it is too short.. To continue, correct the problem, and then run SQL Server Setup again." It isn't clear which password it is complaining about. I was logged in with a domain user account which is a local administrator in one instance, and a domain administrator account in the other instances. Those account passwords, of course, meet the length criterion specified by group policy on the domain. The databases are operating in Windows Authentication mode. Still awaiting further word from Microsoft Tech Support. Thanks. Jeff.
When it asks for a password,
When it asks for a password, use a complex password and complete the SP3 install. Once done, you may try applying this hotfix again.
Thanks
It does not prompt for a
It does not prompt for a password it just fails during repair of sql express. Attached is screenshot. How do we fix this when all of this was setup during Beckup Exec install by default?
FIXED - http://davehope.co.uk/Blog/kb970892-fails-to-install/
I can tell you there is a
I can tell you there is a issue here. I have 3 2003 SBSR2 with 12.5 BupEXEC and a 203 R2 Ent, again 12.5 and they all exhibit this issue with the BACKUPEXEC instance on this hotfix. More confusing is the posted update that SQL 2005 Express Edition with SP3 is NOT affected. so it is confusing as to if this is required or not. Neither Symantec or Microsft seem to be able to clarify this.
Microsoft Being Unhelpful
Microsoft is declining to provide support because we are running Backup Exec in a VMware environment. If anybody is having this problem on a physical machine and is in a position to work on it with Microsoft, please let us all know the outcome.
Problem occurs on physical machines too
Jeff,
I have several clients running BackupExec on physical boxes and am seeing exactly the same problem on at least 3 of those machines. My only solution at present is to block that particular update -- not perfect, I know but better than the alternative until Microsoft gets its act together.
Same issue here
My BE server is running on a physical device running Windows Sever 2003 x64 and I'm getting exactly the same errors. Most annoyingly the Backup Exec servers stay done after the update fails, so the schedule of the backups is stuck. I'll block the update for now and hope we'll find a fix ASAP.
Greetings
Same problem here also...
Running the same configuration as cpegel :-(
Richard
Fabri_Fabri had the fix for mine
I went through the process in Fabri_Fabri's message and it corrected the issue for my server. I did have to go to Microsoft and download the free SQL Server 2005 for 64 bit to complete the process as it was looking for the install files to do the repair.
Once I did that I was able to install the update that was failing, and backup services are working normally again!
Fabri fix attempted
When I try Fabri's fix I get the prompt as posted above. Any resultion to that?
Fix for Password
Here is the link that helped me with my password prompt issue.
http://davehope.co.uk/Blog/kb970892-fails-to-install/
Microsoft's Fix
First of all, Microsoft has clarified its support policy, and SQL Express 2005 is supported in our virtual environment on a Windows Server 2008 SP2 x64 guest and VMware vSphere host. Microsoft has a helpful reference as to exactly which virtualized environments they will support. See the Server Virtualization Validation Program wizard at http://www.windowsservercatalog.com/svvp.aspx?svvppage=svvpwizard.htm.
In this case Microsoft made the following recommendation, which did successfully resolve the issue. To summarize the problem, the security update KB970892 failed to install because the original installation of SQL Express 2005 SP3 did not run to a final completion, even though there was no indication of any problem during the original installation process.
The fix is as follows:
I'll be interested to hear how this works for others.
Jaspain's fix took care of the problem.
Jaspain your "Microsof'ts Fix" was the silver-bullet. Thank you.
Tom
...seems to work...
...seems to work...
Unexpected error Setting Internal Properties
Same problem on a physical machine. When I follow the procedure above instead of a password error I get: "The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation." I tried the Password validation hack, but still get the same error. Any suggestions?
A little more information on my error from the logs.
Microsoft SQL Server 2005 9.00.4035.00
==============================
OS Version : Microsoft Windows Server 2003 family, Service Pack 2 (Build 3790)
Time : Sat Oct 24 06:34:12 2009
Machine : SERVER2
Product : SQL Server Database Services
Error : The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
--------------------------------------------------------------------------------
Machine : SERVER2
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.3.4035.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0009_CNSPPCDC2_SQL.log
Last Action : SetInstanceProperty
Error String : The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Error Number : 29528
--------------------------------------------------------------------------------
Fix - Security Update for SQL Service Pack 3
Hey all,
If there is no option available in the SQL Server 2005 system configuration to complete the suspended installation, then you should try the fix below:
I copied this from another discussion group and it worked on my computer. I am running XP Professional.
To resolve this issue, do the following:
1. Go to Run, type regedit, and click ok, or press Enter.
2. Back up your registry, if you don't know how to do this, google it...
3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\Setup]
[Note that if you have multiple instances of MSSQL installed, the reg key
might be different for you]
4. find the Resume REG_DWORD, and change its decimal value from 1, to 0.
5. install the update, and restart the machine.
If you don't want to install this update using the automatic update
(WUAUCLT), you can download the hotfix directly from microsoft, just google
"download KB970892 ". you will still need to manually change the registy
"Resume" value, or else the hotfix will fail to install.
Best of luck!
P.S. This is a lot faster and easier than calling Microsoft Customer Support. Trust me, I tried. Three times.
-- Nicholas DiDonna --
Possible Fix for error setting internal properties
http://seer.entsupport.symantec.com/docs/312651.htm
Will try this fix when the backups finish. Nicholas, thanks for the post. Will give the resume hack a shot if the hack above doesn't work.
Re-deux: Here's the fix.
EVERYONE, TRY THIS SOLUTION!
Here's the article that bascially helped me fix my Windows Server 2003 (32-bit) and Windows Server x64 Edition. To find it via searching look for "KB954606" or http://www.google.com/search?hl=en&source=hp&q=316661+site%3Asymantec.com&aq=f&oq=&aqi=
http://seer.entsupport.symantec.com/docs/316661.htm
Here are my steps that I do to make sure that things are going as planned... every step of the way. I know that some of the steps can be removed. But being detailed is good fro people who realle really want to know what's going on.
Issue:
Event ID: 20
Source: Windows Update Agent
Description: Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2005 Service Pack 3 (KB970892).
What you notice in the real world: Fails at 3am every day and leaves SQL Server in a stopped state which affects backups.
Resolution:
Have fun everyone.
Phydeaux
This worked for me
A bit on my environment first since this may not work for everyone. Windows 2008 64-bit, BE 12d, and the first time around we tried to fix it before I saw this thread it hosed our OS. So after a fresh re-install, and running into the same SQL patch issue this worked:
1. Installation failed from Windows Update (WSUS)
2. Modified this key (again ours is 64-bit) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1\Setup set Resume REG_DWORD=0.
3. Go through Programs and Features, Change SQL Server 2005, select the BackupExec instance and go through the motions of the install.
4. Go back to Windows Update and try patch again
5. Success
Solution works
Thanks guys for the post, this helped me solve the same exact issue. It was driving me nuts having that outstanding patch showing up.
Here is a little bit of our setup:
Windows 2008x64 BE 12.5 -- vanilla installs
SOLUTION:
2. Modified this key (again ours is 64-bit) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1\Setup set Resume REG_DWORD=0.
3. Go through Programs and Features, Change SQL Server 2005, select the BackupExec instance and go through the motions of the install.
4. Go back to Windows Update and try patch again
5. Success
Kudos and thanks
Gotta love it when scouring forums actually works!
Kudos to all who contributed and triple points should be awarded (IMHO) to jaspain for not only tenacity, but for ACTUALLY posting back the solution that worked for him (how many times have I heard that one before..."I'll post back what I find"....yeah right!).
FYI, I did confirm that you don't have to extract the downloaded SQLEXPR.EXE files to the recommended "C:" drive location. My installer was looking for location "E:\bde2dd924943a3a4cd161a9d05b1\setup" (where "setup" was actually one of the folders being extracted) so that's where I extracted the install files too, and the installation completed with no problems. In fact, I didn't have a problem with the password error either...coincidence? I don't know.
Anyway, thanks again for everyone posting about this.
--Futile
Fabri_Fabri had the
Fabri_Fabri had the instructions that worked for me!
Thanks for the details. I followed them, rebooted, installed the service pack and it worked the first time......sure was tired of looking at the install every day on my task bar.
Apply SQL Service Packs to any SQL Server with Backup Exec.
Hi
Does any body know if there is any impact if i install service packs or hotfix on the SQL Server Backup Exec instance?
or any web link that can help with this doubt.
Thanks
Richard, I haven't
Richard,
I haven't experienced any issues patching the SQL instance(s) for Backup Exec other than what was reported above. But then a few weeeks later we purchases a new agent and that caused a problem (see more details below). We've been using Microsoft Update to patch the server since Backup Exec version 10.0. I have no link to provide because most links are for issues not successes.
There is an issue with SQL (not to do with patching) if you add the VMware license (or 1 other license that we did not purchase) to an existing solution. The trick here is to install and patch SQL Server before installing (re-installing) Backup Exec.
Here's the case I opened (I could not find a (public) link):
From: enterprise_support@symantec.com [mailto:enterprise_support@symantec.com]
Sent: Wednesday, December 09, 2009 4:00 PM
To: X
Subject: Case 281-889-270 (V-225-53:Failed to install SQL Express BKUPEXEC Instance" that occurs when ...)
Workaround #1:
1. Save the Catalogs folder and MDF and LDF Database files for Backup Exec.
2. Uninstall Backup Exec.
3. Reinstall Backup Exec.
4. Apply the SQL Express SP3 by tech note 327649
5. Replace the Catalog folder and use Beutil.exe and Copy the DB to copy the MDF and LDF back into working install.
How to apply the SQL 2005 Express BKUPEXEC Service Pack 3 (SP3) Update to an existing installation of Backup Exec for Windows Servers
http://support.veritas.com/docs/327649
Technical Support Engineer
Backup Exec
Symantec Corporation
www.symantec.com
___________________________________
These are my more detailed notes for the same steps. Note that we do not use the default installation folders:
The best solution after uninstalling Backup Exec 12.5 and SQL Server 2005 Express Edition is to...
The bottom line is that now you have a surefire way to restore Backup Exec 12.5 (and I believe most other versions after Symantec took over) in case of a SQL error. I used this method 5 times. A 3 for practice and honing in the process and then 2 for real.
Phydeaux
Would you like to reply?
Login or Register to post your comment.