Backup Exec 2010 Odbc Access Error Catalog Error
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing
Odbc Access Error Backup Exec 2014
Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange backup exec 15 odbc access error Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español odbc access error backup exec 2010 USA Site: Veritas Veritas PartnerNet Getting "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting Backup
Catrebuildindex -r
Exec Services. Article:000083813 Publish: Article URL:http://www.veritas.com/docs/000083813 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article
Event Id 34326 Backup Exec
Languages Subscribe to this Article Manage your Subscriptions Problem After restarting the Backup Exec services lots of "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" is received in the Application Log and also similar alerts are generated in Alerts tab in Backup Exec. Error Message Application Log Errors: Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failed.Reason: D:\Catalogs\SERVER-NAME\{86794C68-8397-4F24-A2EA-404B54FED371}_31.xml PerformBulkInsert() e:\nicobar\5204r\becat\catindex\dll\..\catdbupdatethread.cpp(447) Source: Backup ExecEvent ID: 34338Error : Backup Exec Alert: Catalog Error (Server: "SERVER-NAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failedReason:[Microsoft][ODBC SQL Server Driver][SQL Server]The INSERT statement conflicted with The FOREIGN KEY constraint "FK_CatImage_CatResource". The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'. cat_RecordSet::ExecuteBulkInsert() e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113) sp_sproc_columns CatImageInfoProc Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Er
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer v-280-2003 Center Support Community MyVeritas Customer Success Licensing Programs
Backup Exec 15 Catalog Error Odbc Access Error
Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec alert: https://www.veritas.com/support/en_US/article.TECH167225 Catalog Error - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Article:000025591 Publish: Article URL:http://www.veritas.com/docs/000025591 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome https://www.veritas.com/support/en_US/article.TECH231540 First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem After applying Feature Pack 1 for Backup Exec 15, alerts and Windows events may pop up related to Catalog Errors: Error Message NOTE: Only Catalog Error alerts beginning with the installation of Feature Pack 1 where Microsoft Exchange backups are performed are applicable to this Technote. Backup Exec Alert: Catalog ErrorMessage: ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Two Windows events will accompany the alert in Backup Exec. The first is a generic ODBC event: Log Name: ApplicationSource: Backup ExecEvent ID: 34338Task Category: NoneLevel: ErrorKeywor
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign https://vox.veritas.com/t5/Backup-Exec/ODBC-access-error-BackupExec-Catalog-not-accessible-after-BE/td-p/689919 In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. https://community.spiceworks.com/topic/594264-backup-exec-a-problematic-child Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : ODBC access error / BackupExec Catalog not accessi... VOX : Backup backup exec and Recovery : Backup Exec : ODBC access error / BackupExec Catalog not accessi... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page ODBC access error / BackupExec Catalog not accessible after BE 2012 SP4 Upgrade JackEmu Level 2 Partner Accredited 03-20-2014 04:37 AM Options odbc access error Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 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:pen() r:\honshu\1798.1364r\becat\segodbc\seg_odbc.cpp(2538) {CALL UpdateCatMediaInfoForDriveLetterChanged( ?, ?, ?, ?) } Tried to reset catalog, no success either. Seems like SQL procedureis missing in SP4!? Labels: 2012 Backup and Recovery Backup Exec Error messages Troubleshooting Upgrade Windows Server (2003-2008) 0 Kudos Reply 3 Replies Hello Jack, Can you confirm Siddhant_Saini Level 6 Accredited Certified 03-20-2014 04:46 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello Jack, Can you confirm if it is Backup Exec 2010 R3 SP4 or B
failing. We needed a replacement, but we didn't have a budget set aside for it. I had to get creative, and I had to keep costs to a minimum. Rewire project LEA funded electrical rewire. But let's not waste the change to make some changes! New file server Plan, Build and deploy a new file server IN THIS DISCUSSION Novastor Veeam Backup & Replication Unitrends Symantec Backup Exec Dell powervault 124t BackupAssist by Cortex I.T Labs Unitrends 4299 Followers Follow Symantec 258197 Followers Follow BackupAssist 1028 Followers Follow RobT64 69 Followers Join the Community! Creating your account only takes a few minutes. Join Now rant I am getting sick of our backup solution including BE2012. It's always a hassle to make things work. Every week it's a battle to get everything backed-up. The few weeks per year that all backups succeed it's a great relief. Shouldn't it be the other way around ? I should be very surprised when things fail ... over here I am surprised if it actually worked the way it's intended to work. I'm sick of this erratical childish behaviour of my backup system !!! Aaaaaaaaaaahhhhhhhhhhh ! /rant Seriously , I'm getting errors , jobs keeping running , part of a newly created job not appearing in the jobs list (so I can't even start it) , stupid error messages when taking a regular (successfull) backup , the BU software not updating to the latest SP , tape drive keeps asking for cleaning even when a schedule is in place (OK , this one may be Dell's fault) , ... . On average it almost takes me half a day up to a day's work PER WEEK to get the backup $*£%#@ like it should. What do you use ? How much work is it for you to maintain ? Tags: Symantec Backup ExecReview it: