cancel
Showing results for 
Search instead for 
Did you mean: 

ODBC access error / BackupExec Catalog not accessible after BE 2012 SP4 Upgrade

JackEmu
Level 2
Partner Accredited

After Upgrade with SP4 for BE 2012 Catalog is not working and thus also restore operations.

Error in Event Log:

 

Backup Exec Alert: Catalog Error

(Server: "SERVERNAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.

Followed by:

 

Access to catalog index (Catalog index database) failed.

Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'UpdateCatMediaInfoForDriveLetterChanged'. cat_RecordSet::Open()

r:\honshu\1798.1364r\becat\segodbc\seg_odbc.cpp(2538)

{CALL UpdateCatMediaInfoForDriveLetterChanged( ?, ?, ?, ?) }

 

Tried to reset catalog, no success either. Seems like SQL procedure is missing in SP4 !?

 

3 REPLIES 3

Siddhant_Saini
Level 6
Accredited Certified

Hello Jack,

Can you confirm if it is Backup Exec 2010 R3 SP4 or Backup Exec 2012 SP4(The product you selected is Backup Exec 2012 whereas the heading is Backup Exec 2010)? If it is BE2012 SP4 then is your Backup Exec Database located on a Remote SQL server? If yes, then refer to the following article and please open a case with us for a possible workaround: http://www.symantec.com/docs/TECH215936

JackEmu
Level 2
Partner Accredited

Hi Saini

Thank you for answering; we already proceed according to that acrticle (before resetting the catalog which means having to catalog every media again), no success.

To answer the question: no, database is located on be server with default naming.

To go further: the sql error is also referencing another stored procedure which I think is the root of the problem: Could not find stored procedure 'UpdateCatMediaInfoForDriveLetterChanged'

Edit: sorry for misleading title: it is regarding BE 2012!

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Suggest you log a formal support case for us to investigate - it might still relate to the condition in the Tech article provided earlier but sounds like it does need a more thorough look.