10-17-2009 07:49 AM
Solved! Go to Solution.
10-24-2009 01:46 PM
10-26-2009 12:14 AM
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
10-29-2009 03:50 AM
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
11-03-2009 11:55 AM
11-18-2009 11:26 AM
12-28-2009 07:39 AM
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
12-31-2009 10:45 AM
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.
02-17-2010 08:45 PM
02-18-2010 10:03 AM
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 ...)
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