Backup Exec Odbc Access Error Possible Lost Connection To Database
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community odbc access error possible lost connection to database backup exec 2015 MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About
Backup Exec Odbc Access Error. Possible Loss Connection
Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English odbc access error backup exec 2012 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Getting "ODBC access error. Possible lost connection to database or odbc access error possible lost connection to database or unsuccessful access to catalog index in the database unsuccessful access to catalog index in the database" on restarting Backup 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
Odbc Access Error Backup Exec 2014
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 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) failedRea
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer odbc access error backup exec 2010 Center Support Community MyVeritas Customer Success Licensing Programs Licensing backup exec 15 odbc access error Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers
Event Id 34326 Backup Exec
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec alert: Catalog https://www.veritas.com/support/en_US/article.TECH167225 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 First https://www.veritas.com/support/en_US/article.TECH231540 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: ErrorKeywords: ClassicDescription:Backup Exec Alert:
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-in-BE-2014/td-p/701163 In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you http://www.bengtsblogg.se/index.php?id=24&tx_ttnews%5Btt_news%5D=243&cHash=0f3469bb8b type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : ODBC access error in BE 2014 VOX : Backup and Recovery backup exec : Backup Exec : ODBC access error in BE 2014 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution ODBC access error in BE 2014 nackros Level 4 Partner Accredited 02-11-2015 12:50 AM Options Mark as New Bookmark Subscribe Subscribe to odbc access error RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, I´m getting lots of error messages that says: "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database". And this is paired with this error message in the Windows event log: Access to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot find either column "dbo" or the user-defined function or aggregate "dbo.fCatLogMsg", or the name is ambiguous. CCatRecordSet:pen r:\columbuscft_sp\1786.1059r\becat\segodbc\seg_odbc.cpp(1889) { CALL DeleteCatMediaByMediaGuid( ?, ?, ? ) } ;---- I would really like to get rid of this error. Now, the backups works for the most part, but sometimes they hang and I relate that to the extreme amount of these ODBC error. If I then restart(often using Task Manager for the Job engine) the services the backups resume. The server has been migrated from another BE2014SP1 server. And lots of other articles about this error seems to be related to an upgrade or migration. when I did the migration I followed a