November 23, 2009 at 9:44 am
Hi,
I ran the SP3 for a 64-bit server to upgrade my SQL Server 2005 64-bit install. This is on a Windows 2003 R2 64-bit server. After the install, I see that the SP3 64-bit fails to install BackupExec 32-bit version. Log file is below.
It appears that the 64-bit version SP3 for SQL Server is trying to upgrade the 32-bit version of BackupExec. How can upgrade BackupExec, so the SP3 install is successful?
----------------------------------------------------------------------------------
Product : Database Services (BKUPEXEC)
Product Version (Previous): 4053
Product Version (Final) :
Status : NA
Log File :
SQL Express Features :
Error Description : Setup cannot update Database Services x86 on this computer. To proceed, run the Service Pack Setup program for the x86 platform instead.
November 24, 2009 at 5:28 am
I found this for you, though not sure if it will work. Here's a link to the thread in case you want to see the whole discussion http://www.symantec.com/connect/forums/security-update-sql-server-2005-service-pack-3-kb970892-fails-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:
* Open the Programs and Features (Add/Remove Programs) control panel.
* Select Microsoft SQL Server 2005, and click Change.
* Select the database engine component.
* Allow the system configuration check to complete.
* Then choose Complete the suspended installation.
* You may get the error message "The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package "SqlRun_SQL.msi" in the box below." This means that the installer needs access to the original installation files.
o In this case download SQL Express 2005 SP3 from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6.
o Execute SQLEXPR.EXE /x and extract the installation files to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Baseline Cache\Express\SP3. This is the location recommended by the article http://support.microsoft.com/kb/955250/, but the location may not really matter.
o Provide the Setup subdirectory of this path in response to the error dialog above.
* Installation will continue, but you may encounter an additional 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."
o To correct this problem, open the Registry Editor.
o Locate the key HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters. Note that it may be MSSQL.2 or some other instance number instead of 1. For x86 operating systems, omit Wow6432Node from the registry path.
o Create a string (REG_SZ) value named SQLArg3 and set the data to "-T4606" (no quotes).
o In response to the error message, cancel the installation and allow it to roll back. Then try the installation again.
* Once the suspended installation of SQL Express 2005 SP3 runs to a successful completion, the KB970892 security patch should install successfully.
* You will need to start up the Backup Exec services after the patch installation.
I'll be interested to hear how this works for others.
November 24, 2009 at 10:20 am
Does this apply to SQL Server 2005 Standard Edition on 64-bit servers? You post mentions fixing the SQL Server Express edition. Sorry for not making this clear in my post.
November 24, 2009 at 10:26 am
What version of BackupExec? Is BE updated to the latest patch?
Those pieces of information are also necessary to try to find a matching resolution for you.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 24, 2009 at 11:08 am
Hi,
Current version of Backup Exec on the server is 12 rev 1364?
Do you know what version Backup Exec is in the SP3? I can run updates for Symantec Backup Exec. Perhaps, this will allow SP3 to be succesful.
November 24, 2009 at 11:40 am
pbyrum (11/24/2009)
Hi,Current version of Backup Exec on the server is 12 rev 1364?
Do you know what version Backup Exec is in the SP3? I can run updates for Symantec Backup Exec. Perhaps, this will allow SP3 to be succesful.
I would start with checking for updates to BE. I also overlooked one tiny detail in your initial post. BE has installed SQL Express on your server alongside your Enterprise Edition install. You should take a look at the second post in this thread and try the fix suggested there.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 30, 2009 at 4:01 pm
What I did was use Windows Installer Cleanup Tool and the SQL Server Install program to remove Express from the server. I have not tried the SP3 upgrade, yet.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply