JayBios
11 years agoLevel 2
BE2012 - SP3 Install fails
I'm having a headache trying to get backup exec to install SP3. It gets to the end and then rolls back the install.
The most information i've got on this error is from the bkuptemp.log it creates while installed the service pack, the area it's failing at is this:
<logdata>
<caller>0</caller>
<type>0</type>
<datetime>01-15-2014,10:16:11 </datetime>
<msg>Connected to SQL Server BACKUP.</msg>
</logdata>
<logdata>
<caller>0</caller>
<type>2</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>V-225-205: ERROR -1: The OLE DB provider "SQLNCLI10" for linked server "BESERVER_DB" does not contain the table ""BEDB"."dbo"."vwGetJobHistoryResourceContainerMapping"". The table either does not exist or the current user does not have permissions on that table.
***To search for information about this error, click <a href="http://entsupport.symantec.com/umi/V-225-205" target="main">here </a> </msg>
</logdata>
<logdata>
<caller>0</caller>
<type>0</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>CREATE PROCEDURE [dbo].[ReportFailedJobs] ( @protected_srv_names nvarchar(4000) = '', @numdays_befor</msg>
</logdata>
<logdata>
<caller>0</caller>
<type>2</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>ERROR: -1 - Failed to execute dbupgradebuildtobuild.sql.</msg>
</logdata>
<logdata>
<caller>0</caller>
<type>1</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>dbupgradebuildtobuild.sql changes did not complete successfully. Database schema may have been modified by this patch.</msg>
</logdata>
<logdata>
<caller>0</caller>
<type>2</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process. ***To search for information about this error, click <a href="http://entsupport.symantec.com/umi/V-225-1000" target="main">here </a> </msg>
</logdata>
<logdata>
<caller>0</caller>
<type>0</type>
<datetime>01-15-2014,10:16:26 </datetime>
<msg>CustomAction PatchBEDBData returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)</msg>
</logdata>
Previously i was getting an error which complained about not being able to login for user "NT AUTHORITY\ANONYMOUS LOGON" I since added this as an SQL user and then i got the error above. Any ideas?
See if this KB helps - http://www.symantec.com/business/support/index?page=content&id=TECH212637