Backup Exec Odbc Access 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 12 Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange
Backup Exec Odbc Access Error Catalog Error
Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español
Fehler Bei Odbc Zugriff Backup Exec
USA Site: Veritas Veritas PartnerNet An alert 'ODBC access error' is observed every time the Backup Exec services start and the restore selections are not complete. Article:000040371
Backup Exec 15 Odbc Access Error
Publish: Article URL:http://www.veritas.com/docs/000040371 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 Article Languages Subscribe to this Article odbc access error backup exec 2015 Manage your Subscriptions Problem Every time Backup Exec (BE) services start, the following Errors are observed in the Alerts tab. (Figure 1). In addition, the restore selections may not be able to be browsed or may not be displayed at all when trying to create a new restore job. Error Message ODBC access error. Possible lost connection to database or unssuccessful access to catalog index in the database Figure 1: Cause This can occur due to connection issues to the Backup Exec database or corrupt catalogs in the Catalog folder. It can also occur after an upgrade of Backup Exec if the catalogs have not been upgraded completely from the past version. Solution 1. Backup Exec Database (BEDD) is hosted on an invalid SQL Instance. Solution: First make sure the SQL instance being used for the BEDB is a valid Instance. This by default is SQL Express but could be a full version of SQL
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 Process odbc access error backup exec 2010 ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations event id 34326 backup exec Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas catrebuildindex -r Veritas PartnerNet Backup Exec alert: Catalog Error - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Article:000025591 Publish: https://www.veritas.com/support/en_US/article.TECH75279 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 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 https://www.veritas.com/support/en_US/article.TECH231540 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: Catalog Error(Server: "SERVERNAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. This second is the unique event tied to this Technote issue. The highlighted text shows the key error: Log Name: ApplicationSource: Backup Exec CatErrorHandler ServerEvent ID: 34326Task Category: NoneLevel: ErrorKeywords: ClassicDescription:Access to catalog index (Catalog index database) failed.Reason: [Microsoft][ODBC SQL Server D
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 Process https://www.veritas.com/support/en_US/article.000013561 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: https://centosbeginer.wordpress.com/2011/07/12/symantec-exec-backup-error-catalog-after-upgrade-from-10-5d-to-12-5/ Veritas Veritas PartnerNet ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database alert appears during setcopy of a GRT backup exec enabled set post Hotfix 159965 for 2010 R3 Article:000013561 Publish: Article URL:http://www.veritas.com/docs/000013561 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 odbc access error Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Alert appears when GRT (Granular Restore Technology) set is duplicated from Deduplication folder or Backup to Disk Folder. Error Message Event Type: ErrorEvent Source: Backup Exec CatErrorHandler ServerEvent Category: NoneEvent ID: 34326Date: 8/30/2011Time: 1:35:45 PMUser: N/AComputer: SERVERX64 Backup Exec Alert:ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Cause This Issue was Introduced with Backup Exec 2010 R3 Hotfix 159965. The errors are cosmetic in nature. The backup completes and data can be restored from the duplicated set. Symantec recommends verifying this in your environment by performing a test restore from a duplicated set that generated this error message. Solution This issue has been resolved in Backup Exec 2010 R3 Service Pack 2http://www.symantec.com/docs/TECH178798 NOTE : The Alert can be Ignored Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation fromFollow one of those solutions: Link 1 http://www.symantec.com/business/support/index?page=content&id=TECH59749 Problem After an Upgrade from Backup Exec for Windows 11d to Backup Exec 12 or 12.5 Catalog Error "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" when the Backup Exec Database (BEDB) is located on a remote SQL Server or not in the default named SQL (BKUPEXEC) Instance. Error Event Viewer Application Log: Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Description: Access to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘UpdateCatMediaInfo'. cat_RecordSet::Open() r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(2404) {CALL UpdateCatMediaInfo( ?, ?, ?, ?) } Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34338 Description: Backup Exec Alert: Catalog Error (Server: "SERVERNAME") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Description: Access to catalog index (Catalog index database) failed. Reason: Data type mismatch cat_RecordSet::SetField() r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(3613) sp_sproc_columns CatImageInfoProc Environment The Backup Exec Database (BEDB) is located on a remote SQL Server or is not in the default named SQL (BKUPEXEC) Instance. Solution After an upgrade from Backup Exec 11d to Backup Exec 12.0 or 12.5 multiple Catalog Errors appear in the Application Log and the Backup Exec Alerts tab when the Backup Exec database (BEDB) is located on a remote SQL server or not in the default named (BKUPEXEC) SQL instance. The alerts appear when the Backup Exec Services Start and during a backup or catalog job. Backup